From: Michael Ellerman <mpe@ellerman.id.au>
To: Kamal Mostafa <kamal@canonical.com>, Alan Modra <amodra@gmail.com>
Cc: kernel-team@lists.ubuntu.com,
Sasha Levin <sasha.levin@oracle.com>,
stable <stable@vger.kernel.org>,
Anton Blanchard <anton@samba.org>
Subject: Re: [3.19.y-ckt stable][dropping] Patch "powerpc: Simplify module TOC handling"
Date: Mon, 15 Feb 2016 20:22:55 +1100 [thread overview]
Message-ID: <1455528175.26205.1.camel@ellerman.id.au> (raw)
In-Reply-To: <1455221508.24361.23.camel@fourier>
On Thu, 2016-02-11 at 12:11 -0800, Kamal Mostafa wrote:
> > > On Tue, Feb 09, 2016 at 02:41:48PM -0800, Kamal Mostafa wrote:
> > > > This is a note to let you know that I have just added a patch titled
> > > > powerpc: Simplify module TOC handling
> > > > to the linux-3.19.y-queue branch of the 3.19.y-ckt extended stable tree
>
> > On Wed, 2016-02-10 at 09:49 +1030, Alan Modra wrote:
> > > Please also add this followup patch by Anton:
> > > https://build.opensuse.org/package/view_file/Base:System/kmod/depmod-Ignore_PowerPC64_ABIv2_.TOC.symbol.patch
> > > depmod: Ignore PowerPC64 ABIv2 .TOC. symbol
>
> On Wed, 2016-02-10 at 11:53 -0800, Kamal Mostafa wrote:
>
> > That ("depmod: Ignore PowerPC64 ABIv2 .TOC. symbol") is a patch to
> > 'kmod' which is not part of the kernel source tree. So I can't include
> > that patch in a stable kernel release -- each distro's kmod package
> > would have to do that.
>
> Okay, I now realize that the stable kernel patch ("powerpc: Simplify
> module TOC handling") will break the ppc64 build for hosts that don't
> have that depmod patch.
>
> So, pending any further discussion here, I'm going to drop this from 4.2
> and 3.19 -stable after all:
>
> c153693d powerpc: Simplify module TOC handling
Yep, OK.
For some reason my build process didn't catch the failure, so I didn't realise
the depmod patch was required when I merged it.
The dilemma we have now is if we don't backport it then the branches that don't
have it won't be able to build with future binutils. But I guess that's a
problem for the future whereas the depmod breakage is happening right now.
cheers
prev parent reply other threads:[~2016-02-15 9:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1455057708-5329-1-git-send-email-kamal@canonical.com>
[not found] ` <20160209231930.GA11459@bubble.grove.modra.org>
[not found] ` <1455134004.8525.12.camel@fourier>
2016-02-11 20:11 ` [3.19.y-ckt stable][dropping] Patch "powerpc: Simplify module TOC handling" Kamal Mostafa
2016-02-15 9:22 ` Michael Ellerman [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=1455528175.26205.1.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=amodra@gmail.com \
--cc=anton@samba.org \
--cc=kamal@canonical.com \
--cc=kernel-team@lists.ubuntu.com \
--cc=sasha.levin@oracle.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