linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ashish Samant <ashish.samant@oracle.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org,
	fuse-devel <fuse-devel@lists.sourceforge.net>
Subject: Re: [PATCH V2] fuse: Dont call set_page_dirty_lock() for ITER_BVEC pages for async_dio
Date: Thu, 3 Aug 2017 14:34:46 -0700	[thread overview]
Message-ID: <598396F6.6010009@oracle.com> (raw)
In-Reply-To: <CAJfpeguDQgbcBfAWwE9N9Vfdyz_SLe8Qg1c=iHWwMXag29d03Q@mail.gmail.com>



On 08/03/2017 08:59 AM, Miklos Szeredi wrote:
> On Thu, Jul 27, 2017 at 1:06 AM, Ashish Samant <ashish.samant@oracle.com> wrote:
>> Hi Miklos,
>>
>> Is this version ok?
> Hi,
>
> Thanks for the patch.  Cleaned up variant pushed to for-next branch in
> my fuse tree.  Please check if it's still OK.

Hi Miklos,

Yes, the patch in your tree looks ok.

Thanks,
Ashish
>
> Thanks,
> Miklos

      reply	other threads:[~2017-08-03 21:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-13  2:26 [PATCH V2] fuse: Dont call set_page_dirty_lock() for ITER_BVEC pages for async_dio Ashish Samant
2017-07-26 23:06 ` Ashish Samant
2017-08-03 15:59   ` Miklos Szeredi
2017-08-03 21:34     ` Ashish Samant [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=598396F6.6010009@oracle.com \
    --to=ashish.samant@oracle.com \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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;
as well as URLs for NNTP newsgroup(s).