Linux-Next discussions
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Pekka Enberg <penberg@cs.helsinki.fi>,
	Christoph Lameter <cl@linux-foundation.org>
Cc: linux-next@vger.kernel.org, Nick Piggin <npiggin@suse.de>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: linux-next: manual merge of the slab tree with Linus' tree
Date: Thu, 5 Mar 2009 16:18:16 +1100	[thread overview]
Message-ID: <20090305161816.ca8ac8e4.sfr@canb.auug.org.au> (raw)

Hi all,

Today's linux-next merge of the slab tree got a conflict in
include/linux/rcupdate.h between commit
a682604838763981613e42015cd0e39f2989d6bb ("rcu: Teach RCU that idle task
is not quiscent state at boot") from Linus' tree and commit
32efb35b328d0e87fa5358239c54c889226cc6e7 ("SLQB slab allocator (try 2)")
from the slab tree.

Just a context change.  I fixed it up (see below) and can carry the fix
as necessary.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

diff --cc include/linux/rcupdate.h
index 528343e,e2917ee..0000000
--- a/include/linux/rcupdate.h
+++ b/include/linux/rcupdate.h
@@@ -42,19 -43,6 +43,9 @@@
  #include <linux/lockdep.h>
  #include <linux/completion.h>
  
- /**
-  * struct rcu_head - callback structure for use with RCU
-  * @next: next update requests in a list
-  * @func: actual update function to call after the grace period.
-  */
- struct rcu_head {
- 	struct rcu_head *next;
- 	void (*func)(struct rcu_head *head);
- };
- 
 +/* Internal to kernel, but needed by rcupreempt.h. */
 +extern int rcu_scheduler_active;
 +
  #if defined(CONFIG_CLASSIC_RCU)
  #include <linux/rcuclassic.h>
  #elif defined(CONFIG_TREE_RCU)

             reply	other threads:[~2009-03-05  5:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-05  5:18 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-05-09  2:41 linux-next: manual merge of the slab tree with Linus' tree Stephen Rothwell
2011-05-09 15:39 ` Christoph Lameter
2024-06-03  2:33 Stephen Rothwell

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=20090305161816.ca8ac8e4.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=cl@linux-foundation.org \
    --cc=linux-next@vger.kernel.org \
    --cc=npiggin@suse.de \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=penberg@cs.helsinki.fi \
    /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