From: Jiri Slaby <jirislaby@kernel.org>
To: Christian Lamparter <chunkeey@gmail.com>, linux-wireless@vger.kernel.org
Cc: ansuelsmth@gmail.com, kvalo@kernel.org, mcgrof@kernel.org,
mickflemm@gmail.com, robimarko@gmail.com, toke@toke.dk,
yangshiji66@qq.com, Shiji Yang <yangshiji66@outlook.com>
Subject: Re: [PATCH] wifi: ath: add struct_group for struct ath_cycle_counters
Date: Mon, 5 Jun 2023 08:00:18 +0200 [thread overview]
Message-ID: <92aacacd-b33f-f86a-700c-98fc90b79cbe@kernel.org> (raw)
In-Reply-To: <582d6f32-23f8-6175-19da-f0b4c97393f5@gmail.com>
On 04. 06. 23, 13:11, Christian Lamparter wrote:
> On 6/4/23 03:48, Shiji Yang wrote:
>> Thank you all,
>> This patch may not look so beautiful, but its main purpose is to raise
>> some awareness about this strange compilation warning.
>>
>> This problem only occurs in mips gcc 12.3 (maybe only on arc mips/ath79).
>
> It also occures with PPC464/APM82181. Could it be that that it occurs on
> "big-endian" archs?
Whatever, to me this very looks like a compiler bug.
So NACK to this one for now.
If this still happens on the latest tree (e.g. 6.4-rc) and with gcc 13,
we might need to fix fortify or report to the gcc bugzilla [1] instead
-- attach a preprocessed source there (the output of your make
CROSSblabla=xyz drivers/net/wireless/ath/ath9k/main.i).
[1] https://gcc.gnu.org/bugzilla/enter_bug.cgi
thanks,
--
js
suse labs
prev parent reply other threads:[~2023-06-05 6:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 4:36 [PATCH] wifi: ath: add struct_group for struct ath_cycle_counters Shiji Yang
2023-06-02 4:58 ` Jiri Slaby
2023-06-02 5:19 ` Kalle Valo
2023-06-04 1:46 ` Shiji Yang
2023-06-04 1:40 ` Shiji Yang
2023-06-04 1:48 ` Shiji Yang
2023-06-04 11:11 ` Christian Lamparter
2023-06-05 6:00 ` Jiri Slaby [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=92aacacd-b33f-f86a-700c-98fc90b79cbe@kernel.org \
--to=jirislaby@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=chunkeey@gmail.com \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mickflemm@gmail.com \
--cc=robimarko@gmail.com \
--cc=toke@toke.dk \
--cc=yangshiji66@outlook.com \
--cc=yangshiji66@qq.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