From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: "Peter Zijlstra" <peterz@infradead.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Martin Liška" <mliska@suse.cz>,
"Lai Jiangshan" <laijs@linux.alibaba.com>,
"Joerg Roedel" <jroedel@suse.de>,
"Lai Jiangshan" <jiangshanlai@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Andy Lutomirski" <luto@kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"Borislav Petkov" <bp@alien8.de>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
"Daniel Bristot de Oliveira" <bristot@redhat.com>,
"Brijesh Singh" <brijesh.singh@amd.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Arvind Sankar" <nivedita@alum.mit.edu>,
"Chester Lin" <clin@suse.com>, "Juergen Gross" <jgross@suse.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
linux-toolchains@vger.kernel.org
Subject: Re: [PATCH 02/24] x86/traps: Move arch/x86/kernel/traps.c to arch/x86/entry/
Date: Thu, 2 Sep 2021 19:19:07 +0200 [thread overview]
Message-ID: <CANiq72=OH0FYLnRfiVt5kjC39bZZsmjsMLCAAfh9iN1KQyzBaw@mail.gmail.com> (raw)
In-Reply-To: <CAKwvOdmhUzR0QfAU+nVRtSPu11vg9yvyJ09Pb8q1X6CEfez=8w@mail.gmail.com>
On Thu, Sep 2, 2021 at 7:05 PM Nick Desaulniers <ndesaulniers@google.com> wrote:
>
> The above 2 hunks should go in include/linux/compiler_attributes.h,
> but yes. I'd been meaning to send such a patch; it's nice to have
Note that `compiler_attributes.h` does not keep attributes that depend
on config options.
On one hand, I feel we should put them there. On the other hand, I
want to avoid making a mess again since the purpose of the file is to
keep things clean for the majority of attributes.
Perhaps we should do a middle-ground, and only allow those that depend
on a single config option, i.e. no nesting `#if`s or complex
conditions.
Cheers,
Miguel
next prev parent reply other threads:[~2021-09-02 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210831175025.27570-1-jiangshanlai@gmail.com>
[not found] ` <20210831175025.27570-3-jiangshanlai@gmail.com>
[not found] ` <YTCGov+vvAMvso7q@suse.de>
[not found] ` <1f327579-e62a-df65-0763-e88243829db3@linux.alibaba.com>
[not found] ` <YTCsWpSmPYvXa1xz@hirez.programming.kicks-ass.net>
[not found] ` <4c589fef-8c98-a6fc-693f-b205a7710e42@linux.alibaba.com>
[not found] ` <YTC+FTo4uLLdyBxA@hirez.programming.kicks-ass.net>
[not found] ` <YTDS/p/bnsTFzNES@hirez.programming.kicks-ass.net>
2021-09-02 17:05 ` [PATCH 02/24] x86/traps: Move arch/x86/kernel/traps.c to arch/x86/entry/ Nick Desaulniers
2021-09-02 17:19 ` Miguel Ojeda [this message]
2021-09-02 17:23 ` Nick Desaulniers
2021-09-03 7:36 ` Martin Liška
2021-09-07 21:12 ` Nick Desaulniers
2021-09-08 7:33 ` Martin Liška
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='CANiq72=OH0FYLnRfiVt5kjC39bZZsmjsMLCAAfh9iN1KQyzBaw@mail.gmail.com' \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=andrew.cooper3@citrix.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bp@alien8.de \
--cc=brijesh.singh@amd.com \
--cc=bristot@redhat.com \
--cc=clin@suse.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=jiangshanlai@gmail.com \
--cc=jroedel@suse.de \
--cc=laijs@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-toolchains@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=mliska@suse.cz \
--cc=ndesaulniers@google.com \
--cc=nivedita@alum.mit.edu \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).