From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>
Cc: ak@muc.de, hch@lst.de, linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net,
Thomas Winischhofer <thomas@winischhofer.net>
Subject: Re: [2.6 patch] {,un}register_ioctl32_conversion should have been removed last month
Date: Tue, 3 May 2005 02:39:59 +0200 [thread overview]
Message-ID: <20050503003959.GQ3592@stusta.de> (raw)
In-Reply-To: <20050502173052.5c78ae30.akpm@osdl.org>
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.
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.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-05-03 0:41 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 [this message]
2005-05-03 7:30 ` Thomas Winischhofer
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=20050503003959.GQ3592@stusta.de \
--to=bunk@stusta.de \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=thomas@winischhofer.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.