From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Kees Cook <kees@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
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: Mon, 12 May 2025 21:32:42 -0400 [thread overview]
Message-ID: <yq1frh9s3e8.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <202505090931.3467A425@keescook> (Kees Cook's message of "Fri, 9 May 2025 09:32:54 -0700")
Hi Kees,
>> d897dae472f2 ("scsi: qedf: Use designated initializer for struct qed_fcoe_cb_ops")
>>
>> in the scsi-mkp tree.
>
> Yeah, I am carrying this and the qede patch since I need them for a
> clean build in my tree. I might need to split my merge window into two
> halves if I need to drop the duplicates.
I can just drop it. Your change won't conflict with anything currently
in the SCSI pipeline for 6.16.
--
Martin K. Petersen
next prev parent reply other threads:[~2025-05-13 1:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 8:48 linux-next: duplicate patch in the kspp tree Stephen Rothwell
2025-05-09 16:32 ` Kees Cook
2025-05-13 1:32 ` Martin K. Petersen [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-26 7:52 Stephen Rothwell
2025-04-22 9:44 Stephen Rothwell
2025-04-22 15:51 ` Kees Cook
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 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=yq1frh9s3e8.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=kees@kernel.org \
--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 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.