From: Vinod Koul <vkoul@kernel.org>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
dmaengine@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: remove section INTEL IOP-ADMA DMA DRIVER
Date: Fri, 4 Nov 2022 19:36:52 +0530 [thread overview]
Message-ID: <Y2UcfDxYQgsqiiyC@matsya> (raw)
In-Reply-To: <20221020082103.29218-1-lukas.bulwahn@gmail.com>
On 20-10-22, 10:21, Lukas Bulwahn wrote:
> Commit cd0ab43ec91a ("dmaengine: remove iop-adma driver") removes the
> driver's source code, but misses to remove the MAINTAINERS section.
>
> Hence, ./scripts/get_maintainer.pl --self-test=patterns complains about a
> broken file pattern.
>
> Remove the INTEL IOP-ADMA DMA DRIVER section pointing to the removed
> driver.
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2022-11-04 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 8:21 [PATCH] MAINTAINERS: remove section INTEL IOP-ADMA DMA DRIVER Lukas Bulwahn
2022-10-20 15:28 ` Dan Williams
2022-11-04 14:06 ` Vinod Koul [this message]
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=Y2UcfDxYQgsqiiyC@matsya \
--to=vkoul@kernel.org \
--cc=arnd@arndb.de \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
/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