From: Juergen Gross <jgross@suse.com>
To: Borislav Petkov <bp@suse.de>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] x86/paravirt for 6.1
Date: Tue, 4 Oct 2022 16:24:18 +0200 [thread overview]
Message-ID: <9654aa58-2e1b-88b0-0165-fff39ba7b953@suse.com> (raw)
In-Reply-To: <Yzw/1M8lEiLriU57@zn.tnic>
[-- Attachment #1.1.1: Type: text/plain, Size: 1213 bytes --]
On 04.10.22 16:14, Borislav Petkov wrote:
> Hi Linus,
>
> please pull a single paravirt ops fix for 6.1.
>
> Thx.
>
> ---
>
> The following changes since commit 521a547ced6477c54b4b0cc206000406c221b4d6:
>
> Linux 6.0-rc6 (2022-09-18 13:44:14 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_paravirt_for_v6.1_rc1
>
> for you to fetch changes up to f92ff8f5dca2acfa475842c71212657b0703c3be:
>
> x86/paravirt: Ensure proper alignment (2022-09-21 12:30:16 +0200)
>
> ----------------------------------------------------------------
> - Ensure paravirt patching site descriptors are aligned properly so that
> code can do proper arithmetic with their addresses
>
> ----------------------------------------------------------------
> Thomas Gleixner (1):
> x86/paravirt: Ensure proper alignment
>
> arch/x86/include/asm/paravirt.h | 1 +
> arch/x86/include/asm/paravirt_types.h | 1 +
> 2 files changed, 2 insertions(+)
>
Hmm, any reason why
https://lore.kernel.org/lkml/20220903073706.3193746-1-keescook@chromium.org/
isn't part of that pull request?
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3149 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2022-10-04 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 14:14 Borislav Petkov
2022-10-04 14:24 ` Juergen Gross [this message]
2022-10-04 14:32 ` Borislav Petkov
2022-10-04 17:34 ` 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=9654aa58-2e1b-88b0-0165-fff39ba7b953@suse.com \
--to=jgross@suse.com \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®