From: Khazhismel Kumykov <khazhy@google.com>
To: Shakeel Butt <shakeelb@google.com>
Cc: miklos@szeredi.hu, linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] fuse: pass gfp flags to fuse_request_alloc
Date: Thu, 22 Aug 2019 12:52:54 -0700 [thread overview]
Message-ID: <CACGdZYJK+Q4Ak5hEj3EDeO3QJ=JNPLJZ=G3HZcGQL9zRoMnbtw@mail.gmail.com> (raw)
In-Reply-To: <CALvZod5d1iyJtfwzW0qtHLJ4cB5zQqAHuVBM_ay9cWD=TTSPSw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 422 bytes --]
On Wed, Aug 21, 2019 at 5:18 PM Shakeel Butt <shakeelb@google.com> wrote:
>
> On Wed, Aug 21, 2019 at 5:10 PM Khazhismel Kumykov <khazhy@google.com> wrote:
> >
> > Instead of having a helper per flag
> >
> > Signed-off-by: Khazhismel Kumykov <khazhy@google.com>
>
> I think it would be better to re-order the patch 2 and 3 of this
> series. There will be less code churn.
That makes sense to me, I'll follow up with a v2
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4843 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Khazhismel Kumykov <khazhy@google.com>
To: Shakeel Butt <shakeelb@google.com>
Cc: miklos@szeredi.hu, linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] fuse: pass gfp flags to fuse_request_alloc
Date: Thu, 22 Aug 2019 12:52:54 -0700 [thread overview]
Message-ID: <CACGdZYJK+Q4Ak5hEj3EDeO3QJ=JNPLJZ=G3HZcGQL9zRoMnbtw@mail.gmail.com> (raw)
In-Reply-To: <CALvZod5d1iyJtfwzW0qtHLJ4cB5zQqAHuVBM_ay9cWD=TTSPSw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 422 bytes --]
On Wed, Aug 21, 2019 at 5:18 PM Shakeel Butt <shakeelb@google.com> wrote:
>
> On Wed, Aug 21, 2019 at 5:10 PM Khazhismel Kumykov <khazhy@google.com> wrote:
> >
> > Instead of having a helper per flag
> >
> > Signed-off-by: Khazhismel Kumykov <khazhy@google.com>
>
> I think it would be better to re-order the patch 2 and 3 of this
> series. There will be less code churn.
That makes sense to me, I'll follow up with a v2
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4843 bytes --]
next prev parent reply other threads:[~2019-08-22 19:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 0:09 [PATCH 1/3] fuse: on 64-bit store time in d_fsdata directly Khazhismel Kumykov
2019-08-22 0:09 ` [PATCH 2/3] fuse: kmemcg account fs data Khazhismel Kumykov
2019-08-22 0:09 ` [PATCH 3/3] fuse: pass gfp flags to fuse_request_alloc Khazhismel Kumykov
2019-08-22 0:18 ` Shakeel Butt
2019-08-22 19:52 ` Khazhismel Kumykov [this message]
2019-08-22 19:52 ` Khazhismel Kumykov
2019-08-22 0:17 ` [PATCH 1/3] fuse: on 64-bit store time in d_fsdata directly Shakeel Butt
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='CACGdZYJK+Q4Ak5hEj3EDeO3QJ=JNPLJZ=G3HZcGQL9zRoMnbtw@mail.gmail.com' \
--to=khazhy@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=shakeelb@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.