From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg KH <greg@kroah.com>
Cc: Felipe Balbi <balbi@kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Pawel Laszczak <pawell@cadence.com>
Subject: Re: linux-next: build failure after merge of the usb and usb-gadget trees
Date: Thu, 4 Jul 2019 17:47:11 +1000 [thread overview]
Message-ID: <20190704174711.0e4a18c5@canb.auug.org.au> (raw)
In-Reply-To: <20190704065949.GA32707@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 429 bytes --]
Hi Greg,
On Thu, 4 Jul 2019 08:59:49 +0200 Greg KH <greg@kroah.com> wrote:
>
> Odd, I thought I pulled the usb-gadget tree into mine.
You did. So after it failed in your tree and I used yesterday's
version of your tree, the build then failed after I merged the
usb-gadget tree (which I do after merging your tree). The usb-gadget
tree contains commits that were not there yesterday.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-07-04 7:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 6:34 linux-next: build failure after merge of the usb and usb-gadget trees Stephen Rothwell
2019-07-04 6:59 ` Greg KH
2019-07-04 7:28 ` Felipe Balbi
2019-07-04 8:07 ` Pawel Laszczak
2019-07-04 8:25 ` Felipe Balbi
2019-07-04 8:32 ` Greg KH
2019-07-04 8:45 ` Felipe Balbi
2019-07-04 11:03 ` Greg KH
2019-07-04 9:08 ` Pawel Laszczak
2019-07-04 9:25 ` Pawel Laszczak
2019-07-04 9:45 ` Felipe Balbi
2019-07-04 9:44 ` Felipe Balbi
2019-07-04 11:03 ` Greg KH
2019-07-04 11:06 ` Felipe Balbi
2019-07-05 4:42 ` Pawel Laszczak
2019-07-04 15:53 ` Nishanth Menon
2019-07-08 15:09 ` Sekhar Nori
2019-07-04 7:47 ` 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=20190704174711.0e4a18c5@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=balbi@kernel.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pawell@cadence.com \
/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).