From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Emmanuel Colbus <ecolbus@manux.info>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][4/11][MANUX] Kernel compatibility : ioctl(2)
Date: Tue, 15 Apr 2014 17:05:19 +0100 [thread overview]
Message-ID: <20140415170519.75d885fb@alan.etchedpixels.co.uk> (raw)
In-Reply-To: <534D5795.8080100@manux.info>
> I think this is an unproblematic extension, especially since these
> ioctls are only supposed to be called by low-level software shipped with
> the OS.
Thats the excuse everyone gives for messing up standards stuff. It
usually comes back to bite you later.
If it's not ioctl don't call it ioctl, have a fdoctl() or something
Alan
next prev parent reply other threads:[~2014-04-15 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 13:42 Emmanuel Colbus
2014-04-15 15:00 ` One Thousand Gnomes
2014-04-15 16:00 ` Emmanuel Colbus
2014-04-15 16:05 ` One Thousand Gnomes [this message]
2014-04-15 16:32 ` Emmanuel Colbus
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=20140415170519.75d885fb@alan.etchedpixels.co.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=ecolbus@manux.info \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome