From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: linux-kernel@vger.kernel.org, davem@davemloft.net, dipankar@in.ibm.com
Subject: Re: [PATCH] Add list_for_each_rcu to features-removal list
Date: Sat, 16 Feb 2008 08:19:58 -0800 [thread overview]
Message-ID: <20080216161958.GC27468@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080216084723.GD9962@cs181133002.pp.htv.fi>
On Sat, Feb 16, 2008 at 10:47:23AM +0200, Adrian Bunk wrote:
> On Mon, Jan 28, 2008 at 04:25:00AM -0800, Paul E. McKenney wrote:
> > Hello!
> >
> > The list_for_each_entry_rcu() primitive should be used instead of
> > list_for_each_rcu(), as the former is easier to use and provides
> > better type safety. This patch therefore adds list_for_each_rcu()
> > to the Documentation/feature-removal-schedule.txt file (for mid-2008)
> > and marks its comment header deprecated.
> >
> > Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> > ---
> >
> > Documentation/feature-removal-schedule.txt | 10 ++++++++++
> > include/linux/list.h | 5 ++++-
> > 2 files changed, 14 insertions(+), 1 deletion(-)
> >
> > diff -urpNa -X dontdiff linux-2.6.24/Documentation/feature-removal-schedule.txt linux-2.6.24-dep-lfeRCU/Documentation/feature-removal-schedule.txt
> > --- linux-2.6.24/Documentation/feature-removal-schedule.txt 2008-01-24 14:58:37.000000000 -0800
> > +++ linux-2.6.24-dep-lfeRCU/Documentation/feature-removal-schedule.txt 2008-01-28 04:00:49.000000000 -0800
> > @@ -333,3 +333,13 @@ Why: This driver has been marked obsolet
> > Who: Stephen Hemminger <shemminger@linux-foundation.org>
> >
> > ---------------------------
> > +
> > +What: list_for_each_rcu() primitive
> > +When: July 2008
> > +Files: include/linux/list.h
> > +Why: The list_for_each_entry_rcu() primitive should be used instead,
> > + as it is less error-prone and provides better type safety.
> > +Who: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> >...
>
> Declaring something as deprecated doesn't automatically convert the
> in-kernel users.
Understood.
> And once there are no in-kernel users left you can kill it immediately.
Hmmm... What is the purpose of Documentation/feature-removal-schedule.txt
in that case?
> The only working way for getting rid of list_for_each_rcu() is:
> - send patches for all in-kernel usages to the maintainers of the code
> in question now
That has happened at least once.
> - once all of these patches have entered Linus' tree (which might not
> be before the 2.6.26 merge window) you can remove list_for_each_rcu()
So your approach would be to mark the macro obsolete to prevent additional
uses in the meantime?
Thanx, Paul
next prev parent reply other threads:[~2008-02-16 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 12:25 Paul E. McKenney
2008-02-16 8:47 ` Adrian Bunk
2008-02-16 16:19 ` Paul E. McKenney [this message]
2008-02-16 16:39 ` Adrian Bunk
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=20080216161958.GC27468@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=bunk@kernel.org \
--cc=davem@davemloft.net \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome