From: Greg KH <gregkh@linuxfoundation.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Steve Capper <steve.capper@arm.com>,
Will Deacon <will.deacon@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] [Rebased for 5.4] mm, hugetlb: allow for "high" userspace addresses
Date: Wed, 4 May 2022 17:08:46 +0200 [thread overview]
Message-ID: <YnKW/h6yElTSBKB1@kroah.com> (raw)
In-Reply-To: <9853ade6-3f32-7811-474e-2da2361af16c@csgroup.eu>
On Wed, May 04, 2022 at 07:26:00AM +0000, Christophe Leroy wrote:
>
>
> Le 03/05/2022 à 15:47, Greg KH a écrit :
> > On Tue, May 03, 2022 at 02:47:11PM +0200, Christophe Leroy wrote:
> >> This is backport for linux 5.4
> >>
> >> commit 5f24d5a579d1eace79d505b148808a850b417d4c upstream.
> >
> > Now queued up, thanks.
> >
>
> Looks like the robot has found a build failure, due to missing #include
> <linux/sched/mm.h>
>
> However, looking into it in more details, I think we should just apply
> the two following commits unmodified instead of modifying the original
> commit:
>
> 885902531586 ("hugetlbfs: get unmapped area below TASK_UNMAPPED_BASE for
> hugetlbfs")
> 5f24d5a579d1 ("mm, hugetlb: allow for "high" userspace addresses")
Ok, thanks, I've done this now.
greg k-h
prev parent reply other threads:[~2022-05-04 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 12:47 [PATCH] [Rebased for 5.4] mm, hugetlb: allow for "high" userspace addresses Christophe Leroy
2022-05-03 13:47 ` Greg KH
2022-05-04 7:26 ` Christophe Leroy
2022-05-04 15:08 ` Greg KH [this message]
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=YnKW/h6yElTSBKB1@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=steve.capper@arm.com \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.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