public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: yamada.masahiro@socionext•com
Cc: davem@davemloft•net, npiggin@gmail•com,
	linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	amodra@gmail•com
Subject: Re: linux-next: build failure after merge of most trees
Date: Fri, 23 Jun 2017 17:04:21 +1000	[thread overview]
Message-ID: <20170623170421.30459eec@canb.auug.org.au> (raw)
In-Reply-To: <cccaf981b39844cb975f41e41abcd809@SOC-EX01V.e01.socionext.com>

Hi,

On Fri, 23 Jun 2017 06:46:53 +0000 <yamada.masahiro@socionext•com> wrote:
>
> > -----Original Message-----
> > From: Stephen Rothwell [mailto:sfr@canb•auug.org.au]
> > Sent: Friday, June 23, 2017 3:43 PM
> > To: David Miller <davem@davemloft•net>
> > Cc: npiggin@gmail•com; linux-next@vger•kernel.org;
> > linux-kernel@vger•kernel.org; Yamada, Masahiro/山田 真弘
> > <yamada.masahiro@socionext•com>; amodra@gmail•com
> > Subject: Re: linux-next: build failure after merge of most trees
> > 
> > Hi all,
> > 
> > On Thu, 22 Jun 2017 10:56:48 -0400 (EDT) David Miller <davem@davemloft•net>
> > wrote:  
> > >
> > > Feel free to merge it into your series:
> > >
> > > ====================  
> [snip]
> > 
> > I added that to linux-next today and it fixed the build problem.  
> 
> Thanks for taking care of this.

No worries.

> Sorry, I missed to pick up this for today's release.
> I will insert this before Nicholas' series.

Thanks, I will drop it on Monday.

-- 
Cheers,
Stephen Rothwell

  reply	other threads:[~2017-06-23  7:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-22  5:24 linux-next: build failure after merge of most trees Stephen Rothwell
2017-06-22  5:49 ` Nicholas Piggin
2017-06-22  6:20   ` Stephen Rothwell
2017-06-22  6:23     ` Stephen Rothwell
2017-06-22  8:41 ` Nicholas Piggin
2017-06-22 14:13   ` David Miller
2017-06-22 14:29     ` David Miller
2017-06-23  3:40       ` Nicholas Piggin
2017-06-22 14:33     ` Nicholas Piggin
2017-06-22 14:56       ` David Miller
2017-06-23  3:34         ` Nicholas Piggin
2017-06-23  6:43         ` Stephen Rothwell
2017-06-23  6:46           ` yamada.masahiro
2017-06-23  7:04             ` Stephen Rothwell [this message]
2017-06-23 15:13             ` David Miller
2017-06-22 14:13   ` Alan Modra
2017-06-22 14:43     ` Nicholas Piggin

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=20170623170421.30459eec@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=amodra@gmail$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=npiggin@gmail$(echo .)com \
    --cc=yamada.masahiro@socionext$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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