From: Greg KH <gregkh@linuxfoundation.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, Kevin Loughlin <kevinloughlin@google.com>,
Borislav Petkov <bp@alien8.de>,
stable@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: FAILED: Patch "x86/sev: Fix position dependent variable references in startup code" failed to apply to 6.8-stable tree
Date: Fri, 29 Mar 2024 12:56:46 +0100 [thread overview]
Message-ID: <2024032916-statue-skyrocket-af59@gregkh> (raw)
In-Reply-To: <CAMj1kXGNneD2E=iGM18DMrAqKySi6JdDF-f-Sd+Vs036-_RL2g@mail.gmail.com>
On Wed, Mar 27, 2024 at 04:39:20PM +0200, Ard Biesheuvel wrote:
> On Wed, 27 Mar 2024 at 14:08, Sasha Levin <sashal@kernel.org> wrote:
> >
> > The patch below does not apply to the 6.8-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
> >
>
> I will send the v6.8 backport separately right away.
>
> v6.7 and v6.6 can take this patch unmodified but will need to take
> 29956748339aa8757a7e2f927a8679dd08f24bb6 as a prerequisite first.
Now done, thanks.
> (v6.8 no longer applies because of the way Linus fixed up a merge
> conflict in the 6.8 cycle)
I fixed this up by hand, hopefully got it right :)
> v6.1 and older need separate backports so i will send those out later.
Wonderful, thanks!
greg k-h
next prev parent reply other threads:[~2024-03-29 11:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 12:08 FAILED: Patch "x86/sev: Fix position dependent variable references in startup code" failed to apply to 6.8-stable tree Sasha Levin
2024-03-27 14:39 ` Ard Biesheuvel
2024-03-29 11:56 ` Greg KH [this message]
2024-03-29 15:25 ` Ard Biesheuvel
2024-03-29 17:56 ` 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=2024032916-statue-skyrocket-af59@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=kevinloughlin@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@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.