From: Kees Cook <kees@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Greg KH <greg@kroah.com>, Arnd Bergmann <arnd@arndb.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the kspp tree
Date: Tue, 22 Apr 2025 08:51:05 -0700 [thread overview]
Message-ID: <202504220850.F5647C68@keescook> (raw)
In-Reply-To: <20250422194458.074ed355@canb.auug.org.au>
On Tue, Apr 22, 2025 at 07:44:58PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in the char-misc tree as a different commit
> (but the same patch):
>
> e166ec7e7164 ("misc: bcm-vk: avoid -Wflex-array-member-not-at-end warning")
>
> This is commit
>
> e1ee28b12675 ("misc: bcm-vk: avoid -Wflex-array-member-not-at-end warning")
>
> in the char-misc tree.
Thanks! I will drop the one in my tree.
--
Kees Cook
next prev parent reply other threads:[~2025-04-22 15:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 9:44 linux-next: duplicate patch in the kspp tree Stephen Rothwell
2025-04-22 15:51 ` Kees Cook [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-26 7:52 Stephen Rothwell
2025-05-09 8:48 Stephen Rothwell
2025-05-09 16:32 ` Kees Cook
2025-05-13 1:32 ` Martin K. Petersen
2024-11-04 5:42 Stephen Rothwell
2024-11-04 6:41 ` Andrew Morton
2024-07-08 8:24 Stephen Rothwell
2024-07-08 19:20 ` Kees Cook
2024-02-28 3:02 Stephen Rothwell
2024-02-28 3:26 ` Kees Cook
2024-01-04 3:23 Stephen Rothwell
2024-01-04 3:26 ` Stephen Rothwell
2023-06-05 2:34 Stephen Rothwell
2023-06-01 2:30 Stephen Rothwell
2023-06-01 2:43 ` Kees Cook
2023-06-01 4:12 ` Andrew Morton
2023-01-17 4:02 Stephen Rothwell
2023-01-17 13:52 ` Karol Herbst
2023-01-17 20:56 ` Stephen Rothwell
2023-01-18 20:38 ` Kees Cook
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=202504220850.F5647C68@keescook \
--to=kees@kernel.org \
--cc=arnd@arndb.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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