[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210716095243.GA12505@amd>
Date: Fri, 16 Jul 2021 11:52:43 +0200
From: Pavel Machek <pavel@....cz>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
Oscar Salvador <osalvador@...e.de>,
Naoya Horiguchi <naoya.horiguchi@....com>,
Vlastimil Babka <vbabka@...e.cz>,
David Hildenbrand <david@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Hanjun Guo <guohanjun@...wei.com>
Subject: Re: [PATCH 5.10 140/215] mm,hwpoison: return -EBUSY when migration
fails
Hi!
> From: Oscar Salvador <osalvador@...e.de>
>
> commit 3f4b815a439adfb8f238335612c4b28bc10084d8
Another format of marking upstream commits. How are this is number 8
or so. I have scripts trying to parse this, and I don't believe I'm
the only one.
> Link: https://lkml.kernel.org/r/20201209092818.30417-1-osalvador@suse.de
> Signed-off-by: Oscar Salvador <osalvador@...e.de>
> Acked-by: Naoya Horiguchi <naoya.horiguchi@....com>
> Acked-by: Vlastimil Babka <vbabka@...e.cz>
> Cc: David Hildenbrand <david@...hat.com>
> Signed-off-by: Andrew Morton <akpm@...ux-foundation.org>
> Signed-off-by: Linus Torvalds <torvalds@...ux-foundation.org>
Could se simply place Upstream: <hash> tag here? That should
discourage such "creativity"... plus it will make it clear who touched
patch in mainline context and who in stable context.
Best regards,
Pavel
--
http://www.livejournal.com/~pavelmachek
Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)
Powered by blists - more mailing lists