On Fri, Jul 16, 2021 at 12:04:51PM +0200, David Hildenbrand wrote: > On 16.07.21 06:31, Greg KH wrote: > > On Fri, Jul 16, 2021 at 10:20:45AM +0800, Hanjun Guo wrote: > > > On 2021/7/15 21:07, Greg KH wrote: > > > > On Thu, Jul 15, 2021 at 08:45:47PM +0800, Hanjun Guo wrote: > > > > > Hi Greg, > > > > > > > > > > On 2021/7/15 19:23, gregkh@xxxxxxxxxxxxxxxxxxx wrote: > > > > > > > > > > > > This is a note to let you know that I've just added the patch titled > > > > > > > > > > > > mm,hwpoison: return -EBUSY when migration fails > > > > > > > > > > > > to the 5.10-stable tree which can be found at: > > > > > > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary > > > > > > > > > > > > The filename of the patch is: > > > > > > mm-hwpoison-return-ebusy-when-migration-fails.patch > > > > > > and it can be found in the queue-5.10 subdirectory. > > > > > > > > > > > > If you, or anyone else, feels it should not be added to the stable tree, > > > > > > please let <stable@xxxxxxxxxxxxxxx> know about it. > > > > > [...] > > > > > > > > > > > > From: Oscar Salvador <osalvador@xxxxxxx> > > > > > > > > > > > > commit 3f4b815a439adfb8f238335612c4b28bc10084d8 > > > > > > > > > > Oops, I missed the 'upstream' above, sorry. Could you update it > > > > > in your local tree? > > > > > > > > I'm sorry, I do not understand the context or what to do here. > > > > > > The right commit message is: > > > > > > commit 3f4b815a439adfb8f238335612c4b28bc10084d8 upstream. > > > > > > (original commit message ...) > > > > > > but I missed the 'upstream.' above, the wrong commit message > > > is "commit 3f4b815a439adfb8f238335612c4b28bc10084d8", and > > > the 'upstream.' needs to be added back. > > > > Again, I do not know what you are asking me to do... > > > > https://www.kernel.org/doc/html/v5.14-rc1//process/stable-kernel-rules.html > > documents the format to be > > "commit <sha1> upstream." > > Hanjun Guo seems to be concerned that what he specified is not correct and > the patch might not get applied to stable trees because of that issue. > > But form what I understand, we don't care too much what the string is, as > long as it begins with > > "commit <sha1>" Ah, that makes more sense, sorry for the confusion. I've now fixed it up. greg k-h
