linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: Jan Kara <jack@suse.cz>, Matthew Wilcox <willy@infradead.org>,
	Ross Zwisler <zwisler@kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fs/dax: Convert to use vmf_error()
Date: Mon, 4 Feb 2019 18:42:23 -0800	[thread overview]
Message-ID: <CAPcyv4h819u1teAQrwJEbPUzucwTwOENYwi4nPHnGvvX3YSx5g@mail.gmail.com> (raw)
In-Reply-To: <CAFqt6zYZdpckNPFGx2+nbNs=1UKSGtFvMc5YMvPEnmK4PJyGMQ@mail.gmail.com>

On Mon, Feb 4, 2019 at 6:33 PM Souptick Joarder <jrdr.linux@gmail.com> wrote:
>
> Hi Dan,
>
> On Tue, Jan 15, 2019 at 4:00 AM Dan Williams <dan.j.williams@intel.com> wrote:
> >
> > On Mon, Jan 14, 2019 at 12:59 AM Jan Kara <jack@suse.cz> wrote:
> > >
> > > On Sat 05-01-19 00:54:11, Souptick Joarder wrote:
> > > > This code is converted to use vmf_error().
> > > >
> > > > Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
> > >
> > > Dan, you are merging DAX patches these days. So probably you should add
> > > yourself to 'FILESYSTEM DIRECT ACCESS (DAX)' in MAINTAINERs.
> >
> > Sounds good, I'll merge this and get MAINTAINERs fixed up.
>
> This is not reflecting in linux-next. Is this queued for 5.1 ?

Thanks for the ping, I'll get it queued up shortly.

      reply	other threads:[~2019-02-05  2:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-04 19:24 [PATCH] fs/dax: Convert to use vmf_error() Souptick Joarder
2019-01-14  4:28 ` Souptick Joarder
2019-01-14  8:58 ` Jan Kara
2019-01-14 22:30   ` Dan Williams
2019-02-05  2:33     ` Souptick Joarder
2019-02-05  2:42       ` Dan Williams [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=CAPcyv4h819u1teAQrwJEbPUzucwTwOENYwi4nPHnGvvX3YSx5g@mail.gmail.com \
    --to=dan.j.williams@intel.com \
    --cc=jack@suse.cz \
    --cc=jrdr.linux@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.org \
    --cc=zwisler@kernel.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).