linux-kernel - Re: [GIT PULL] NVDIMM and DAX for 6.5

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-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sat, 1 Jul 2023 08:51:29 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     "Verma, Vishal L" <vishal.l.verma@...el.com>
Cc:     "Williams, Dan J" <dan.j.williams@...el.com>,
        "nvdimm@...ts.linux.dev" <nvdimm@...ts.linux.dev>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] NVDIMM and DAX for 6.5

On Fri, 30 Jun 2023 at 12:17, Verma, Vishal L <vishal.l.verma@...el.com> wrote:
>
> On an operational note, as Dan handed off the branch to me for this cycle, we
> missed that the original few commits were inadvertently made on top of a few
> CXL commits that went in in the 6.4-rc cycle via the CXL tree.
>
> git-request-pull included these, and hence they appear in the shortlog and
> diffstat below, but the actual merge correctly identifies and skips over them.
> I kept it as it is to preserve the linux-next soak time, but if I should have
> done it differently, please let me know.

No, this was the right thing to do. Apart from a slightly odd choice
of base for this all, the pull looks perfectly normal.

Thanks,
                Linus