linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: linux-next@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Apr 10
Date: Tue, 10 Apr 2012 15:12:29 +1000	[thread overview]
Message-ID: <20120410151229.836f8d8e806f33d26c4719f9@canb.auug.org.au> (raw)
In-Reply-To: <20120410145546.65b54b0d515db38e23bb4624@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 790 bytes --]

On Tue, 10 Apr 2012 14:55:46 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Changes since 20120405:
> 
> New trees: sh-current, sh
> 
> The tile tree gained conflicts against Linus' tree.
> 
> The net-next tree lost its build failure.
> 
> The wireless-next tree gained a conflict against the net-next tree.
> 
> The trivial tree lost its conflict.

The regulator tree gained a build failure so I used the version from
next-20120405.

> The tty tree gained a build failure so I used the version from
> next-20120405.
> 
> The pinctrl tree still had its build failure so I used the version from
> next-20120403.
> 
> The akpm tree lost several patches that turned up in Linus' tree.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-04-10  5:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-10  4:55 linux-next: Tree for Apr 10 Stephen Rothwell
2012-04-10  5:12 ` Stephen Rothwell [this message]
2013-04-10  8:48 Stephen Rothwell
2013-04-10 10:40 ` Sedat Dilek
2014-04-10  4:50 Stephen Rothwell
2015-04-10 11:18 Stephen Rothwell
2017-04-10  7:52 Stephen Rothwell
2018-04-10  4:51 Stephen Rothwell
2019-04-10  6:30 Stephen Rothwell
2020-04-10  3:27 Stephen Rothwell
2024-04-10  4:53 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=20120410151229.836f8d8e806f33d26c4719f9@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.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).