linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: Matthew Wilcox <willy@infradead.org>,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH] fs: f2fs: Adding new return type vm_fault_t
Date: Thu, 10 May 2018 09:23:05 -0700	[thread overview]
Message-ID: <20180510162305.GA49708@jaegeuk-macbookpro.roam.corp.google.com> (raw)
In-Reply-To: <CAFqt6zZbci2FZPdTRCdhpTu0h=uguCnk+0q_602O6tz66oePxQ@mail.gmail.com>

On 05/10, Souptick Joarder wrote:
> On Mon, Apr 16, 2018 at 7:17 AM, Chao Yu <yuchao0@huawei.com> wrote:
> > On 2018/4/15 4:10, Souptick Joarder wrote:
> >> Use new return type vm_fault_t for page_mkwrite
> >> and fault handler.
> >>
> >> Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
> >> Reviewed-by: Matthew Wilcox <mawilcox@microsoft.com>
> >
> > Acked-by: Chao Yu <yuchao0@huawei.com>
> >
> 
> Chao, If no further comment, we would like to get this patch
> queued for 4.18.

Hi Souptick,

Is this one of your patch series?
I already queued it towards 4.18:

https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git/commit/?h=dev-test&id=f8fcb679cfbeb2076c547364929182babdd69a50

Thanks,

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

  reply	other threads:[~2018-05-10 16:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-14 20:10 [PATCH] fs: f2fs: Adding new return type vm_fault_t Souptick Joarder
2018-04-16  1:47 ` Chao Yu
2018-05-10 15:32   ` Souptick Joarder
2018-05-10 16:23     ` Jaegeuk Kim [this message]
2018-05-10 17:12       ` Souptick Joarder
2018-05-14  3:47         ` Chao Yu

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=20180510162305.GA49708@jaegeuk-macbookpro.roam.corp.google.com \
    --to=jaegeuk@kernel.org \
    --cc=jrdr.linux@gmail.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).