From: Borislav Petkov <bp@alien8.de>
To: Bill Wendling <morbo@google.com>
Cc: Juergen Gross <jgross@suse.com>,
"Srivatsa S. Bhat (VMware)" <srivatsa@csail.mit.edu>,
Alexey Makhalov <amakhalov@vmware.com>,
VMware PV-Drivers Reviewers <pv-drivers@vmware.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
llvm@lists.linux.dev
Subject: Re: [PATCH 1/2] x86/paravirt: clean up typos and grammaros
Date: Sat, 3 Sep 2022 06:28:22 +0200 [thread overview]
Message-ID: <YxLX5i0aUoe9zBsx@nazgul.tnic> (raw)
In-Reply-To: <20220902213750.1124421-2-morbo@google.com>
On Fri, Sep 02, 2022 at 09:37:49PM +0000, Bill Wendling wrote:
> Drive-by clean up of the comment.
>
> [ Impact: cleanup]
We used to do that type of "impact" tagging years ago but we stopped.
Where did you dig this out from?
:)
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: Bill Wendling <morbo@google.com>
Cc: Juergen Gross <jgross@suse.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
VMware PV-Drivers Reviewers <pv-drivers@vmware.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Nick Desaulniers <ndesaulniers@google.com>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Nathan Chancellor <nathan@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
llvm@lists.linux.dev, Alexey Makhalov <amakhalov@vmware.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 1/2] x86/paravirt: clean up typos and grammaros
Date: Sat, 3 Sep 2022 06:28:22 +0200 [thread overview]
Message-ID: <YxLX5i0aUoe9zBsx@nazgul.tnic> (raw)
In-Reply-To: <20220902213750.1124421-2-morbo@google.com>
On Fri, Sep 02, 2022 at 09:37:49PM +0000, Bill Wendling wrote:
> Drive-by clean up of the comment.
>
> [ Impact: cleanup]
We used to do that type of "impact" tagging years ago but we stopped.
Where did you dig this out from?
:)
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2022-09-03 4:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 21:37 [PATCH 0/2] fix clobbers list with ZERO_CALL_USED_REGS feature Bill Wendling
2022-09-02 21:37 ` [PATCH 1/2] x86/paravirt: clean up typos and grammaros Bill Wendling
2022-09-03 4:28 ` Borislav Petkov [this message]
2022-09-03 4:28 ` Borislav Petkov
2022-09-04 2:13 ` Bill Wendling
2022-09-02 21:37 ` [PATCH 2/2] x86/paravirt: add extra clobbers with ZERO_CALL_USED_REGS enabled Bill Wendling
2022-09-03 7:18 ` Kees Cook
2022-09-03 7:18 ` Kees Cook
2022-09-05 6:02 ` Bill Wendling
2022-09-07 6:00 ` Nick Desaulniers
2022-09-07 6:00 ` Nick Desaulniers via Virtualization
2022-09-07 8:50 ` Peter Zijlstra
2022-09-07 8:50 ` Peter Zijlstra
2022-09-07 23:10 ` Kees Cook
2022-09-07 23:10 ` Kees Cook
2022-09-08 21:16 ` Bill Wendling
2022-09-14 14:40 ` Nathan Chancellor
2022-09-14 15:49 ` Bill Wendling
[not found] ` <20220914162149.71271-1-morbo@google.com>
2022-09-15 6:59 ` [PATCH v2 1/1] x86/paravirt: write paravirt ident function in assembly Juergen Gross via Virtualization
2022-09-15 6:59 ` Juergen Gross
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=YxLX5i0aUoe9zBsx@nazgul.tnic \
--to=bp@alien8.de \
--cc=amakhalov@vmware.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mingo@redhat.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=pv-drivers@vmware.com \
--cc=srivatsa@csail.mit.edu \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.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 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.