From: Andrew Morton <akpm@linux-foundation.org>
To: Alistair Popple <apopple@nvidia.com>
Cc: Shigeru Yoshida <syoshida@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
syzbot+616ff0452fec30f4dcfd@syzkaller.appspotmail.com,
John Hubbard <jhubbard@nvidia.com>
Subject: Re: [PATCH v2] mm/gup.c: Fix return value for __gup_longterm_locked()
Date: Mon, 22 Aug 2022 19:24:06 -0700 [thread overview]
Message-ID: <20220822192406.612a596aa5fecd5e6ff67023@linux-foundation.org> (raw)
In-Reply-To: <8735dnu53w.fsf@nvdebian.thelocal>
On Tue, 23 Aug 2022 11:15:29 +1000 Alistair Popple <apopple@nvidia.com> wrote:
> > Fixes: 61c63c2076d9 (mm/gup.c: simplify and fix check_and_migrate_movable_pages() return codes)
>
> I couldn't find that SHA1, I'm guessing due to rebasing, etc. of
> mm-unstable?
Yup. That's why we include the patch title as well as its hash.
next prev parent reply other threads:[~2022-08-23 2:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 15:37 [PATCH v2] mm/gup.c: Fix return value for __gup_longterm_locked() Shigeru Yoshida
2022-08-23 1:15 ` Alistair Popple
2022-08-23 2:24 ` Andrew Morton [this message]
2022-08-23 9:05 ` Shigeru Yoshida
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=20220822192406.612a596aa5fecd5e6ff67023@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syoshida@redhat.com \
--cc=syzbot+616ff0452fec30f4dcfd@syzkaller.appspotmail.com \
/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