From: Michael Ellerman <mpe@ellerman.id.au>
To: David Daney <david.daney@cavium.com>,
Jason Baron <jbaron@akamai.com>,
Steven Rostedt <rostedt@goodmis.org>,
Sachin Sant <sachinp@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org
Cc: linux-mips@linux-mips.org, linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
Chris Metcalf <cmetcalf@mellanox.com>,
Ralf Baechle <ralf@linux-mips.org>,
Russell King <linux@armlinux.org.uk>,
Rabin Vincent <rabin@rab.in>, Paul Mackerras <paulus@samba.org>,
Anton Blanchard <anton@samba.org>, Ingo Molnar <mingo@kernel.org>,
Zhigang Lu <zlu@ezchip.com>, David Daney <david.daney@cavium.com>
Subject: Re: [PATCH] module: set __jump_table alignment to 8
Date: Thu, 02 Mar 2017 22:18:30 +1100 [thread overview]
Message-ID: <8737ewexkp.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <87varsj6qc.fsf@concordia.ellerman.id.au>
Michael Ellerman <mpe@ellerman.id.au> writes:
> David Daney <david.daney@cavium.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.
cheers
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <mpe@ellerman.id.au>
To: David Daney <david.daney@cavium.com>,
Jason Baron <jbaron@akamai.com>,
Steven Rostedt <rostedt@goodmis.org>,
Sachin Sant <sachinp@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org
Cc: linux-mips@linux-mips.org, linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
Chris Metcalf <cmetcalf@mellanox.com>,
Ralf Baechle <ralf@linux-mips.org>,
Russell King <linux@armlinux.org.uk>,
Rabin Vincent <rabin@rab.in>, Paul Mackerras <paulus@samba.org>,
Anton Blanchard <anton@samba.org>, Ingo Molnar <mingo@kernel.org>,
Zhigang Lu <zlu@ezchip.com>
Subject: Re: [PATCH] module: set __jump_table alignment to 8
Date: Thu, 02 Mar 2017 22:18:30 +1100 [thread overview]
Message-ID: <8737ewexkp.fsf@concordia.ellerman.id.au> (raw)
Message-ID: <20170302111830.dIDtbrDXDcoX4KJ9A7uFxAhv7Xsvem7lo2ubzoXaHYI@z> (raw)
In-Reply-To: <87varsj6qc.fsf@concordia.ellerman.id.au>
Michael Ellerman <mpe@ellerman.id.au> writes:
> David Daney <david.daney@cavium.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.
cheers
next prev parent reply other threads:[~2017-03-02 11:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 22:04 [PATCH] module: set __jump_table alignment to 8 David Daney
2017-03-02 10:47 ` Michael Ellerman
2017-03-02 10:47 ` Michael Ellerman
2017-03-02 11:18 ` Michael Ellerman [this message]
2017-03-02 11:18 ` Michael Ellerman
2017-03-02 17:44 ` Steven Rostedt
2017-03-03 3:34 ` Michael Ellerman
2017-03-02 15:30 ` Jason Baron
2017-03-02 18:11 ` Steven Rostedt
2017-03-02 18:26 ` Jessica Yu
2017-03-02 19:24 ` David Daney
2017-03-02 22:49 ` Jessica Yu
-- strict thread matches above, loose matches on Subject: below --
2017-02-28 20:10 David Daney
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=8737ewexkp.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=anton@samba.org \
--cc=cmetcalf@mellanox.com \
--cc=david.daney@cavium.com \
--cc=jbaron@akamai.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux@armlinux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@kernel.org \
--cc=paulus@samba.org \
--cc=rabin@rab.in \
--cc=ralf@linux-mips.org \
--cc=rostedt@goodmis.org \
--cc=sachinp@linux.vnet.ibm.com \
--cc=zlu@ezchip.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