linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
	Masahiro Yamada <masahiroy@kernel.org>
Cc: Albert Ou <aou@eecs.berkeley.edu>, Arnd Bergmann <arnd@arndb.de>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Miguel Ojeda <ojeda@kernel.org>,
	Paul Mackerras <paulus@samba.org>,
	linux-riscv@lists.infradead.org, linuxppc-dev@lists.ozlabs.org,
	Will Deacon <will@kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] Raise the minimum GCC version to 5.2
Date: Sat, 1 May 2021 19:38:14 +0200	[thread overview]
Message-ID: <2ecdbfed-82c4-b0cb-85dc-857b3b06b353@csgroup.eu> (raw)
In-Reply-To: <CANiq72k1hB3X6+Nc_iu=f=BoB-F9JW2j_B4ZMcv8_UpW5QQ2Og@mail.gmail.com>



Le 01/05/2021 à 17:52, Miguel Ojeda a écrit :
> On Sat, May 1, 2021 at 5:17 PM Masahiro Yamada <masahiroy@kernel.org> wrote:
>>
>> More cleanups will be possible as follow-up patches, but this one must
>> be agreed and applied to the mainline first.
> 
> +1 This will allow me to remove the __has_attribute hack in
> include/linux/compiler_attributes.h.
> 
> Reviewed-by: Miguel Ojeda <ojeda@kernel.org>
> 

On powerpc this will allow us to remove commit https://github.com/linuxppc/linux/commit/592bbe9c505d

Reviewed-by: Christophe Leroy <christophe.leroy@csgroup.eu>

Christophe

  reply	other threads:[~2021-05-01 17:50 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-01 15:15 [PATCH] Raise the minimum GCC version to 5.2 Masahiro Yamada
2021-05-01 15:52 ` Miguel Ojeda
2021-05-01 17:38   ` Christophe Leroy [this message]
2021-05-02  2:41   ` Joe Perches
2021-05-02 18:30     ` Segher Boessenkool
2021-05-02 20:00       ` Joe Perches
2021-05-02 20:32         ` Segher Boessenkool
2021-05-02 21:05           ` Ali Kaasinen
2021-05-02 21:08           ` Linus Torvalds
2021-05-02 22:30             ` Matthew Wilcox
2021-05-03  7:34               ` Alexander Dahl
2021-05-03  8:54                 ` Joe Perches
2021-05-03  9:25                 ` Arnd Bergmann
2021-05-03 12:20                   ` David Laight
2021-05-03 13:10                     ` Miguel Ojeda
2021-05-04  5:30                   ` Alexander Dahl
2021-05-04  6:33                     ` Christophe Leroy
2021-05-04 12:07                     ` Arnd Bergmann
2021-05-04 13:25                   ` Andy Shevchenko
2021-05-03 11:35               ` Arnd Bergmann
2021-05-03  9:49             ` Kirill A. Shutemov
2021-05-02 21:23           ` Joe Perches
2021-05-03  0:44             ` Segher Boessenkool
2021-05-03  9:57               ` Arnd Bergmann
2021-05-04  7:56     ` Ben Dooks
2021-05-04  8:38       ` Miguel Ojeda
2021-05-04  9:22         ` Michal Suchánek
2021-05-04 12:09           ` Miguel Ojeda
2021-05-04 12:17             ` Michal Suchánek
2021-05-04 12:26               ` Christophe Leroy
2021-05-02 18:37 ` Segher Boessenkool
2021-05-03  6:16 ` Christophe Leroy
2021-05-04  2:13   ` Masahiro Yamada
2021-05-04 13:18   ` Andy Shevchenko
2021-05-03 12:27 ` David Sterba
2021-05-15  7:14 ` Pavel Machek
2021-05-15  7:27   ` Joe Perches

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=2ecdbfed-82c4-b0cb-85dc-857b3b06b353@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=aou@eecs.berkeley.edu \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=masahiroy@kernel.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=ojeda@kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=paulus@samba.org \
    --cc=torvalds@linux-foundation.org \
    --cc=will@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).