From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
linux-kernel-mentees@lists.linuxfoundation.org,
dwaipayanray1@gmail.com, Aditya <yashsri421@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Jakub Jelinek <jakub@redhat.com>,
Florian Fainelli <f.fainelli@gmail.com>,
kernel test robot <lkp@intel.com>,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>, LKP <lkp@lists.01.org>,
Kees Cook <keescook@chromium.org>,
"H.J. Lu" <hjl.tools@gmail.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
linux-toolchains@vger.kernel.org
Subject: Re: GCC section alignment, and GCC-4.9 being a weird one
Date: Wed, 21 Oct 2020 21:27:15 +0200 [thread overview]
Message-ID: <CANiq72kfuDfHeL9Eb9e7PccZ+L9wMpnBj_gtFj3-aFfcvYuskA@mail.gmail.com> (raw)
In-Reply-To: <3ec15b41754b01666d94b76ce51b9832c2dd577a.camel@perches.com>
On Wed, Oct 21, 2020 at 8:35 PM Joe Perches <joe@perches.com> wrote:
>
> Perhaps something to add as a generic test in checkpatch.
Agreed! It would be nice to check all of them. Even checking for
`attribute` and `__attribute__` could be potentially reasonable (i.e.
so that people are reminded to consider adding whatever attributes
they need into `compiler_attributes.h`), although perhaps too
annoying/noisy for some (e.g. for `arch/*` devs...).
Cheers,
Miguel
next prev parent reply other threads:[~2020-10-21 19:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200629003127.GB5535@shao2-debian>
[not found] ` <20200630124628.GV4817@hirez.programming.kicks-ass.net>
[not found] ` <20200630144905.GX4817@hirez.programming.kicks-ass.net>
[not found] ` <58ff47cc-dc55-e383-7a5b-37008d145aba@gmail.com>
2020-10-21 8:00 ` GCC section alignment, and GCC-4.9 being a weird one Peter Zijlstra
2020-10-21 13:18 ` Jakub Jelinek
2020-10-21 13:44 ` Peter Zijlstra
2020-10-21 17:42 ` Nick Desaulniers
2020-10-21 17:54 ` Miguel Ojeda
2020-10-21 18:35 ` Joe Perches
2020-10-21 19:27 ` Miguel Ojeda [this message]
2020-10-22 7:38 ` Peter Zijlstra
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=CANiq72kfuDfHeL9Eb9e7PccZ+L9wMpnBj_gtFj3-aFfcvYuskA@mail.gmail.com \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=dwaipayanray1@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=hjl.tools@gmail.com \
--cc=jakub@redhat.com \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-toolchains@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=lukas.bulwahn@gmail.com \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=x86@kernel.org \
--cc=yashsri421@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 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).