From: Michal Hocko <mhocko@suse.com>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Dave Chinner <david@fromorbit.com>,
Christoph Hellwig <hch@infradead.org>,
Ilya Dryomov <idryomov@gmail.com>,
Jeff Layton <jlayton@kernel.org>, Linux-MM <linux-mm@kvack.org>,
mm-commits@vger.kernel.org, Neil Brown <neilb@suse.de>,
Uladzislau Rezki <urezki@gmail.com>
Subject: Re: [patch 099/262] mm/vmalloc: be more explicit about supported gfp flags
Date: Mon, 8 Nov 2021 18:30:05 +0100 [thread overview]
Message-ID: <YYleneQXV/Jz619B@dhcp22.suse.cz> (raw)
In-Reply-To: <CAHk-=wjov5-baOgf+r7bOh=P_YCHuxBcyf_b=or990RTxz5QAw@mail.gmail.com>
On Mon 08-11-21 09:15:04, Linus Torvalds wrote:
> On Mon, Nov 8, 2021 at 1:25 AM Michal Hocko <mhocko@suse.com> wrote:
> >
> > As already pointed out
> > http://lkml.kernel.org/r/YXE+hcodJ7zxeYA7@dhcp22.suse.cz this patch
> > cannot be applied without other patches from the same series.
>
> Hmm. I've taken it already.
>
> Not a huge deal, since it's a comment change - and the code will
> presumably eventually match the updated comment.
I plan to send the rest after the merge window.
> I guess it's a new thing that instead of stale comments, we have
> future-proof ones ;)
I just hope nobody gets confused about which are not supported yet. E.g.
GFP_NOFAIL, GFP_NO{FS,IO}. In both cases the direct use could lead to
bugs.
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2021-11-08 17:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211105133408.cccbb98b71a77d5e8430aba1@linux-foundation.org>
[not found] ` <20211105203950.AJ1Cnteeh%akpm@linux-foundation.org>
2021-11-08 9:25 ` [patch 099/262] mm/vmalloc: be more explicit about supported gfp flags Michal Hocko
2021-11-08 17:15 ` Linus Torvalds
2021-11-08 17:30 ` Michal Hocko [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=YYleneQXV/Jz619B@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mm-commits@vger.kernel.org \
--cc=neilb@suse.de \
--cc=urezki@gmail.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