From: Borislav Petkov <bp@alien8.de>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
Christoph Hellwig <hch@lst.de>, Borislav Petkov <bp@suse.de>,
Yash Shah <yash.shah@sifive.com>,
linux-edac@vger.kernel.org,
Sebastian Duda <sebastian.duda@fau.de>,
Joe Perches <joe@perches.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] MAINTAINERS: place sifive_l2_cache.c only in SIFIVE DRIVERS
Date: Wed, 15 Apr 2020 11:34:35 +0200 [thread overview]
Message-ID: <20200415093435.GC31016@zn.tnic> (raw)
In-Reply-To: <20200413115255.7100-1-lukas.bulwahn@gmail.com>
On Mon, Apr 13, 2020 at 01:52:55PM +0200, Lukas Bulwahn wrote:
> Commit 9209fb51896f ("riscv: move sifive_l2_cache.c to drivers/soc") moved
> arch/riscv/mm/sifive_l2_cache.c to drivers/soc/sifive/sifive_l2_cache.c
> and adjusted the MAINTAINERS EDAC-SIFIVE entry but slipped in a mistake.
>
> Since then, ./scripts/get_maintainer.pl --self-test complains:
>
> warning: no file matches F: drivers/soc/sifive_l2_cache.c
>
> Boris suggested that sifive_l2_cache.c is considered part of the SIFIVE
> DRIVERS, not part of EDAC-SIFIVE. So, we can simply drop this entry, and
> by the sifive keyword pattern in SIFIVE PATTERNS, it is automatically part
> of the SIFIVE DRIVERS.
>
> Suggested-by: Borislav Petkov <bp@alien8.de>
> Co-developed-by: Sebastian Duda <sebastian.duda@fau.de>
> Signed-off-by: Sebastian Duda <sebastian.duda@fau.de>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
Applied, thanks.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2020-04-15 9:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 11:52 [PATCH v3] MAINTAINERS: place sifive_l2_cache.c only in SIFIVE DRIVERS Lukas Bulwahn
2020-04-15 9:34 ` Borislav Petkov [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=20200415093435.GC31016@zn.tnic \
--to=bp@alien8.de \
--cc=bp@suse.de \
--cc=hch@lst.de \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=paul.walmsley@sifive.com \
--cc=sebastian.duda@fau.de \
--cc=yash.shah@sifive.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;
as well as URLs for NNTP newsgroup(s).