From: Greg KH <gregkh@linuxfoundation.org>
To: Srinivasa Srikanth Podila <srinivasa-srikanth.podila@broadcom.com>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
vannapurve@google.com, Mukul Sinha <mukul.sinha@broadcom.com>,
Ramana Reddy <ramana.reddy@broadcom.com>
Subject: Re: Regarding linux kernel commit 805e3ce5e0e32b31dcecc0774c57c17a1f13cef6
Date: Tue, 12 Aug 2025 13:58:57 +0200 [thread overview]
Message-ID: <2025081231-boxer-footsie-7800@gregkh> (raw)
In-Reply-To: <CAGhJvC47-ku9-72pDwVu_2iuROfLGchZVtmofWeJoN0wV7yBPg@mail.gmail.com>
On Tue, Aug 12, 2025 at 05:11:01PM +0530, Srinivasa Srikanth Podila wrote:
> Hello,
>
> I have come across the linux kernel
> commit 805e3ce5e0e32b31dcecc0774c57c17a1f13cef6 merged into the 6.15 kernel.
>
> Kernel Commit:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=805e3ce5e0e32b31dcecc0774c57c17a1f13cef6
>
> Currently, we need this fix into the latest 6.8 based kernel as our servers
> are all based on Ubuntu 24.04 with 6.8 based kernels. Please let us know
> the process for the same.
>
> Could you please help in this regard. Any help on this would be greatly
> appreciated.
As per the front page of kernel.org, the 6.8.y kernel is long
end-of-life and not supported by us at all. If you are relying on a
distro to provide a specific kernel version for you, please contact them
as you are paying for that service from them already, there's nothing
that we can do about that for obvious reasons.
hope this helps,
greg k-h
prev parent reply other threads:[~2025-08-12 11:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 11:41 Regarding linux kernel commit 805e3ce5e0e32b31dcecc0774c57c17a1f13cef6 Srinivasa Srikanth Podila
2025-08-12 11:58 ` Greg KH [this message]
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=2025081231-boxer-footsie-7800@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mukul.sinha@broadcom.com \
--cc=ramana.reddy@broadcom.com \
--cc=srinivasa-srikanth.podila@broadcom.com \
--cc=stable@vger.kernel.org \
--cc=vannapurve@google.com \
/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