linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Schrempf Frieder <frieder.schrempf@kontron.de>
To: Yogesh Narayan Gaur <yogeshnarayan.gaur@nxp.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"bbrezillon@kernel.org" <bbrezillon@kernel.org>,
	"marek.vasut@gmail.com" <marek.vasut@gmail.com>,
	"broonie@kernel.org" <broonie@kernel.org>,
	"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>
Cc: "computersforpeace@gmail.com" <computersforpeace@gmail.com>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Re: [PATCH] spi: spi-mem: spi-fsl-qspi: typo fix in author name
Date: Tue, 29 Jan 2019 11:46:02 +0000	[thread overview]
Message-ID: <4759d7a9-71a2-70a7-2704-0ef7fa37b2ca@kontron.de> (raw)
In-Reply-To: <1548755607-27544-1-git-send-email-yogeshnarayan.gaur@nxp.com>

On 29.01.19 10:55, Yogesh Narayan Gaur wrote:
> Typo fix in Author Boris Brezillon last name and update with new
> email address.
> 
> Signed-off-by: Yogesh Narayan Gaur <yogeshnarayan.gaur@nxp.com>

Oh, so this was my typo in the first place and you just copied it ;)
Thanks for sending the patch.

Mark, could you please squash this with the original commit 
(84d043185dbe spi: Add a driver for the Freescale/NXP QuadSPI 
controller) in spi-next?

Acked-by: Frieder Schrempf <frieder.schrempf@kontron.de>

> ---
>   drivers/spi/spi-fsl-qspi.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/spi/spi-fsl-qspi.c b/drivers/spi/spi-fsl-qspi.c
> index f0a340026ba4..6a713f78a62e 100644
> --- a/drivers/spi/spi-fsl-qspi.c
> +++ b/drivers/spi/spi-fsl-qspi.c
> @@ -10,7 +10,7 @@
>    *
>    * Transition to SPI MEM interface:
>    * Authors:
> - *     Boris Brezillion <boris.brezillon@bootlin.com>
> + *     Boris Brezillon <bbrezillon@kernel.org>
>    *     Frieder Schrempf <frieder.schrempf@kontron.de>
>    *     Yogesh Gaur <yogeshnarayan.gaur@nxp.com>
>    *     Suresh Gupta <suresh.gupta@nxp.com>
> @@ -959,7 +959,7 @@ module_platform_driver(fsl_qspi_driver);
>   
>   MODULE_DESCRIPTION("Freescale QuadSPI Controller Driver");
>   MODULE_AUTHOR("Freescale Semiconductor Inc.");
> -MODULE_AUTHOR("Boris Brezillion <boris.brezillon@bootlin.com>");
> +MODULE_AUTHOR("Boris Brezillon <bbrezillon@kernel.org>");
>   MODULE_AUTHOR("Frieder Schrempf <frieder.schrempf@kontron.de>");
>   MODULE_AUTHOR("Yogesh Gaur <yogeshnarayan.gaur@nxp.com>");
>   MODULE_AUTHOR("Suresh Gupta <suresh.gupta@nxp.com>");
> 
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2019-01-29 11:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-29  9:55 [PATCH] spi: spi-mem: spi-fsl-qspi: typo fix in author name Yogesh Narayan Gaur
2019-01-29 11:46 ` Schrempf Frieder [this message]
2019-01-29 11:59   ` Mark Brown
2019-01-29 12:08     ` Schrempf Frieder
2019-01-29 12:12       ` Mark Brown
2019-01-29 12:14 ` Applied "spi: spi-mem: spi-fsl-qspi: typo fix in author name" to the spi tree Mark Brown

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=4759d7a9-71a2-70a7-2704-0ef7fa37b2ca@kontron.de \
    --to=frieder.schrempf@kontron.de \
    --cc=bbrezillon@kernel.org \
    --cc=broonie@kernel.org \
    --cc=computersforpeace@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=marek.vasut@gmail.com \
    --cc=yogeshnarayan.gaur@nxp.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).