From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Ping-Ke Shih <pkshih@realtek.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Kalle Valo <kvalo@kernel.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-hardening@vger.kernel.org"
<linux-hardening@vger.kernel.org>
Subject: Re: [PATCH][next] wifi: rtw89: coex: Fix -Wstringop-overflow warnings in _append_tdma()
Date: Mon, 13 Nov 2023 19:23:49 -0600 [thread overview]
Message-ID: <192fbb0d-f4f6-4384-98d8-b7422349dafb@embeddedor.com> (raw)
In-Reply-To: <fd0d79048efa47868173c5fd8950b956@realtek.com>
On 11/13/23 18:37, Ping-Ke Shih wrote:
>
>
>> -----Original Message-----
>> From: Gustavo A. R. Silva <gustavoars@kernel.org>
>> Sent: Tuesday, November 14, 2023 3:36 AM
>> To: Ping-Ke Shih <pkshih@realtek.com>; Kalle Valo <kvalo@kernel.org>
>> Cc: linux-wireless@vger.kernel.org; linux-kernel@vger.kernel.org; Gustavo A. R. Silva
>> <gustavoars@kernel.org>; linux-hardening@vger.kernel.org
>> Subject: [PATCH][next] wifi: rtw89: coex: Fix -Wstringop-overflow warnings in _append_tdma()
>>
>> Copy a couple of structures directly, instead of using `memcpy()`.
>>
>
> wireless-next has taken my patch [1] that is identical to yours.
Great!
I had mine ready on Oct 31, but I was waiting for the merge window to close
before sending it.
Glad to see that the issue is fixed already. :)
Thanks
--
Gustavo
>
> [1] https://lore.kernel.org/all/20231102003716.25815-1-pkshih@realtek.com/
>
>
next prev parent reply other threads:[~2023-11-14 1:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 19:35 Gustavo A. R. Silva
2023-11-14 0:37 ` Ping-Ke Shih
2023-11-14 1:23 ` Gustavo A. R. Silva [this message]
2023-11-14 8:03 ` 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=192fbb0d-f4f6-4384-98d8-b7422349dafb@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=gustavoars@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®