From: <Tudor.Ambarus@microchip.com>
To: <mika.westerberg@linux.intel.com>, <marek.vasut@gmail.com>
Cc: vigneshr@ti.com, richard@nod.at, linux-mtd@lists.infradead.org,
miquel.raynal@bootlin.com, computersforpeace@gmail.com,
dwmw2@infradead.org
Subject: Re: [PATCH 2/2] spi-nor: intel-spi: Convert to use SPDX identifier
Date: Sat, 22 Jun 2019 12:04:29 +0000 [thread overview]
Message-ID: <16bd8081-456d-bbc2-a7d2-4f451271b151@microchip.com> (raw)
In-Reply-To: <20190620122629.20838-2-mika.westerberg@linux.intel.com>
On 06/20/2019 03:26 PM, Mika Westerberg wrote:
> External E-Mail
>
>
> This gets rid of the license boilerplate duplicated in each file.
>
> No functional changes intended.
>
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> ---
> drivers/mtd/spi-nor/intel-spi-pci.c | 5 +----
> drivers/mtd/spi-nor/intel-spi-platform.c | 5 +----
> drivers/mtd/spi-nor/intel-spi.c | 5 +----
> drivers/mtd/spi-nor/intel-spi.h | 5 +----
> include/linux/platform_data/intel-spi.h | 5 +----
> 5 files changed, 5 insertions(+), 20 deletions(-)
>
The patch's subject should begin with "mtd: spi-nor:". Did the change and
applied to https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git,
spi-nor/next branch.
Thanks,
ta
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-06-22 12:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 12:26 [PATCH 1/2] spi-nor: intel-spi: Add support for Intel Elkhart Lake SPI serial flash Mika Westerberg
2019-06-20 12:26 ` [PATCH 2/2] spi-nor: intel-spi: Convert to use SPDX identifier Mika Westerberg
2019-06-22 12:04 ` Tudor.Ambarus [this message]
2019-06-22 12:03 ` [PATCH 1/2] spi-nor: intel-spi: Add support for Intel Elkhart Lake SPI serial flash Tudor.Ambarus
2019-06-24 11:02 ` Mika Westerberg
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=16bd8081-456d-bbc2-a7d2-4f451271b151@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=mika.westerberg@linux.intel.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.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).