From: Andi Kleen <ak@muc.de>
To: Adrian Bunk <bunk@stusta.de>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Pavel Machek <pavel@suse.cz>, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] Add removal schedule of register_serial/unregister_serial to appropriate file
Date: 23 Jun 2005 18:24:48 +0200
Date: Thu, 23 Jun 2005 18:24:48 +0200 [thread overview]
Message-ID: <20050623162448.GA5430@muc.de> (raw)
In-Reply-To: <20050623140316.GH3749@stusta.de>
On Thu, Jun 23, 2005 at 04:03:16PM +0200, Adrian Bunk wrote:
> On Thu, Jun 23, 2005 at 02:23:35PM +0100, Russell King wrote:
> >...
> > However, wouldn't it be a good idea if this file was ordered by "when" ?
> > A quick scan of the file reveals a couple of overdue/forgotten items
> > (maybe they happened but the entry in the file got missed?):
> >...
> > What: register_ioctl32_conversion() / unregister_ioctl32_conversion()
> > When: April 2005
> >...
>
> The removal (including the removal of the feature-removal-schedule.txt
> entry) is already in -mm.
Ok, but I hope whoever did that fixed the locking in the compat
path too. e.g. the BKL is not needed anymore.
-Andi
next prev parent reply other threads:[~2005-06-23 16:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-23 13:23 [PATCH] Add removal schedule of register_serial/unregister_serial to appropriate file Russell King
2005-06-23 13:54 ` Andi Kleen
2005-06-23 14:03 ` Adrian Bunk
2005-06-23 16:24 ` Andi Kleen [this message]
2005-06-23 18:32 ` Andrew Morton
2005-06-23 21:38 ` Dave Airlie
2005-06-23 19:13 ` Horst von Brand
2005-06-25 2:42 ` Pavel Machek
2005-06-25 9:47 ` Russell King
2005-06-25 9:57 ` Russell King
2005-06-27 0:36 ` David McCullough
2005-06-27 9:30 ` Russell King
2005-07-14 19:33 ` Russell King
2005-08-12 17:30 ` Max Asbock
2005-08-15 8:42 ` Russell King
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=20050623162448.GA5430@muc.de \
--to=ak@muc.de \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=torvalds@osdl.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