LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Dave Jiang <dave.jiang@intel.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>, Vinod Koul <vkoul@kernel.org>
Cc: dmaengine@vger.kernel.org, Joe Perches <joe@perches.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: rectify the INTEL IADX DRIVER entry
Date: Mon, 9 Mar 2020 09:08:57 -0700 [thread overview]
Message-ID: <26c4fdca-4a36-d710-0504-569adf5ec079@intel.com> (raw)
In-Reply-To: <20200307205737.5829-1-lukas.bulwahn@gmail.com>
On 3/7/20 1:57 PM, Lukas Bulwahn wrote:
> Commit bfe1d56091c1 ("dmaengine: idxd: Init and probe for Intel data
> accelerators") added the INTEL IADX DRIVER entry in MAINTAINERS, which
> mentions include/linux/idxd.h as file entry. However, this header file was
> not added in this commit, nor in any later one.
>
> Hence, since then, ./scripts/get_maintainer.pl --self-test complains:
>
> warning: no file matches F: include/linux/idxd.h
>
> Drop the file entry to the non-existing file in INTEL IADX DRIVER now.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Thanks. That was a mistake.
Acked-by: Dave Jiang <dave.jiang@intel.com>
> ---
> applies cleanly on current master and next-20200306
>
> MAINTAINERS | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index c93e4937164c..303e1ea83484 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -8478,7 +8478,6 @@ L: dmaengine@vger.kernel.org
> S: Supported
> F: drivers/dma/idxd/*
> F: include/uapi/linux/idxd.h
> -F: include/linux/idxd.h
>
> INTEL IDLE DRIVER
> M: Jacob Pan <jacob.jun.pan@linux.intel.com>
>
next prev parent reply other threads:[~2020-03-09 16:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 20:57 Lukas Bulwahn
2020-03-09 16:08 ` Dave Jiang [this message]
2020-03-11 9:30 ` Vinod Koul
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=26c4fdca-4a36-d710-0504-569adf5ec079@intel.com \
--to=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=vkoul@kernel.org \
--subject='Re: [PATCH] MAINTAINERS: rectify the INTEL IADX DRIVER entry' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).