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] libnvdimm/dax fixes for 4.19-rc6
Date: Tue, 25 Sep 2018 11:19:00 +0200 [thread overview]
Message-ID: <20180925091900.GB21972@kroah.com> (raw)
In-Reply-To: <1537832042.7585.16.camel@intel.com>
On Mon, Sep 24, 2018 at 11:34:04PM +0000, Williams, Dan J wrote:
> Hi Greg, please pull from...
>
> git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm libnvdimm-fixes
That isn't a signed tag. Did you mean to not sign it? Your previous
pull requests did have signed tags :(
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] libnvdimm/dax fixes for 4.19-rc6
Date: Tue, 25 Sep 2018 11:19:00 +0200 [thread overview]
Message-ID: <20180925091900.GB21972@kroah.com> (raw)
In-Reply-To: <1537832042.7585.16.camel@intel.com>
On Mon, Sep 24, 2018 at 11:34:04PM +0000, Williams, Dan J wrote:
> Hi Greg, please pull from...
>
> git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm libnvdimm-fixes
That isn't a signed tag. Did you mean to not sign it? Your previous
pull requests did have signed tags :(
thanks,
greg k-h
next prev parent reply other threads:[~2018-09-25 9:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 23:34 [GIT PULL] libnvdimm/dax fixes for 4.19-rc6 Williams, Dan J
2018-09-25 9:19 ` gregkh [this message]
2018-09-25 9:19 ` gregkh
2018-09-25 15:30 ` Dan Williams
2018-09-25 15:30 ` Dan Williams
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=20180925091900.GB21972@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.