From: Harvey Harrison <harvey.harrison@gmail.com>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Miller <davem@davemloft.net>,
Jiri Slaby <jirislaby@gmail.com>, Pavel Machek <pavel@suse.cz>,
Christoph Hellwig <hch@lst.de>,
Dominik Brodowski <linux@brodo.de>, Andi Kleen <ak@suse.de>,
Adrian Bunk <bunk@stusta.de>, Greg Kroah-Hartman <gregkh@suse.de>,
Nick Piggin <npiggin@suse.de>,
Stephen Hemminger <shemminger@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Randy Dunlap <randy.dunlap@oracle.com>,
Len Brown <len.brown@intel.com>
Subject: Re: Feature Removals for 2.6.25
Date: Thu, 31 Jan 2008 23:04:20 -0800 [thread overview]
Message-ID: <1201849460.23523.92.camel@brick> (raw)
In-Reply-To: <47A2BD22.4020106@linux.intel.com>
On Thu, 2008-01-31 at 22:33 -0800, Arjan van de Ven wrote:
> Harvey Harrison wrote:
> > Something like the following (grep found me two example symbols)
>
> to be honest, nobody reads this file with such detail; the actual UNUSED marking
> is a lot more louder and people are more likely to notice those.... for all I care
> we nuke the entire entry from the removals file.
Well, if there is interest in having an up-to-date file, I'm willing to
do the bookkeeping to make this usable and try to keep it up to date.
Anybody think this is worthwhile?
Harvey
next prev parent reply other threads:[~2008-02-01 7:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 1:38 Feature Removals for 2.6.25 Harvey Harrison
2008-02-01 4:53 ` Arjan van de Ven
2008-02-01 5:18 ` Harvey Harrison
2008-02-01 6:33 ` Arjan van de Ven
2008-02-01 7:04 ` Harvey Harrison [this message]
2008-02-01 5:02 ` Feature Removals for 2.6.25 (USB driver api) Greg KH
2008-02-01 7:08 ` Feature Removals for 2.6.25 Stephen Hemminger
2008-02-02 1:29 ` Nick Piggin
2008-02-03 10:44 ` Feature Removals for 2.6.25 - old NCR53C9x driver Boaz Harrosh
2008-02-14 2:49 ` Feature Removals for 2.6.25 Bill Davidsen
2008-02-14 2:55 ` Stephen Hemminger
2008-02-14 18:16 ` Bill Davidsen
2008-02-14 18:24 ` Arjan van de Ven
2008-02-14 18:26 ` Christoph Hellwig
2008-02-14 23:20 ` David Newall
2008-02-15 3:27 ` Rene Herman
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=1201849460.23523.92.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=bunk@stusta.de \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=hch@lst.de \
--cc=jirislaby@gmail.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
--cc=npiggin@suse.de \
--cc=pavel@suse.cz \
--cc=randy.dunlap@oracle.com \
--cc=shemminger@linux-foundation.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 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.