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: Fri, 1 Feb 2008 15:58:26 -0800 [thread overview]
Message-ID: <20080201155826.a2d308c1.akpm@linux-foundation.org> (raw)
In-Reply-To: <478FBEEA.6040000@gmail.com>
On Thu, 17 Jan 2008 21:47:38 +0100
Franck Bui-Huu <vagabon.xyz@gmail.com> wrote:
> This patch moves rcu-protected lists from list.h into a new header
> file rculist.h.
I'm getting way too many compilation errors from this, perhaps because of
new rcu-list usages which weren't present in the old tree (ie: current
Linus mainline) which you tested it against.
The most practical way to prepare a patch like this is to either make it
back-compatible (for a while at least) or to prepare and carefully test it
against latest -mm. That way you'll pick up everyone's new code.
next prev parent reply other threads:[~2008-02-01 23:58 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 [this message]
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
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=20080201155826.a2d308c1.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 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.