From: Bart Veer <bartv@ecoscentric.com>
To: andrew@lunn.ch
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: FWD: ioctl h8300 specific problem fix
Date: Mon, 31 Jan 2005 11:36:00 -0000 [thread overview]
Message-ID: <20050131113641.64206EC102@delenn.bartv.net> (raw)
In-Reply-To: <20050130224621.GS23679@lunn.ch> (message from Andrew Lunn on Sun, 30 Jan 2005 23:46:21 +0100)
>>>>> "Andrew" == Andrew Lunn <andrew@lunn.ch> writes:
Andrew> Hi Folks
Andrew> Any suggests as to what we should do this with patch for
Andrew> ioctl. I don't like target specific #define in a generic
Andrew> file like this. We could just make varargs the standard
Andrew> solution.
We should make the varargs version the standard solution. ioctl() has
not been well-standardized in the past, but these days the varargs
version seems to be ubiquitous and is listed @
http://www.opengroup.org/onlinepubs/009695399/functions/ioctl.html
Bart
prev parent reply other threads:[~2005-01-31 11:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-30 22:46 Andrew Lunn
2005-01-31 1:25 ` Gary Thomas
2005-01-31 9:57 ` Nick Garnett
2005-01-31 11:36 ` Bart Veer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050131113641.64206EC102@delenn.bartv.net \
--to=bartv@ecoscentric.com \
--cc=andrew@lunn.ch \
--cc=ecos-maintainers@ecos.sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).