linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Frieder Schrempf <frieder.schrempf@exceet.de>
Cc: dwmw2@infradead.org, computersforpeace@gmail.com,
	marek.vasut@gmail.com, richard@nod.at, broonie@kernel.org,
	linux-mtd@lists.infradead.org, linux-spi@vger.kernel.org,
	cyrille.pitchen@wedev4u.fr, pp@emlix.com, Zhiqiang.Hou@nxp.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/3] spi: spi-mem: Fix a typo in the documentation of struct spi_mem
Date: Thu, 2 Aug 2018 15:09:45 +0200	[thread overview]
Message-ID: <20180802150945.44cc8328@bbrezillon> (raw)
In-Reply-To: <1533214434-28761-2-git-send-email-frieder.schrempf@exceet.de>

On Thu,  2 Aug 2018 14:53:52 +0200
Frieder Schrempf <frieder.schrempf@exceet.de> wrote:

We usually try to avoid empty commit message, even if this one is
pretty obvious, I'd suggest adding something here.

"
Fix a typo in the @drvpriv description.
"

?

> Signed-off-by: Frieder Schrempf <frieder.schrempf@exceet.de>

Acked-by: Boris Brezillon <boris.brezillon@bootlin.com>

> ---
>  include/linux/spi/spi-mem.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/linux/spi/spi-mem.h b/include/linux/spi/spi-mem.h
> index 4fa34a2..72cc9bc 100644
> --- a/include/linux/spi/spi-mem.h
> +++ b/include/linux/spi/spi-mem.h
> @@ -124,7 +124,7 @@ struct spi_mem_op {
>  /**
>   * struct spi_mem - describes a SPI memory device
>   * @spi: the underlying SPI device
> - * @drvpriv: spi_mem_drviver private data
> + * @drvpriv: spi_mem_driver private data
>   *
>   * Extra information that describe the SPI memory device and may be needed by
>   * the controller to properly handle this device should be placed here.

  reply	other threads:[~2018-08-02 13:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-02 12:53 [PATCH v3 0/3] Extend the SPI mem interface to set a custom memory name Frieder Schrempf
2018-08-02 12:53 ` [PATCH v3 1/3] spi: spi-mem: Fix a typo in the documentation of struct spi_mem Frieder Schrempf
2018-08-02 13:09   ` Boris Brezillon [this message]
2018-08-02 13:39     ` Frieder Schrempf
2018-08-02 14:35       ` Mark Brown
2018-08-02 14:58   ` Applied "spi: spi-mem: Fix a typo in the documentation of struct spi_mem" to the spi tree Mark Brown
2018-08-02 12:53 ` [PATCH v3 2/3] spi: spi-mem: Extend the SPI mem interface to set a custom memory name Frieder Schrempf
2018-08-02 13:12   ` Boris Brezillon
2018-08-02 12:53 ` [PATCH v3 3/3] mtd: m25p80: Call spi_mem_get_name() to let controller set a custom name Frieder Schrempf
2018-08-02 13:14   ` Boris Brezillon
2018-08-02 14:58   ` Applied "mtd: m25p80: Call spi_mem_get_name() to let controller set a custom 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=20180802150945.44cc8328@bbrezillon \
    --to=boris.brezillon@bootlin.com \
    --cc=Zhiqiang.Hou@nxp.com \
    --cc=broonie@kernel.org \
    --cc=computersforpeace@gmail.com \
    --cc=cyrille.pitchen@wedev4u.fr \
    --cc=dwmw2@infradead.org \
    --cc=frieder.schrempf@exceet.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=marek.vasut@gmail.com \
    --cc=pp@emlix.com \
    --cc=richard@nod.at \
    /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).