All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jens Axboe <jens.axboe@oracle.com>, linux-next@vger.kernel.org
Subject: Re: linux-next: manual merge of the generic-ipi tree
Date: Wed, 16 Jul 2008 12:40:12 +0200	[thread overview]
Message-ID: <20080716104012.GA2425@elte.hu> (raw)
In-Reply-To: <20080716202521.ea91d90d.sfr@canb.auug.org.au>


* Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi Ingo,
> 
> On Wed, 16 Jul 2008 12:19:21 +0200 Ingo Molnar <mingo@elte.hu> wrote:
> >
> > hm, generic-ipi is already in Linus's tree:
> 
> Yeah, but powerpc wasn't when I started this morning (and now is).
> 
> > i hope i'll be able to update the auto-*-next branches soon - a lot of 
> > them got very empty ;-)
> 
> As I am hoping ...

hm, so them being stale over the merge window is a problem for you, even 
thought the sha1's didnt change? Ok - i'll do a full integration run 
right away to update them all to linus-very-latest. There's been quite a 
number of nontrivial interactions.

	Ingo

  reply	other threads:[~2008-07-16 10:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-16  9:45 linux-next: manual merge of the generic-ipi tree Stephen Rothwell
2008-07-16 10:19 ` Ingo Molnar
2008-07-16 10:25   ` Stephen Rothwell
2008-07-16 10:40     ` Ingo Molnar [this message]
2008-07-16 10:56       ` Stephen Rothwell
2008-07-16 11:44         ` Ingo Molnar
2008-07-16 11:14       ` Ingo Molnar
2008-07-16 13:14         ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2008-07-07 16:46 Stephen Rothwell
2008-07-03  6:56 Stephen Rothwell
2008-07-03  6:44 Stephen Rothwell
2008-07-03  6:40 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=20080716104012.GA2425@elte.hu \
    --to=mingo@elte.hu \
    --cc=jens.axboe@oracle.com \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.