From: Andrew Morton <akpm@linux-foundation.org>
To: Franck Bui-Huu <vagabon.xyz@gmail.com>
Cc: linux-kernel@vger.kernel.org, paulmck@linux.vnet.ibm.com
Subject: Re: [PATCH 1/2] Split list.h and move rcu-protected lists into rculist.h
Date: Sun, 3 Feb 2008 01:00:13 -0800 [thread overview]
Message-ID: <20080203010013.04bc601e.akpm@linux-foundation.org> (raw)
In-Reply-To: <47A57F25.5070902@gmail.com>
On Sun, 03 Feb 2008 09:45:25 +0100 Franck Bui-Huu <vagabon.xyz@gmail.com> wrote:
> Andrew Morton wrote:
> > On Sat, 02 Feb 2008 14:32:41 +0100 Franck Bui-Huu <vagabon.xyz@gmail.com> wrote:
> >> Do you think it's better ?
> >
> > Could. I'd suggest that you redo the header-file split patch around the
> > 2.6.25-rc1 timeframe, test it carefully then let's get it in then.
> >
>
> Does the mm tree also have a calm down period during release candidates ?
Yes, I try to not merge too much material late in the -rcs and in the merge
window. Often it's not practical to merge things anyway, because people
prepare patches against mainline, which is ancient history...
> I have modified the patchset so now if rcu helpers are used from
> rculist.h then fine otherwise gcc warns you that you're using the
> helpers from list.h like this:
>
> init/foo.c:13: warning: ‘__deprecated_list_add_rcu’ is deprecated (declared at include/linux/rculist.h:76)
>
> But the build process doesn't fail anymore.
>
> For that I added some ugly hacks in list.h and rculist.h but they
> definitively should be removed for mainline inclusion. I'm sending them
> in response to this email.
I wouldn't bother, really. Let's just get it as good as we can and slam it
in.
> If we include this now, then people can have a chance to notice that
> rculist.h exists and fix their stuffs until 2.6.25 release
> candidates but I'll redo the patchset and give it some test around the
> 2.6.25-rc1 timeframe anyway.
I'm just about finished compilation-testing for 2.6.24-mm1 which is a
shame. Please do a best-effort against 2.6.24-mm1 (hopefully I'll get that
out tomorrow) and I'll slip it into -rc1 if it gets through cross-build
testing without unfixable-with-my-patience-level problems.
next prev parent reply other threads:[~2008-02-03 9:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 20:46 [PATCH 0/2] Make RCU lists use the RCU API Franck Bui-Huu
2008-01-17 20:47 ` [PATCH 1/2] Split list.h and move rcu-protected lists into rculist.h Franck Bui-Huu
2008-02-01 23:58 ` Andrew Morton
2008-02-02 13:32 ` Franck Bui-Huu
2008-02-02 19:15 ` Andrew Morton
2008-02-03 8:45 ` Franck Bui-Huu
2008-02-03 9:00 ` Andrew Morton [this message]
2008-02-03 9:11 ` Franck Bui-Huu
2008-01-17 20:48 ` [PATCH 2/2] rculist.h: use the rcu API Franck Bui-Huu
2008-01-18 5:55 ` Paul E. McKenney
-- strict thread matches above, loose matches on Subject: below --
2008-02-19 11:51 [PATCH 1/2] Split list.h and move rcu-protected lists into rculist.h Franck Bui-Huu
2008-05-14 21:24 Franck Bui-Huu
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=20080203010013.04bc601e.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=vagabon.xyz@gmail.com \
/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