[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Fri, 03 Mar 2017 14:34:58 +1100
From: Michael Ellerman <mpe@...erman.id.au>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: David Daney <david.daney@...ium.com>,
Jason Baron <jbaron@...mai.com>,
Sachin Sant <sachinp@...ux.vnet.ibm.com>,
linux-kernel@...r.kernel.org, linux-mips@...ux-mips.org,
linuxppc-dev@...ts.ozlabs.org,
linux-arm-kernel@...ts.infradead.org,
Chris Metcalf <cmetcalf@...lanox.com>,
Ralf Baechle <ralf@...ux-mips.org>,
Russell King <linux@...linux.org.uk>,
Rabin Vincent <rabin@....in>,
Paul Mackerras <paulus@...ba.org>,
Anton Blanchard <anton@...ba.org>,
Ingo Molnar <mingo@...nel.org>, Zhigang Lu <zlu@...hip.com>
Subject: Re: [PATCH] module: set __jump_table alignment to 8
Steven Rostedt <rostedt@...dmis.org> writes:
> On Thu, 02 Mar 2017 22:18:30 +1100
> Michael Ellerman <mpe@...erman.id.au> wrote:
>> Michael Ellerman <mpe@...erman.id.au> writes:
>> > David Daney <david.daney@...ium.com> writes:
>> >> Strict alignment became necessary with commit 3821fd35b58d
>> >> ("jump_label: Reduce the size of struct static_key"), currently in
>> >> linux-next, which uses the two least significant bits of pointers to
>> >> __jump_table elements.
>> >
>> > It would obviously be nice if this could go in before the commit that
>> > exposes the breakage, but I guess that's problematic because Steve
>> > doesn't want to rebase the tracing tree.
>> >
>> > Steve I think you've already sent your pull request for this cycle? So I
>> > guess if this can go in your first batch of fixes?
>>
>> Ugh. Was looking at the wrong tree - Linus has already merged the commit
>> in question, so the above is all moot.
>
> No problem. I've got some other "fixes" to push to Linus. That's what
> the -rc releases are for. To fix up breakage from the merge window ;-)
Yep, no drama.
> I'll pull this into my tree.
Thanks.
cheers
Powered by blists - more mailing lists