public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Fengguang Wu <lkp@intel•com>
Cc: linux-next@vger•kernel.org, Christoph Hellwig <hch@lst•de>,
	kbuild-all@01•org, Arnd Bergmann <arnd@arndb•de>,
	linux-kernel@vger•kernel.org
Subject: Re: [kbuild-all] linux-next: build failure after merge of the asm-generic tree
Date: Fri, 16 Oct 2015 01:56:49 +1100	[thread overview]
Message-ID: <20151016015649.2d4471f2@canb.auug.org.au> (raw)
In-Reply-To: <20151015144532.GB32452@wfg-t540p.sh.intel.com>

Hi Fengguang,

On Thu, 15 Oct 2015 22:45:32 +0800 Fengguang Wu <lkp@intel•com> wrote:
>
> On Thu, Oct 15, 2015 at 01:37:34PM +1100, Stephen Rothwell wrote:
> > 
> > On Thu, 15 Oct 2015 07:32:27 +0800 kbuild test robot <lkp@intel•com> wrote:  
> > >
> > > [auto build test ERROR on v4.3-rc5 -- if it's inappropriate base, please suggest rules for selecting the more suitable base]  
> > 
> > I think you should just ignore any patches from me that have
> > "linux-next:" in the subject line as they need to be applied either to
> > a branch I have merged or to a combination of branches I have merged.  
> 
> OK. Sorry for the noise!

No worries, keep up the good work!

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

      reply	other threads:[~2015-10-15 14:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 22:55 linux-next: build failure after merge of the asm-generic tree Stephen Rothwell
2015-10-14 23:32 ` kbuild test robot
2015-10-15  2:37   ` Stephen Rothwell
2015-10-15 14:45     ` [kbuild-all] " Fengguang Wu
2015-10-15 14:56       ` Stephen Rothwell [this message]

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=20151016015649.2d4471f2@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=arnd@arndb$(echo .)de \
    --cc=hch@lst$(echo .)de \
    --cc=kbuild-all@01$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=lkp@intel$(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