linux-kernel - Re: [PATCH] MAINTAINERS: remove section LIBNVDIMM BLK: MMIO-APERTURE DRIVER

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

Message-ID: <CAPcyv4ita5JmK4noL0euebNgLDYYb6fmnDQZfksTr=FOqtqe+g@mail.gmail.com>
Date:   Tue, 15 Mar 2022 22:25:28 -0700
From:   Dan Williams <dan.j.williams@...el.com>
To:     Lukas Bulwahn <lukas.bulwahn@...il.com>
Cc:     Linux NVDIMM <nvdimm@...ts.linux.dev>,
        Vishal Verma <vishal.l.verma@...el.com>,
        Dave Jiang <dave.jiang@...el.com>,
        Ira Weiny <ira.weiny@...el.com>,
        kernel-janitors@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: remove section LIBNVDIMM BLK: MMIO-APERTURE DRIVER

On Tue, Mar 15, 2022 at 10:21 PM Lukas Bulwahn <lukas.bulwahn@...il.com> wrote:
>
> Commit f8669f1d6a86 ("nvdimm/blk: Delete the block-aperture window driver")
> removes the file drivers/nvdimm/blk.c, but misses to adjust MAINTAINERS.
>
> Hence, ./scripts/get_maintainer.pl --self-test=patterns complains about a
> broken reference.
>
> The section LIBNVDIMM BLK: MMIO-APERTURE DRIVER refers to the driver in
> blk.c, and some more generic nvdimm code in region_devs.c.
>
> As the driver is deleted, delete the section LIBNVDIMM BLK: MMIO-APERTURE
> DRIVER in MAINTAINERS as well.
>
> The remaining file region_devs.c is still covered by the section LIBNVDIMM:
> NON-VOLATILE MEMORY DEVICE SUBSYSTEM, and all patches to region_devs.c will
> still reach the same developers as before.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@...il.com>
> ---
> Dan, please pick this minor clean-up patch in your -next tree on top of
> the commit above.

Ah yes, looks good. Thank you for the fix up.