From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kees Cook <keescook@chromium.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
DRI <dri-devel@lists.freedesktop.org>,
Karol Herbst <kherbst@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: duplicate patch in the kspp tree
Date: Tue, 17 Jan 2023 15:02:12 +1100 [thread overview]
Message-ID: <20230117150212.3d8ee843@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 396 bytes --]
Hi all,
The following commit is also in the drm-misc tree as a different commit
(but the same patch):
06b19f46455c ("drm/nouveau/fb/ga102: Replace zero-length array of trailing structs with flex-array")
This is commit
54d47689c6e3 ("drm/nouveau/fb/ga102: Replace zero-length array of trailing structs with flex-array")
in the drm-misc tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-01-17 4:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 4:02 Stephen Rothwell [this message]
2023-01-17 13:52 ` linux-next: duplicate patch in the kspp tree Karol Herbst
2023-01-17 20:56 ` Stephen Rothwell
2023-01-18 20:38 ` Kees Cook
-- strict thread matches above, loose matches on Subject: below --
2023-06-01 2:30 Stephen Rothwell
2023-06-01 2:43 ` Kees Cook
2023-06-01 4:12 ` Andrew Morton
2023-06-05 2:34 Stephen Rothwell
2024-01-04 3:23 Stephen Rothwell
2024-01-04 3:26 ` Stephen Rothwell
2024-02-28 3:02 Stephen Rothwell
2024-02-28 3:26 ` Kees Cook
2024-07-08 8:24 Stephen Rothwell
2024-07-08 19:20 ` Kees Cook
2024-11-04 5:42 Stephen Rothwell
2024-11-04 6:41 ` Andrew Morton
2025-04-22 9:44 Stephen Rothwell
2025-04-22 15:51 ` Kees Cook
2025-05-09 8:48 Stephen Rothwell
2025-05-09 16:32 ` Kees Cook
2025-05-13 1:32 ` Martin K. Petersen
2025-05-26 7:52 Stephen Rothwell
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=20230117150212.3d8ee843@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=keescook@chromium.org \
--cc=kherbst@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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