From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Aithal, Srikanth" <sraithal@amd.com>,
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: Thu, 30 Nov 2023 15:54:57 -0600 [thread overview]
Message-ID: <402fc89f-96ff-4f64-ad6d-aaa7ecc284e7@embeddedor.com> (raw)
In-Reply-To: <001021e0-2262-49c8-89d0-c0d0720ca313@embeddedor.com>
Hi Stephen,
On 11/28/23 15:11, Gustavo A. R. Silva wrote:
> Hi Stephen,
>
> On 11/27/23 16:13, Stephen Rothwell wrote:
>> Hi Gustavo,
>>
>> On Wed, 22 Nov 2023 10:21:27 +0530 "Aithal, Srikanth" <sraithal@amd.com> wrote:
>>>
>>> @Gustavo I see you have mentioned it as gcc issue. I was not hitting this until yesterdays linux-next build. I am on latest gcc which RHEL 9.x provides,
>>> gcc --version
>>> gcc (GCC) 11.4.1 20230605 (Red Hat 11.4.1-2)
>>
>> Given that gcc 11 is a provided compiler on RHEL 9, can you not add
>> -Wstringop-overflow for that compiler, please.
Done:
https://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux.git/commit/?h=for-next/kspp&id=617ab3c357d2ebdfff0e1a090c46f2f3f29b45e2
Thanks!
--
Gustavo
>
>
> Sure thing. Working on that. :)
>
> --
> Gustavo
>
next prev parent reply other threads:[~2023-11-30 21:55 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
[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 [this message]
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=402fc89f-96ff-4f64-ad6d-aaa7ecc284e7@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sraithal@amd.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).