From: Jakub Kicinski <kuba@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, pabeni@redhat.com
Subject: Re: [GIT PULL] Networking for v6.5-rc7
Date: Fri, 18 Aug 2023 12:40:05 -0700 [thread overview]
Message-ID: <20230818124005.20d90a33@kernel.org> (raw)
In-Reply-To: <CAHk-=wi-DdiZu-zMfE3X5nx4i5farupHmJawz-My_Z2nk9Qkow@mail.gmail.com>
On Fri, 18 Aug 2023 06:58:49 +0200 Linus Torvalds wrote:
> > Fixes to fixes:
>
> Heh. New header for an old problem ...
Yeah.. Almost all the "current" fixes are just follow ups to the fixes
we sent after -rc1, I wanted to highlight that somehow. Highlight that
it doesn't feel like we're fixing problems which came in via -next any
more.
next prev parent reply other threads:[~2023-08-18 19:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 22:11 [GIT PULL] Networking for v6.5-rc7 Jakub Kicinski
2023-08-18 4:58 ` Linus Torvalds
2023-08-18 19:40 ` Jakub Kicinski [this message]
2023-08-18 5:18 ` 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=20230818124005.20d90a33@kernel.org \
--to=kuba@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