public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the kspp-gustavo tree
Date: Wed, 22 Nov 2023 16:15:44 +1100	[thread overview]
Message-ID: <20231122161544.7a7b8c13@canb.auug.org.au> (raw)
In-Reply-To: <7e58f7a0-440f-4067-87e2-381f05bfce2b@embeddedor.com>

[-- Attachment #1: Type: text/plain, Size: 359 bytes --]

Hi Gustavo,

On Tue, 21 Nov 2023 22:04:17 -0600 "Gustavo A. R. Silva" <gustavo@embeddedor.com> wrote:
>
> This doesn't show up with more recent compilers because it was an issue in GCC.

Sure, but we do still support gcc back to v5.1 .. are there other
earlier versions where you may want to suppress these warnings?

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2023-11-22  5:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22  3:48 linux-next: build warnings after merge of the kspp-gustavo tree Stephen Rothwell
2023-11-22  4:04 ` Gustavo A. R. Silva
2023-11-22  5:15   ` Stephen Rothwell [this message]
     [not found]     ` <bbde1882-9124-408c-9f59-de3de66bfc56@embeddedor.com>
2023-11-24 19:07       ` Gustavo A. R. Silva
2023-11-22  4:51 ` Aithal, Srikanth
2023-11-24  1:23   ` Gustavo A. R. Silva
2023-11-27 22:13   ` Stephen Rothwell
2023-11-28 21:11     ` Gustavo A. R. Silva
2023-11-30 21:54       ` Gustavo A. R. Silva
2023-11-30 22:10         ` Stephen Rothwell
2023-12-01  8:40         ` Aithal, Srikanth

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=20231122161544.7a7b8c13@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=gustavo@embeddedor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.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