From: Greg KH <gregkh@linuxfoundation.org>
To: Harsh Shandilya <msfjarvis@gmail.com>
Cc: stable@vger.kernel.org
Subject: Re: 3.18.y queue build failure on arm64 and x86_64
Date: Fri, 20 Apr 2018 16:09:50 +0200 [thread overview]
Message-ID: <20180420140949.GB22919@kroah.com> (raw)
In-Reply-To: <E497028E-84E4-4733-BDE7-79BD7AF1D07F@gmail.com>
On Fri, Apr 20, 2018 at 04:56:19PM +0530, Harsh Shandilya wrote:
> Hi Greg,
>
> Patch "usb: dwc3: pci: Properly cleanup resource" uses the `err` label which doesn't exist on 3.18, causing a build failure on at least the architectures mentioned in the subject line with allyesconfig. Changing `goto err` to `goto err3` resolves the build failure. Would you like me to send the fixed up patch or you would prefer to make the change by hand?
A fixed up patch would be great, but let me go look at it right now. I
knew the tree was broken, but had to get back on the road, I'm traveling
this week. Will work on it now...
greg k-h
next prev parent reply other threads:[~2018-04-20 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 11:26 3.18.y queue build failure on arm64 and x86_64 Harsh Shandilya
2018-04-20 14:09 ` Greg KH [this message]
2018-04-20 14:15 ` Greg KH
2018-04-20 15:16 ` Harsh Shandilya
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=20180420140949.GB22919@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=msfjarvis@gmail.com \
--cc=stable@vger.kernel.org \
/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).