linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org
Subject: Re: linux-next: Tree for March 30
Date: Mon, 30 Mar 2009 20:37:06 +0200	[thread overview]
Message-ID: <200903302037.06373.rjw@sisk.pl> (raw)
In-Reply-To: <20090330200145.8d0da09b.sfr@canb.auug.org.au>

On Monday 30 March 2009, Stephen Rothwell wrote:
> Hi all,

Hi Stephen,

> Changes since 20090327:
> 
> Various conflicts have moved around due to some trees being merged into
> Linus' tree.
> 
> Linus' tree gained a build failure for which I applied a patch.
> 
> The arm tree lost its three conflicts.
> 
> The tracing tree inherited a build failure from the net tree.
> 
> The genirq tree lost its conflict.
> 
> The sched tree lost its conflict.
> 
> The v4l-dvb tree lost its build failure.
> 
> The acpi tree gained a conflict against Linus' tree but lost its build
> failure.
> 
> The ext4 tree lost its conflict.
> 
> The net tree lost all its conflicts.
> 
> The rr tree lost 8 conflicts.
> 
> The slab tree lost all its conflicts.
> 
> The drm tree lost its conflict.
> 
> The lblnet tree lost its conflicts.
> 
> The proc tree gained a build failure due to a new commit in Linus' tree -
> I applied a patch.
> 
> The suspend tree lost its conflict.

For your information, I have created for-linus branch in the suspend tree.
Currently, it is identical to the linux-next branch, but in future the Linus'
tree will be periodically merged into the for-linus branch and the linux-next
branch will be rebased on top of it.

Thanks,
Rafael

  parent reply	other threads:[~2009-03-30 18:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-30  9:01 linux-next: Tree for March 30 Stephen Rothwell
2009-03-30 12:24 ` linux-next: Tree for March 30: [BUG] kmemleak page fault Matthias Kaehlcke
2009-04-01  9:30   ` Catalin Marinas
2009-04-01  9:52     ` Matthias Kaehlcke
2009-04-02 16:08       ` Catalin Marinas
2009-04-02 17:21         ` Matthias Kaehlcke
2009-03-30 18:37 ` Rafael J. Wysocki [this message]
2010-03-30  8:18 linux-next: Tree for March 30 Stephen Rothwell
2011-03-30  3:29 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=200903302037.06373.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --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 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).