linux-kernel - Re: [GIT PULL] libnvdimm for 4.21

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 28 Dec 2018 21:57:28 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     "Williams, Dan J" <dan.j.williams@...el.com>,
        Konstantin Ryabitsev <konstantin@...uxfoundation.org>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>
Subject: Re: [GIT PULL] libnvdimm for 4.21

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@...ux-foundation.org" <torvalds@...ux-foundation.org>
  CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>
  ...
  Date: Fri, 28 Dec 2018 05:04:27 +0000
  Message-ID: <4880b31d0d32c38a675048be903814a062907125.camel@...el.com>

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

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

Weird.

               Linus

On Thu, Dec 27, 2018 at 9:04 PM Williams, Dan J
<dan.j.williams@...el.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.
[...]