linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Aug 28
Date: Fri, 28 Aug 2015 12:06:46 -0700	[thread overview]
Message-ID: <CAPcyv4iWFGKOLd0KJQRBR9_bG1czoiA_edpoeS5WXtWf_SD9XA@mail.gmail.com> (raw)
In-Reply-To: <20150828152441.GA8179@roeck-us.net>

On Fri, Aug 28, 2015 at 8:24 AM, Guenter Roeck <linux@roeck-us.net> wrote:
> On Fri, Aug 28, 2015 at 06:27:12PM +1000, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20150827:
>>
>> The rdma tree gained a conflict aaginst the net-next tree.
>>
>> The sound-asoc tree gained a build failure for which I reverted a commit.
>>
>> The mmc-uh tree lost its build failure.
>>
>> The tty tree still had its build failure for which I reverted part of
>> a commit.
>>
>> The nvdimm tree gained conflicts against Linus' and the v4l-dvb trees.
>>
>> Non-merge commits (relative to Linus' tree): 10211
>>  8743 files changed, 533186 insertions(+), 210999 deletions(-)
>>
>> ----------------------------------------------------------------------------
>>
>
> Time for a status report. We might see at least some of the following
> failures in mainline after the commit window closes.
>
> Build results:
>         total: 145 pass: 138 fail: 7
> Failed builds:
>         alpha:allmodconfig [1], [2]

Thanks for the report!  Fixed and pushed back out to the
libnvdimm-for-next branch of nvdimm.git

  reply	other threads:[~2015-08-28 19:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-28  8:27 linux-next: Tree for Aug 28 Stephen Rothwell
2015-08-28 15:24 ` Guenter Roeck
2015-08-28 19:06   ` Dan Williams [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-08-28  5:25 Stephen Rothwell
2024-08-28  7:21 Stephen Rothwell
2023-08-28  5:02 Stephen Rothwell
2020-08-28  5:23 Stephen Rothwell
2019-08-28 10:02 Stephen Rothwell
2018-08-28  1:24 Stephen Rothwell
2017-08-28  9:31 Stephen Rothwell
2014-08-28  5:46 Stephen Rothwell
2013-08-28  8:45 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=CAPcyv4iWFGKOLd0KJQRBR9_bG1czoiA_edpoeS5WXtWf_SD9XA@mail.gmail.com \
    --to=dan.j.williams@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --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).