From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>, linux-can@vger.kernel.org
Cc: Dan Murphy <dmurphy@ti.com>, Sean Nyekjaer <sean@geanix.com>,
Sriram Dash <sriram.dash@samsung.com>,
Joe Perches <joe@perches.com>,
Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de>,
Pia Eichinger <pia.eichinger@st.oth-regensburg.de>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH for can-next] MAINTAINERS: adjust entry to tcan4x5x file split
Date: Fri, 8 Jan 2021 09:06:33 +0100 [thread overview]
Message-ID: <0ba9535f-2e1d-116d-1c47-01bdd0ff89b3@pengutronix.de> (raw)
In-Reply-To: <20210108073932.20804-1-lukas.bulwahn@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1103 bytes --]
On 1/8/21 8:39 AM, Lukas Bulwahn wrote:
> Commit 7813887ea972 ("can: tcan4x5x: rename tcan4x5x.c -> tcan4x5x-core.c")
> and commit 67def4ef8bb9 ("can: tcan4x5x: move regmap code into seperate
> file") split the file tcan4x5x.c into two files, but missed to adjust the
> TI TCAN4X5X DEVICE DRIVER section in MAINTAINERS.
>
> Hence, ./scripts/get_maintainer.pl --self-test=patterns complains:
>
> warning: no file matches F: drivers/net/can/m_can/tcan4x5x.c
>
> Adjust the file entry in MAINTAINERS to the tcan4x5x file splitting.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
> applies cleanly on next-20210107, not for current master
>
> Marc, please pick this for your -next tree on top of the tcan4x5x cleanup.
Makes perfect sense. Applied to linux-can-next.
Thanks,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-01-08 8:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 7:39 Lukas Bulwahn
2021-01-08 8:06 ` Marc Kleine-Budde [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=0ba9535f-2e1d-116d-1c47-01bdd0ff89b3@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=dmurphy@ti.com \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=pia.eichinger@st.oth-regensburg.de \
--cc=ralf.ramsauer@oth-regensburg.de \
--cc=sean@geanix.com \
--cc=sriram.dash@samsung.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
all inboxes | Powered by JetHome®