From: Al Viro <viro@ZenIV.linux.org.uk>
To: Salah Triki <salah.triki@acm.org>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs: befs: replace GFP_KERNEL by GFP_NOFS
Date: Sat, 21 May 2016 01:57:01 +0100 [thread overview]
Message-ID: <20160521005701.GV14480@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1463742428-4862-1-git-send-email-salah.triki@acm.org>
On Fri, May 20, 2016 at 12:07:08PM +0100, Salah Triki wrote:
> Since this is a filesystem driver, using the flag GFP_NOFS is more
> appropriate than the flag GFP_KERNEL.
What does "more appropriate" mean? Either there is a specific reason, or
it's a cargo-culting, plain and simple. _Why_ does it need GFP_NOFS?
prev parent reply other threads:[~2016-05-21 0:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 11:07 [PATCH] fs: befs: replace GFP_KERNEL by GFP_NOFS Salah Triki
2016-05-21 0:57 ` Al Viro [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=20160521005701.GV14480@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=salah.triki@acm.org \
/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