public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Winischhofer <thomas@winischhofer.net>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>,
	ak@muc.de, hch@lst.de, linux-kernel@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net
Subject: Re: [2.6 patch] {,un}register_ioctl32_conversion should have been removed last month
Date: Tue, 03 May 2005 09:30:06 +0200	[thread overview]
Message-ID: <4277287E.4040003@winischhofer.net> (raw)
In-Reply-To: <20050503003959.GQ3592@stusta.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Adrian Bunk wrote:
> On Mon, May 02, 2005 at 05:30:52PM -0700, Andrew Morton wrote:
> 
>>Adrian Bunk <bunk@stusta.de> wrote:
>>
>>>This removal should have happened last month.
>>
>>drivers/usb/misc/sisusbvga/sisusb.c will use these functions if someone
>>defines SISUSB_OLD_CONFIG_COMPAT, so we need to agree to zap that code
>>before I can merge this upstream.


Why on earth should anyone #define something with "SISUSB" in the
beginning, on a level that might be available in a usb driver?


> 
> That's not a problem.
> 
> 
> Quoting drivers/usb/misc/sisusbvga/sisusb.h:
> 
> #ifdef CONFIG_COMPAT
> #if LINUX_VERSION_CODE <= KERNEL_VERSION(2,6,10)
> #include <linux/ioctl32.h>
> #define SISUSB_OLD_CONFIG_COMPAT
> #else
> #define SISUSB_NEW_CONFIG_COMPAT
> #endif
> #endif
> 
> 
> I decided not to drop the SISUSB_OLD_CONFIG_COMPAT code in my patch 
> because it seems Thomas is sharing this code between different kernel 
> versions, and a removal might make his life harder for no big win.


Exactly. Thanks, Adrian.

Thomas

- --
Thomas Winischhofer
Vienna/Austria
thomas AT winischhofer DOT net	       *** http://www.winischhofer.net
twini AT xfree86 DOT org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCdyh+zydIRAktyUcRAgTLAKDJ7woebRDkqRS70aImI5c0y+fiyQCgyNqE
8haWeqvcbbbCjYn607Xh51E=
=ZaoZ
-----END PGP SIGNATURE-----

  reply	other threads:[~2005-05-03  7:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-02  1:45 [2.6 patch] {,un}register_ioctl32_conversion should have been removed last month Adrian Bunk
2005-05-02 16:09 ` Andi Kleen
2005-05-02 16:20   ` Christoph Hellwig
2005-05-02 16:34   ` Adrian Bunk
2005-05-02 17:16     ` Andi Kleen
2005-05-03  0:30 ` Andrew Morton
2005-05-03  0:39   ` Adrian Bunk
2005-05-03  7:30     ` Thomas Winischhofer [this message]
2005-05-03 14:46   ` Andi Kleen

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=4277287E.4040003@winischhofer.net \
    --to=thomas@winischhofer.net \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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