From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Christopher Lameter <cl@linux.com>,
Dennis Zhou <dennis@kernel.org>,
Ben Dooks <ben.dooks@codethink.co.uk>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
Tejun Heo <tj@kernel.org>, Nicholas Piggin <npiggin@gmail.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] fix __percpu annotation in asm-generic
Date: Tue, 24 Mar 2020 07:44:52 +0100 [thread overview]
Message-ID: <20200324064452.zsnpcvihgeyegtmu@ltop.local> (raw)
In-Reply-To: <20200324041347.GA186169@zx2c4.com>
On Mon, Mar 23, 2020 at 10:13:47PM -0600, Jason A. Donenfeld wrote:
> On Sat, Nov 30, 2019 at 01:00:37AM +0100, Luc Van Oostenryck wrote:
> > Note: it would be much much nicer to do all these type generic
> > macros with '__auto_type' (only supported in GCC 4.9 IIUC
> > and supported in sparse but it shouldn't be very hard to do)..
>
> I'm curious to know if you know why we're not using __auto_type. Because
> we're stuck on gcc 4.6, or is there a more subtle reason?
I suppose. I don't remember having ever seen a discussion on the
subject (other than a simple remark like "it would be simpler
with __auto_type").
Mainline Sparse doesn't support it but I've a pending series for it
that seems to work well.
-- Luc
prev parent reply other threads:[~2020-03-24 6:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 20:06 [PATCH] fix __percpu annotation in asm-generic Luc Van Oostenryck
2019-11-26 20:06 ` Luc Van Oostenryck
2019-11-27 15:55 ` Christopher Lameter
2019-11-27 15:55 ` Christopher Lameter
2019-11-27 17:53 ` Dennis Zhou
2019-11-27 17:53 ` Dennis Zhou
2019-11-27 22:54 ` Luc Van Oostenryck
2019-11-27 22:54 ` Luc Van Oostenryck
2019-11-29 18:11 ` Christopher Lameter
2019-11-29 18:11 ` Christopher Lameter
2019-11-30 0:00 ` Luc Van Oostenryck
2019-11-30 0:00 ` Luc Van Oostenryck
2019-12-02 19:07 ` Dennis Zhou
2019-12-02 19:07 ` Dennis Zhou
2019-12-02 19:42 ` Christopher Lameter
2019-12-02 19:42 ` Christopher Lameter
2019-12-03 3:01 ` Luc Van Oostenryck
2019-12-03 3:01 ` Luc Van Oostenryck
2020-03-24 4:13 ` Jason A. Donenfeld
2020-03-24 6:44 ` Luc Van Oostenryck [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=20200324064452.zsnpcvihgeyegtmu@ltop.local \
--to=luc.vanoostenryck@gmail.com \
--cc=Jason@zx2c4.com \
--cc=arnd@arndb.de \
--cc=ben.dooks@codethink.co.uk \
--cc=cl@linux.com \
--cc=dennis@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=tj@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