From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Williams, Dan J" <dan.j.williams@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [GIT PULL] filesystem-dax fix for 4.19-rc6
Date: Sun, 30 Sep 2018 06:38:18 -0700 [thread overview]
Message-ID: <20180930133818.GA5085@kroah.com> (raw)
In-Reply-To: <1538273814.24243.65.camel@intel.com>
On Sun, Sep 30, 2018 at 02:16:57AM +0000, Williams, Dan J wrote:
> Hi Greg, please pull from...
>
> git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/libnvdimm-fixes2-4.19-rc6
>
> ...to receive one more urgent fix for 4.19-rc6.
Now pulled, thanks.
greg k-h
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Williams, Dan J" <dan.j.williams@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [GIT PULL] filesystem-dax fix for 4.19-rc6
Date: Sun, 30 Sep 2018 06:38:18 -0700 [thread overview]
Message-ID: <20180930133818.GA5085@kroah.com> (raw)
In-Reply-To: <1538273814.24243.65.camel@intel.com>
On Sun, Sep 30, 2018 at 02:16:57AM +0000, Williams, Dan J wrote:
> Hi Greg, please pull from...
>
> git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/libnvdimm-fixes2-4.19-rc6
>
> ...to receive one more urgent fix for 4.19-rc6.
Now pulled, thanks.
greg k-h
next prev parent reply other threads:[~2018-09-30 13:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-30 2:16 [GIT PULL] filesystem-dax fix for 4.19-rc6 Williams, Dan J
2018-09-30 2:16 ` Williams, Dan J
2018-09-30 13:38 ` gregkh [this message]
2018-09-30 13:38 ` gregkh
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=20180930133818.GA5085@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.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.