From: <Tudor.Ambarus@microchip.com>
To: <lukas.bulwahn@gmail.com>
Cc: vigneshr@ti.com, bbrezillon@kernel.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
vz@mleia.com, linux-mtd@lists.infradead.org, joe@perches.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] MAINTAINERS: update entry after SPI NOR controller move
Date: Mon, 23 Mar 2020 17:57:00 +0000 [thread overview]
Message-ID: <22897927.UjJTgWM9OM@192.168.0.120> (raw)
In-Reply-To: <20200321064217.6179-1-lukas.bulwahn@gmail.com>
On Saturday, March 21, 2020 8:42:17 AM EET Lukas Bulwahn wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
>
> Commit a0900d0195d2 ("mtd: spi-nor: Prepare core / manufacturer code
> split") moved all SPI NOR controller drivers to a controllers/
> sub-directory. However, the moved nxp-spifi.c file was referenced in the
> ARM/LPC18XX ARCHITECTURE entry in MAINTAINERS.
>
> Hence, since then, ./scripts/get_maintainer.pl --self-test complains:
>
> warning: no file matches F: drivers/mtd/spi-nor/nxp-spifi.c
>
> Update the file entry in MAINTAINERS to its new location.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
> applies cleanly on next-20200320
> Boris, Tudor, please pick this trivial patch. Not urgent.
>
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied to spi-nor/next, thanks.
ta
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2020-03-23 17:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 6:42 [PATCH] MAINTAINERS: update entry after SPI NOR controller move Lukas Bulwahn
2020-03-23 17:57 ` Tudor.Ambarus [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=22897927.UjJTgWM9OM@192.168.0.120 \
--to=tudor.ambarus@microchip.com \
--cc=bbrezillon@kernel.org \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=lukas.bulwahn@gmail.com \
--cc=vigneshr@ti.com \
--cc=vz@mleia.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).