linux-kernel - Re: No matching files for file entry added in MAINTAINERS

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: <CAKXUXMwZyEzZxM8zT8z1mHkLnNCBd=VxcxCPn=0QE-Gn-iU0aA@mail.gmail.com>
Date:   Mon, 19 Dec 2022 11:38:19 +0100
From:   Lukas Bulwahn <lukas.bulwahn@...il.com>
To:     Christoph Niedermaier <cniedermaier@...electronics.com>
Cc:     Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Arnd Bergmann <arnd@...db.de>, Shawn Guo <shawnguo@...nel.org>
Subject: Re: No matching files for file entry added in MAINTAINERS

On Fri, Dec 16, 2022 at 11:54 PM Christoph Niedermaier
<cniedermaier@...electronics.com> wrote:
>
> From: Lukas Bulwahn [mailto:lukas.bulwahn@...il.com]
> Sent: Friday, December 16, 2022 11:02 AM
> >
> > Dear Christoph,
> >
> > with commit 894799e1f496 ("MAINTAINERS: Add DHCOR to the DH electronic
> > i.MX6 board support"), originating from
> > https://lore.kernel.org/lkml/20221117105131.7059-1-cniedermaier@dh-electronics.com/,
> > you have added a file entry to DH ELECTRONICS IMX6 DHCOM/DHCOR BOARD
> > SUPPORT, but there is no file matching this entry in the repository.
> >
> > Are there still files to come or should this pattern actually match
> > certain files in the repository, but they are named slightly
> > different?
> >
> >
>
> At least one DHCOR file should come soon hopefully:
> https://lore.kernel.org/linux-arm-kernel/20221123173601.13291-2-cniedermaier@dh-electronics.com/
>

Thanks for the pointer, Christoph. I probably just missed that, as I
checked on November 22th (when it hit linux-next), put reporting it on
my todo list, and I did not re-check for pending patches afterwards
when sending out the report on Friday. Let us just wait until the
pending patches land and then the reported issue is resolved.


Best regards,

Lukas