From: John Hubbard <jhubbard@nvidia.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: <linux-next@vger.kernel.org>, <akpm@linux-foundation.org>,
<borntraeger@de.ibm.com>, <david@redhat.com>,
<aarcange@redhat.com>, <linux-mm@kvack.org>,
<frankja@linux.ibm.com>, <sfr@canb.auug.org.au>,
<linux-kernel@vger.kernel.org>, <linux-s390@vger.kernel.org>,
Jan Kara <jack@suse.cz>,
"Kirill A. Shutemov" <kirill@shutemov.name>
Subject: Re: [RFC v1 1/2] mm/gup: fixup for 9947ea2c1e608e32 "mm/gup: track FOLL_PIN pages"
Date: Sat, 29 Feb 2020 12:09:15 -0800 [thread overview]
Message-ID: <a48a6fee-babe-45fd-5ff5-881fbdabf79b@nvidia.com> (raw)
In-Reply-To: <20200229115119.3562c73e@p-imbrenda>
On 2/29/20 2:51 AM, Claudio Imbrenda wrote:
> my idea was that my patch should be used as fix-up, so the actual
> content of the commit message is not relevant
>
aha, OK. Yes, a fixup would be nice.
thanks,
--
John Hubbard
NVIDIA
next prev parent reply other threads:[~2020-02-29 20:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 15:43 [RFC v1 0/2] add callbacks for inaccessible pages Claudio Imbrenda
2020-02-28 15:43 ` [RFC v1 1/2] fixup for 9947ea2c1e608e32669d5caeb67b3e3fba3309e8 "mm/gup: track FOLL_PIN pages" Claudio Imbrenda
2020-02-28 15:45 ` Claudio Imbrenda
2020-02-28 15:43 ` [RFC v1 1/2] mm/gup: fixup for 9947ea2c1e608e32 " Claudio Imbrenda
2020-02-28 23:08 ` John Hubbard
2020-02-29 10:51 ` Claudio Imbrenda
2020-02-29 20:09 ` John Hubbard [this message]
2020-03-02 13:46 ` Michal Hocko
2020-02-28 15:43 ` [RFC v1 2/2] mm/gup/writeback: add callbacks for inaccessible pages Claudio Imbrenda
2020-02-28 16:08 ` Christian Borntraeger
2020-02-29 0:08 ` John Hubbard
2020-02-29 10:49 ` Claudio Imbrenda
2020-02-29 20:07 ` John Hubbard
2020-03-01 3:47 ` Andrew Morton
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=a48a6fee-babe-45fd-5ff5-881fbdabf79b@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=jack@suse.cz \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).