From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Alexander Viro <viro@zeniv.linux.org.uk>, Jan Kara <jack@suse.cz>,
Dave Chinner <dchinner@redhat.com>,
"Theodore Ts'o" <tytso@mit.edu>,
Bob Peterson <rpeterso@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Matthew Wilcox <willy@infradead.org>,
Christoph Hellwig <hch@infradead.org>,
Andreas Gruenbacher <agruenba@redhat.com>
Subject: Re: [PATCH] fs: iomap: Change return type to vm_fault_t
Date: Thu, 19 Jul 2018 23:09:44 -0700 [thread overview]
Message-ID: <20180720060944.GA4823@magnolia> (raw)
In-Reply-To: <CAFqt6zY4BLw4HeaQmwgv2B+hQLnULuyvJDkcRd5-CbYTZuPw+w@mail.gmail.com>
On Fri, Jul 20, 2018 at 10:31:30AM +0530, Souptick Joarder wrote:
> On Wed, Jul 4, 2018 at 3:22 AM, Andreas Gruenbacher <agruenba@redhat.com> wrote:
> > On 3 July 2018 at 23:39, Darrick J. Wong <darrick.wong@oracle.com> wrote:
> >> On Mon, Jul 02, 2018 at 07:52:41PM +0200, Andreas Gruenbacher wrote:
> >>> On 2 July 2018 at 17:43, Souptick Joarder <jrdr.linux@gmail.com> wrote:
> >>> > Return type has been changed to vm_fault_t type for
> >>> > iomap_page_mkwrite().
> >>> >
> >>> > see commit 1c8f422059ae ("mm: change return type to
> >>> > vm_fault_t") for reference.
> >>> >
> >>> > Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
> >>> > Reviewed-by: Matthew Wilcox <mawilcox@microsoft.com>
> >>
> >> I don't recall Christoph [now cc'd] rescinding his NAK of the previous
> >> version of this patch[1]. Has he changed his mind since May?
> > /|\
> > Oops, a reply gone wrong -- I was me | to reply to Souptick
> > Joarder's gfs2 change which I've add | the gfs2 for-next branch.
> > Not the iomap change. Sorry for the | sion.
> > |
> >> [1] https://spinics.net/lists/linux | vel/msg126032.html
> >> |
> >> Now granted I didn't have a problem | the code (and applied the xfs
> >> version to 4.18 after monitoring to | sfy myself that nothing
> >> particularly weird happened during | but seeing as most of the iomap
> >> changes have gone through hch's rev | nd landed via the xfs tree...
|
--D |
|
I wasn't planning on it, due to aforementioned NAK still being in place
to the best of my knowledge, at least for the iomap patch.
> Darrick, is this patch going to 4.19 through xfs tree ?
next prev parent reply other threads:[~2018-07-20 6:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 15:43 [PATCH] fs: iomap: Change return type to vm_fault_t Souptick Joarder
2018-07-02 17:52 ` Andreas Gruenbacher
2018-07-03 21:39 ` Darrick J. Wong
2018-07-03 21:52 ` Andreas Gruenbacher
2018-07-20 5:01 ` Souptick Joarder
2018-07-20 6:09 ` Darrick J. Wong [this message]
2018-07-20 6:55 ` Souptick Joarder
2018-07-20 19:36 ` Matthew Wilcox
-- strict thread matches above, loose matches on Subject: below --
2018-08-27 17:20 Souptick Joarder
2018-04-14 20:02 Souptick Joarder
2018-05-14 18:15 ` Souptick Joarder
2018-05-15 7:10 ` Christoph Hellwig
2018-05-15 8:00 ` Souptick Joarder
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=20180720060944.GA4823@magnolia \
--to=darrick.wong@oracle.com \
--cc=agruenba@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dchinner@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=jrdr.linux@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpeterso@redhat.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--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 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.