Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <4880b31d0d32c38a675048be903814a062907125.camel@intel.com>
In-Reply-To: <4880b31d0d32c38a675048be903814a062907125.camel@intel.com>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri, 28 Dec 2018 21:57:28 -0800
Message-ID: <CAHk-=wgMfBXdiaeAxYrdTq9VoaVgN26T8MU7+3EnvJP_e0byuw@mail.gmail.com>
Subject: Re: [GIT PULL] libnvdimm for 4.21
To:     "Williams, Dan J" <dan.j.williams@intel.com>,
        Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc:     "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Hmm.

This pull request doesn't seem to have gotten an automatic pr-tracker
reply, even though I pulled it, and even though it was cc'd to lkml.

Konstantin, any idea why the automation didn't trigger? I'm not seeing
anything all that odd about it.

[ looks around ]

Oh, I notice that I can't seem to find this message on lore.kernel.org
either, despite seeing that lkml cc when I look at my copy of the
email.

Does lkml hate Dan?

Headers say

  To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
  CC: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
  ...
  Date: Fri, 28 Dec 2018 05:04:27 +0000
  Message-ID: <4880b31d0d32c38a675048be903814a062907125.camel@intel.com>

but when I try to look it up on lore.kernel.org, I get:

  Message-ID <4880b31d0d32c38a675048be903814a062907125.camel@intel.com>
  not found

Weird.

               Linus

On Thu, Dec 27, 2018 at 9:04 PM Williams, Dan J
<dan.j.williams@intel.com> wrote:
>
> Hi Linus, please pull from:
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/libnvdimm-for-4.21
>
> ...to receive the libnvdimm update for 4.21.
[...]