From: Sasha Levin <sashal@kernel.org>
To: Young Hsieh <youngh@uber.com>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: Question for AMD patches
Date: Thu, 17 Dec 2020 15:32:11 -0500 [thread overview]
Message-ID: <20201217203211.GB643756@sasha-vm> (raw)
In-Reply-To: <83E7490A-EFB0-42C2-BD9D-B5E6E5BF440D@uber.com>
On Fri, Dec 18, 2020 at 04:05:45AM +0800, Young Hsieh wrote:
>Hello,
>
>This is Young Hsieh from Uber and currently I am in Uber infra team and in charge of server system design. Nice to e-meet you! :)
>
>We are working on AMD Milan platform with Debian, and notice there are some patches for performance and security improvements, which are not implemented in LTS kernels (4.14/4.19/5.4) yet. On our side, we prefer to use the general LTS kernel release instead of a customized kernel, in case we will not align on major fixes down the road. So would like to know if there is any plan to backport these patches and if so, what is the timeline? Thanks a lot again for any advice.
Easy: use 5.10. It's LTS and has all the patches you care about.
--
Thanks,
Sasha
next prev parent reply other threads:[~2020-12-17 20:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1B44E762-F9F2-4E2B-BFEF-6F032BE8841E@uber.com>
2020-12-17 20:05 ` Question for AMD patches Young Hsieh
2020-12-17 20:32 ` Sasha Levin [this message]
[not found] ` <D69B8685-4410-4839-AB67-A89D77F82203@uber.com>
[not found] ` <DB3DB0E4-4751-4527-B030-40EF0B11F195@uber.com>
2020-12-18 0:03 ` Sasha Levin
2020-12-17 20:35 ` Greg K-H
[not found] ` <380D416C-D23B-4F35-A944-EC3E3A8349C3@uber.com>
2020-12-18 5:51 ` Greg K-H
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=20201217203211.GB643756@sasha-vm \
--to=sashal@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=x86@kernel.org \
--cc=youngh@uber.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