From: Kalle Valo <kvalo@kernel.org>
To: "Arnd Bergmann" <arnd@arndb.de>
Cc: "Arnd Bergmann" <arnd@kernel.org>,
"Ping-Ke Shih" <pkshih@realtek.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
"Ching-Te Ku" <ku920601@realtek.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rtw89: avoid stringop-overflow warning
Date: Tue, 12 Dec 2023 16:23:49 +0200 [thread overview]
Message-ID: <87plzbo5xm.fsf@kernel.org> (raw)
In-Reply-To: <f39d5940-2030-4378-9a44-3355a4429e31@app.fastmail.com> (Arnd Bergmann's message of "Thu, 07 Dec 2023 17:11:06 +0100")
"Arnd Bergmann" <arnd@arndb.de> writes:
> On Thu, Dec 7, 2023, at 16:47, Kalle Valo wrote:
>> Arnd Bergmann <arnd@kernel.org> wrote:
>>> From: Arnd Bergmann <arnd@arndb.de>
>>>
>>> Fixes: 89741e7e42f6 ("Makefile: Enable -Wstringop-overflow globally")
>>> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>>
>> ERROR: 'wifi:' prefix missing: '[PATCH] rtw89: avoid stringop-overflow
>> warning'
>> ERROR: Failed to find commit id: Fixes: 89741e7e42f6 ("Makefile: Enable
>> -Wstringop-overflow globally")
>>
>> I can add the "wifi:" prefix but where can I find the commit 89741e7e42f6?
>
> It's in linux-next and came in from Gustavo's tree at
> https://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux.git/log/?h=for-next/kspp
Ah, I think then I'll drop the Fixes tag to avoid warnings or reports.
My understanding is that a commit in the Fixes tag should be a parent.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-12-12 14:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 7:30 [PATCH] rtw89: avoid stringop-overflow warning Arnd Bergmann
2023-12-05 0:26 ` Ping-Ke Shih
2023-12-07 15:47 ` Kalle Valo
2023-12-07 16:11 ` Arnd Bergmann
2023-12-12 14:23 ` Kalle Valo [this message]
2023-12-12 15:11 ` wifi: " Kalle Valo
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=87plzbo5xm.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=gustavoars@kernel.org \
--cc=ku920601@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.