From: Jakub Kicinski <kuba@kernel.org>
To: stable@vger.kernel.org
Subject: [6.5] please apply f5f80e32de12
Date: Tue, 29 Aug 2023 17:49:57 -0700 [thread overview]
Message-ID: <20230829174957.0ae84f41@kernel.org> (raw)
Hi!
Is the queue for 6.5 open already? :)
Please apply commit f5f80e32de12 ("ipv6: remove hard coded limitation
on ipv6_pinfo") to 6.5, it mistakenly went via -next. It's in Linus's
tree now.
Discussions:
https://lore.kernel.org/all/CABq1_viq9yMo9wZ2XkLg_45FaOcwL93qVhqFUZ9wTygKagnszg@mail.gmail.com/
https://lore.kernel.org/netdev/CANn89iLTn6vv9=PvAUccpRNNw6CKcXktixusDpqxqvo+UeLviQ@mail.gmail.com/T/#mb8dca9fc9491cc78fca691e64e601301ec036ce7
Fixes: fe79bd65c819 ("net/tcp: refactor tcp_inet6_sk()")
next reply other threads:[~2023-08-30 0:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 0:49 Jakub Kicinski [this message]
2023-08-31 10:45 ` [6.5] please apply f5f80e32de12 Greg KH
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=20230829174957.0ae84f41@kernel.org \
--to=kuba@kernel.org \
--cc=stable@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 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.