From: Laurent Dufour <ldufour@linux.ibm.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 1/2] mm: replace memmap_context by memplug_context
Date: Tue, 29 Sep 2020 17:31:50 +0200 [thread overview]
Message-ID: <b4e8f0ea-2d4a-eacf-b617-932906cbf1b1@linux.ibm.com> (raw)
In-Reply-To: <20200929142904.GC1203131@kroah.com>
Le 29/09/2020 à 16:29, Greg KH a écrit :
> On Tue, Sep 29, 2020 at 03:57:37PM +0200, Laurent Dufour wrote:
>> Backport version to the 5.4-stable tree of the commit:
>>
>> c1d0da83358a ("mm: replace memmap_context by meminit_context")
>>
>> Cc: <stable@vger.kernel.org> # 5.4.y
>> Signed-off-by: Laurent Dufour <ldufour@linux.ibm.com>
>
> What happened to the full changelog from the original commit, and all of
> the cc: and signed-off-by from it?
>
> Please include that in the patch, you don't want to see all of that
> stripped off, right?
Sorry, I was thinking some magic script was pulling the original commit
description based on the git commit id ;)
I'll send the patches again.
Is there a specific tag to use when mentioning the original commit id?
Thanks,
Laurent.
next prev parent reply other threads:[~2020-09-29 15:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 13:57 [PATCH 1/2] mm: replace memmap_context by memplug_context Laurent Dufour
2020-09-29 13:57 ` [PATCH 2/2] mm: don't rely on system state to detect hot-plug operations Laurent Dufour
2020-09-29 14:29 ` [PATCH 1/2] mm: replace memmap_context by memplug_context Greg KH
2020-09-29 15:31 ` Laurent Dufour [this message]
2020-09-29 16:03 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2020-09-29 14:03 Laurent Dufour
2020-09-29 16:12 Laurent Dufour
2020-09-29 16:22 Laurent Dufour
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=b4e8f0ea-2d4a-eacf-b617-932906cbf1b1@linux.ibm.com \
--to=ldufour@linux.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.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.