linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	the arch/x86 maintainers <x86@kernel.org>
Subject: Re: linux-next: manual merge of the block tree
Date: Fri, 27 Jun 2008 10:47:58 +0200	[thread overview]
Message-ID: <20080627084758.GR20851@kernel.dk> (raw)
In-Reply-To: <20080627083053.GC6562@elte.hu>

On Fri, Jun 27 2008, Ingo Molnar wrote:
> 
> * Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> > Hi Jens,
> > 
> > Today's linux-next merge of the block tree got a trivial conflict in 
> > include/asm-x86/smp.h between commit 
> > a4c81cf684350797939416c99effb9d3ae46bca6 ("x86: extend e820 ealy_res 
> > support 32bit") from the x86 tree and commit 
> > 3b16cf874861436725c43ba0b68bdd799297be7c ("x86: convert to generic 
> > helpers for IPI function calls") from the block tree.
> > 
> > A case of contextually close deletions.
> 
> Jens, would it be possible for you to prepare a pullable branch for us 
> for the x86 and generic bits of the SMP generic helpers thing - 
> independent of any block tree bits? (it can touch generic code but it 
> should not break the build on other architectures)
> 
> That way we could pull it into tip/x86 and give it some testing on the 
> x86 side, and resolve its integration effects. Would that be possible?

Currently I have two branches for this - one is generic-ipi, which
contains the generic bits and all the arch conversions. The other is
smp_call_function, which kills the unused argument to
smp_call_function() (and friends) and on_each_cpu(). If I separate out
the non-x86 archs, I'll have trouble getting it all in for 2.6.27 as
I'll be on vacation as of july 5th.

So it's not tied in with any block bits, but it does have all archs.
Even if it's a bit of a weird thing to put the whole thing into the x86
tree, I don't mind if we do that. Heck, it's in the block repo to begin
with :-)

So if you could pull:

git://git.kernel.dk/linux-2.6-block.git generic-ipi

and

git://git.kernel.dk/linux-2.6-block.git smp_call_function

and merge them with the x86 changes, that would be fine. It's also the
place where we currently have conflicts due to 32-bit and 64-bit stuff
being merged, so it would help Stephen as well.

-- 
Jens Axboe

  reply	other threads:[~2008-06-27  8:48 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-27  6:13 linux-next: manual merge of the block tree Stephen Rothwell
2008-06-27  8:30 ` Ingo Molnar
2008-06-27  8:47   ` Jens Axboe [this message]
2008-06-27  9:26     ` Ingo Molnar
2008-06-27  9:57       ` Ingo Molnar
2008-06-27 10:11         ` Ingo Molnar
2008-06-27 11:21           ` Jens Axboe
2008-06-27 11:21         ` Jens Axboe
2008-06-27 11:18       ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2013-10-25 15:03 linux-next: Tree for Oct 25 Thierry Reding
2013-10-25 15:03 ` linux-next: manual merge of the block tree Thierry Reding
2013-10-14 14:48 linux-next: Tree for Oct 14 Thierry Reding
2013-10-14 14:48 ` linux-next: manual merge of the block tree Thierry Reding
2013-10-11 19:04 Mark Brown
2013-10-01 11:03 linux-next: Tree for Oct 1 Thierry Reding
2013-10-01 11:07 ` linux-next: manual merge of the block tree Thierry Reding
2013-09-30 11:26 linux-next: manual merge of the bcon tree Thierry Reding
2013-09-30 11:26 ` linux-next: manual merge of the block tree Thierry Reding
2008-12-15  7:08 Stephen Rothwell
2008-11-19  3:21 Stephen Rothwell
2008-11-19  9:14 ` Jens Axboe
2008-11-19  9:32   ` Stephen Rothwell
2008-11-07  6:14 Stephen Rothwell
2008-11-07  6:10 Stephen Rothwell
2008-11-07  9:50 ` Jens Axboe
2008-11-07 10:07   ` Stephen Rothwell
2008-10-15  7:40 Stephen Rothwell
2008-09-05  6:12 Stephen Rothwell
2008-09-05  6:22 ` Jens Axboe
2008-09-05 13:58   ` James Bottomley
2008-09-03  5:58 Stephen Rothwell
2008-09-03  5:55 Stephen Rothwell
2008-09-02  6:06 Stephen Rothwell
2008-09-02  5:59 Stephen Rothwell
2008-08-28  5:30 Stephen Rothwell
2008-08-27  5:48 Stephen Rothwell
2008-08-27  5:47 Stephen Rothwell
2008-06-27  6:09 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=20080627084758.GR20851@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=hpa@zytor.com \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sfr@canb.auug.org.au \
    --cc=tglx@linutronix.de \
    --cc=x86@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;
as well as URLs for NNTP newsgroup(s).