From: Brendan Jackman <jackmanb@google.com>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
Lai Jiangshan <laijs@linux.alibaba.com>,
Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org, Kevin Cheng <chengkev@google.com>,
Yosry Ahmed <yosryahmed@google.com>
Subject: Re: [tip: x86/entry] x86/entry: Avoid redundant CR3 write on paranoid returns
Date: Mon, 19 Feb 2024 15:51:27 +0100 [thread overview]
Message-ID: <CA+i-1C10TjwEKEYoV636PPXJZpQDvbLqETVzA=rjgsU-Dvucmw@mail.gmail.com> (raw)
In-Reply-To: <20240219144210.GDZdNowiz8Tr9j8acY@fat_crate.local>
Ah yep, it's there. Checked my history, I was looking in the wrong
branch. Thanks for the correction.
On Mon, 19 Feb 2024 at 15:42, Borislav Petkov <bp@alien8.de> wrote:
>
> On Mon, Feb 19, 2024 at 11:49:46AM +0100, Brendan Jackman wrote:
> > [Apologies if you see this as a duplicate, accidentally sent the
> > original in HTML, please disregard the other one]
> >
> > Hi Thomas,
> >
> > I have just noticed that the commit has disappeared from
> > tip/x86/entry. Is that deliberate?
>
> $ git fetch tip
> $ git log -1 --oneline tip/x86/entry
> bb998361999e (refs/remotes/tip/x86/entry) x86/entry: Avoid redundant CR3 write on paranoid returns
>
> Looks there to me. :)
>
> --
> Regards/Gruss,
> Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2024-02-19 14:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 11:39 [PATCH v3 RESEND] x86/entry: Avoid redundant CR3 write on paranoid returns Brendan Jackman
2024-01-23 5:33 ` Yosry Ahmed
2024-01-24 18:36 ` [tip: x86/entry] " tip-bot2 for Lai Jiangshan
2024-02-19 10:49 ` Brendan Jackman
2024-02-19 14:42 ` Borislav Petkov
2024-02-19 14:51 ` Brendan Jackman [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='CA+i-1C10TjwEKEYoV636PPXJZpQDvbLqETVzA=rjgsU-Dvucmw@mail.gmail.com' \
--to=jackmanb@google.com \
--cc=bp@alien8.de \
--cc=chengkev@google.com \
--cc=laijs@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yosryahmed@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 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.