public inbox for [email protected]
 help / color / mirror / Atom feed
From: Ammar Faizi <[email protected]>
To: Borislav Petkov <[email protected]>
Cc: Thomas Gleixner <[email protected]>,
	Alviro Iskandar Setiawan <[email protected]>,
	Alviro Iskandar Setiawan <[email protected]>,
	Dave Hansen <[email protected]>,
	Greg Kroah-Hartman <[email protected]>,
	"H. Peter Anvin" <[email protected]>, Ingo Molnar <[email protected]>,
	Tony Luck <[email protected]>,
	Yazen Ghannam <[email protected]>,
	[email protected], [email protected],
	[email protected], [email protected], [email protected],
	David Laight <[email protected]>,
	Jiri Hladky <[email protected]>
Subject: Re: [PATCH v5 1/2] x86/delay: Fix the wrong asm constraint in `delay_loop()`
Date: Mon, 28 Mar 2022 11:16:42 +0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 3/28/22 4:38 AM, Borislav Petkov wrote:
> All those Ccs in the commit message are not really needed -
> get_maintainers.pl gives the correct list already.
> 
>> Cc: [email protected] # v2.6.27+
> 
> I don't see the need for the stable Cc. Or do you have a case where
> a corruption really does happen?
> 
>> Fixes: e01b70ef3eb ("x86: fix bug in arch/i386/lib/delay.c file, delay_loop function")
> 
> Commit sha1 (e01b70ef3eb) needs to be at least 12 chars long:
> 
> e01b70ef3eb3 ("x86: fix bug in arch/i386/lib/delay.c file, delay_loop function")
> 
> This is best fixed by doing:
> 
> [core]
>          abbrev = 12
> 
> in your .git/config

Will fix that in the v6.

-- 
Ammar Faizi

  reply	other threads:[~2022-03-28  4:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10  1:53 [PATCH v5 0/2] Two x86 fixes Ammar Faizi
2022-03-10  1:53 ` [PATCH v5 1/2] x86/delay: Fix the wrong asm constraint in `delay_loop()` Ammar Faizi
2022-03-27 21:38   ` Borislav Petkov
2022-03-28  4:16     ` Ammar Faizi [this message]
2022-03-28  4:29     ` Ammar Faizi
2022-03-28  7:56       ` Borislav Petkov
2022-03-10  1:53 ` [PATCH v5 2/2] x86/MCE/AMD: Fix memory leak when `threshold_create_bank()` fails Ammar Faizi
2022-03-27 22:52   ` Borislav Petkov
2022-03-28  4:12     ` Ammar Faizi
2022-03-28  8:05       ` Borislav Petkov
2022-03-17  8:19 ` [PATCH v5 0/2] Two x86 fixes Ammar Faizi
2022-03-17  9:27   ` Borislav Petkov
2022-03-17  9:50     ` Ammar Faizi

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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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