From: Andrew Morton <akpm@linux-foundation.org>
To: Andreas Gruenbacher <agruenba@redhat.com>
Cc: Baoquan He <bhe@redhat.com>,
gfs2@lists.linux.dev, linux-mm@kvack.org, david@redhat.com,
osalvador@suse.de, yanjun.zhu@linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/4] mm/gup: fix wrongly calculated returned value in fault_in_safe_writeable()
Date: Fri, 11 Apr 2025 16:22:15 -0700 [thread overview]
Message-ID: <20250411162215.e7b102cf432e7de885b0eec7@linux-foundation.org> (raw)
In-Reply-To: <CAHc6FU7B5ORy-97OegzZ939MjuZWdBicLjRxj_bYmG3Hm1mKSA@mail.gmail.com>
On Fri, 11 Apr 2025 17:07:32 +0200 Andreas Gruenbacher <agruenba@redhat.com> wrote:
> Can this fix please be sent to Linus for inclusion into 6.15?
Sure, I made the adjustments.
next prev parent reply other threads:[~2025-04-11 23:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 3:57 [PATCH v4 0/4] mm/gup: Minor fix, cleanup and improvements Baoquan He
2025-04-10 3:57 ` [PATCH v4 1/4] mm/gup: fix wrongly calculated returned value in fault_in_safe_writeable() Baoquan He
2025-04-10 8:31 ` Oscar Salvador
2025-04-11 3:43 ` Andrew Morton
2025-04-11 5:32 ` Baoquan He
2025-04-11 15:07 ` Andreas Gruenbacher
2025-04-11 23:22 ` Andrew Morton [this message]
2025-04-11 8:44 ` David Hildenbrand
2025-04-10 3:57 ` [PATCH v4 2/4] mm/gup: remove unneeded checking in follow_page_pte() Baoquan He
2025-04-10 3:57 ` [PATCH v4 3/4] mm/gup: remove gup_fast_pgd_leaf() and clean up the relevant codes Baoquan He
2025-04-10 3:57 ` [PATCH v4 4/4] mm/gup: clean up codes in fault_in_xxx() functions Baoquan He
2025-04-11 8:54 ` David Hildenbrand
2025-04-11 11:15 ` Baoquan He
2025-04-11 11:41 ` David Hildenbrand
2025-04-13 1:07 ` Baoquan He
2025-04-13 20:02 ` David Hildenbrand
2025-04-13 2:04 ` [PATCH v5 " Baoquan He
2025-04-13 20:09 ` David Hildenbrand
2025-04-14 3:44 ` Baoquan He
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=20250411162215.e7b102cf432e7de885b0eec7@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=agruenba@redhat.com \
--cc=bhe@redhat.com \
--cc=david@redhat.com \
--cc=gfs2@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=yanjun.zhu@linux.dev \
/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