From: "John W. Linville" <linville@tuxdriver.com>
To: Masakazu Mokuno <mokuno@sm.sony.co.jp>
Cc: linux-wireless@vger.kernel.org,
Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
geoffrey.levand@am.sony.com
Subject: Re: [PATCH] remove duplicated ioctl entries in compat_ioctl.c
Date: Thu, 26 Jul 2007 14:50:29 -0400 [thread overview]
Message-ID: <20070726185029.GC6068@tuxdriver.com> (raw)
In-Reply-To: <20070709193744.D021.MOKUNO@sm.sony.co.jp>
On Mon, Jul 09, 2007 at 07:54:39PM +0900, Masakazu Mokuno wrote:
> This patch removes some duplicated wireless ioctl entries in the array
> 'struct ioctl_trans ioctl_start[]' of fs/compat_ioctl.c
>
> These entries are registered twice like:
>
> COMPATIBLE_IOCTL(SIOCGIWPRIV)
>
> and
>
> HANDLE_IOCTL(SIOCGIWPRIV, do_wireless_ioctl)
>
>
> Signed-off-by: Masakazu Mokuno <mokuno@sm.sony.co.jp>
> ---
> fs/compat_ioctl.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> --- a/fs/compat_ioctl.c
> +++ b/fs/compat_ioctl.c
> @@ -3156,12 +3156,9 @@ COMPATIBLE_IOCTL(SIOCSIWSENS)
> COMPATIBLE_IOCTL(SIOCGIWSENS)
> COMPATIBLE_IOCTL(SIOCSIWRANGE)
> COMPATIBLE_IOCTL(SIOCSIWPRIV)
> -COMPATIBLE_IOCTL(SIOCGIWPRIV)
> COMPATIBLE_IOCTL(SIOCSIWSTATS)
> -COMPATIBLE_IOCTL(SIOCGIWSTATS)
> COMPATIBLE_IOCTL(SIOCSIWAP)
> COMPATIBLE_IOCTL(SIOCGIWAP)
> -COMPATIBLE_IOCTL(SIOCSIWSCAN)
> COMPATIBLE_IOCTL(SIOCSIWRATE)
> COMPATIBLE_IOCTL(SIOCGIWRATE)
> COMPATIBLE_IOCTL(SIOCSIWRTS)
As I read the code in compat_ioctl.c, it looks to me like the
COMPATIBLE_IOCTL definitions are the ones that are actually being
used today. Do you agree?
Given the...stability...of the wireless extensions API, if we are going
to remove one or the other of these not-quite-duplicate definitions,
shouldn't we remove the HANDLE_IOCTL defintions instead?
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2007-07-26 19:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 10:54 [PATCH] remove duplicated ioctl entries in compat_ioctl.c Masakazu Mokuno
2007-07-09 11:10 ` Holger Schurig
2007-07-09 11:13 ` Holger Schurig
2007-07-20 5:04 ` Masakazu Mokuno
2007-07-20 13:12 ` John W. Linville
2007-07-26 18:50 ` John W. Linville [this message]
2007-07-27 1:35 ` [PATCH] " Masakazu Mokuno
-- strict thread matches above, loose matches on Subject: below --
2007-07-27 19:10 John W. Linville
2007-07-27 21:58 ` Jean Tourrilhes
2007-07-30 12:02 ` Masakazu Mokuno
2007-07-30 14:47 ` John W. Linville
2007-07-30 18:37 ` Jean Tourrilhes
2007-07-31 4:45 ` Masakazu Mokuno
2007-07-31 16:55 ` Jean Tourrilhes
2007-08-07 7:41 ` Masakazu Mokuno
2007-08-07 17:51 ` Jean Tourrilhes
2007-09-12 4:36 ` Masakazu Mokuno
2007-09-12 13:43 ` John W. Linville
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=20070726185029.GC6068@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=geoffrey.levand@am.sony.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mokuno@sm.sony.co.jp \
/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 NNTP newsgroup(s).