From: Christoph Niedermaier <cniedermaier@dh-electronics.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Shawn Guo <shawnguo@kernel.org>
Subject: RE: No matching files for file entry added in MAINTAINERS
Date: Fri, 16 Dec 2022 22:54:33 +0000 [thread overview]
Message-ID: <df35a27cca8444b884e35b1b9387beb2@dh-electronics.com> (raw)
In-Reply-To: <CAKXUXMxpWOXCUY-dd02P4ckAhF211VJtPTFeTriCMozZon7A5w@mail.gmail.com>
From: Lukas Bulwahn [mailto:lukas.bulwahn@gmail.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/
Best regards
Christoph
next prev parent reply other threads:[~2022-12-16 22:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 10:01 No matching files for file entry added in MAINTAINERS Lukas Bulwahn
2022-12-16 22:54 ` Christoph Niedermaier [this message]
2022-12-19 10:38 ` Lukas Bulwahn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=df35a27cca8444b884e35b1b9387beb2@dh-electronics.com \
--to=cniedermaier@dh-electronics.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=shawnguo@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox