[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1d85ad0b-8f3f-4ab1-810f-0b5357f561ab@redhat.com>
Date: Tue, 3 Jun 2025 10:30:05 +0200
From: Paolo Abeni <pabeni@...hat.com>
To: "Jason A. Donenfeld" <Jason@...c4.com>, netdev@...r.kernel.org,
kuba@...nel.org
Subject: Re: [PATCH net-next 0/1] wireguard updates for 6.16, part 2, late
On 6/3/25 10:25 AM, Paolo Abeni wrote:
> On 5/30/25 5:04 AM, Jason A. Donenfeld wrote:
>> This one patch missed the cut off of the series I sent last week for
>> net-next. It's a oneliner, almost trivial, and I suppose it could be a
>> "net" patch, but we're still in the merge window. I was hoping that if
>> you're planning on doing a net-next part 2 pull, you might include this.
>> If not, I'll send it later in 6.16 as a "net" patch.
>
> We usually (always AFAIR) send a single PR for net-next, mostly because
> there is no additional material due to net-next being closed in the
> merge window.
>
> Anyhow I can apply directly this patch to the net tree and it will be
> included in this week net PR.
I'm sorry, I rushed my reply a bit. Could you please provide a suitable
Fixes: tag for this patch?
Thanks,
Paolo
Powered by blists - more mailing lists