From: Gavin Shan <gwshan@linux.vnet.ibm.com>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Gavin Shan <gwshan@linux.vnet.ibm.com>,
Guenter Roeck <linux@roeck-us.net>,
stable <stable@vger.kernel.org>, Youngmin Nam <ym0914@gmail.com>,
Alan Cox <alan@linux.intel.com>
Subject: Re: Build errors in v3.18-stable-queue
Date: Wed, 2 Mar 2016 10:17:08 +1100 [thread overview]
Message-ID: <20160301231708.GA4979@gwshan> (raw)
In-Reply-To: <56D5B2EC.5000906@oracle.com>
On Tue, Mar 01, 2016 at 10:19:08AM -0500, Sasha Levin wrote:
>On 03/01/2016 12:06 AM, Gavin Shan wrote:
>> Cc: stable@vger.kernel.org # v4.1+
>
>What about the 3.18 breakages? Is there a different fix for those?
>
This build failure is introduced by commit ff57b45 ("powerpc/eeh:
Do probe on pci_dn") which was merged to 4.1 kernel. I don't know
why 3.18 stable kernel needs it. If 3.18 stable kernel needs the
commit, yes, the attached fix should be put into 3.18 stable
kernel as well.
Let me know if there're anything else I need to handle.
gwshan@gwshan:~/sandbox/linux.main$ git tag --contains ff57b45
v4.1
v4.1-rc1
v4.1-rc2
v4.1-rc3
v4.1-rc4
v4.1-rc5
v4.1-rc6
v4.1-rc7
v4.1-rc8
v4.2
:
:
Thanks,
Gavin
>
>Thanks,
>Sasha
>
next prev parent reply other threads:[~2016-03-01 23:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-28 10:45 Build errors in v3.18-stable-queue Guenter Roeck
2016-03-01 0:24 ` Sasha Levin
2016-03-01 1:14 ` Gavin Shan
2016-03-01 2:47 ` Guenter Roeck
2016-03-01 5:06 ` Gavin Shan
2016-03-01 15:19 ` Sasha Levin
2016-03-01 23:17 ` Gavin Shan [this message]
2016-03-06 22:38 ` Gavin Shan
2016-03-02 4:31 ` Guenter Roeck
2016-03-01 11:12 ` Youngmin Nam
2016-03-01 15:18 ` Sasha Levin
-- strict thread matches above, loose matches on Subject: below --
2015-08-25 19:24 build " Guenter Roeck
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=20160301231708.GA4979@gwshan \
--to=gwshan@linux.vnet.ibm.com \
--cc=alan@linux.intel.com \
--cc=linux@roeck-us.net \
--cc=sasha.levin@oracle.com \
--cc=stable@vger.kernel.org \
--cc=ym0914@gmail.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 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.