All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Laurentiu Tudor <laurentiu.tudor@nxp.com>,
	"heiko.carstens@de.ibm.com" <heiko.carstens@de.ibm.com>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure in the staging tree (Was: kisskb: FAILED linux-next/s390-allmodconfig/s390x Mon Jul 31, 17:24)
Date: Mon, 14 Aug 2017 15:19:29 -0700	[thread overview]
Message-ID: <20170814221929.GA25665@kroah.com> (raw)
In-Reply-To: <20170811100435.5094fa5b@canb.auug.org.au>

On Fri, Aug 11, 2017 at 10:04:35AM +1000, Stephen Rothwell wrote:
> Hi Greg,
> 
> On Thu, 10 Aug 2017 16:48:42 -0700 Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > I have a patch in my queue, somewhere, that should resolve this, I
> > think.  I have 600+ staging patches in my todo queue right now, that's
> > what I get for trying to have a vacation...
> > 
> > I'll get to it soon, it's not lost, thanks.
> 
> No worries, just checking.

Ok, should now be fixed in my tree.

thanks,

greg k-h

  reply	other threads:[~2017-08-14 22:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170731072425.1.95853@222023911cb9>
2017-07-31  9:35 ` linux-next: build failure in the staging tree (Was: kisskb: FAILED linux-next/s390-allmodconfig/s390x Mon Jul 31, 17:24) Stephen Rothwell
2017-07-31  9:55   ` Laurentiu Tudor
2017-07-31 15:58     ` Greg KH
2017-08-01  8:29       ` Laurentiu Tudor
2017-08-07  0:22         ` Stephen Rothwell
2017-08-10 23:41           ` Stephen Rothwell
2017-08-10 23:48             ` Greg KH
2017-08-11  0:04               ` Stephen Rothwell
2017-08-14 22:19                 ` Greg KH [this message]
2017-08-14 23:06                   ` 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=20170814221929.GA25665@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=laurentiu.tudor@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.