From: Jakub Kicinski <kuba@kernel.org>
To: torvalds@linux-foundation.org
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, pabeni@redhat.com,
bpf@vger.kernel.org
Subject: Re: [GIT PULL] Networking for v6.5
Date: Tue, 27 Jun 2023 11:59:25 -0700 [thread overview]
Message-ID: <20230627115925.4e55f199@kernel.org> (raw)
In-Reply-To: <20230627184830.1205815-1-kuba@kernel.org>
On Tue, 27 Jun 2023 11:48:30 -0700 Jakub Kicinski wrote:
> WiFi 7 and sendpage changes are the biggest pieces of work for
> this release. The latter will definitely require fixes but
> I think that we got it to a reasonable point.
I forgot to mention a conflict, there's a trivial one because of
adjacent changes in fs/splice.c. Stephen has the resolution:
https://lore.kernel.org/all/20230613125939.595e50b8@canb.auug.org.au/
next prev parent reply other threads:[~2023-06-27 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 18:48 [GIT PULL] Networking for v6.5 Jakub Kicinski
2023-06-27 18:59 ` Jakub Kicinski [this message]
2023-06-28 0:24 ` Jakub Kicinski
2023-06-28 23:58 ` pr-tracker-bot
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=20230627115925.4e55f199@kernel.org \
--to=kuba@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).