public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: <Tudor.Ambarus@microchip.com>
To: <michael@walle.cc>
Cc: vigneshr@ti.com, richard@nod.at, linux-mtd@lists.infradead.org,
	linux-kernel@vger.kernel.org, miquel.raynal@bootlin.com
Subject: Re: [PATCH v2] mtd: spi-nor: remove unused enum spi_nor_ops
Date: Thu, 16 Jan 2020 11:06:54 +0000	[thread overview]
Message-ID: <2612409.6oCxq906ie@localhost.localdomain> (raw)
In-Reply-To: <20200113223248.15743-1-michael@walle.cc>

On Tuesday, January 14, 2020 12:32:48 AM EET Michael Walle wrote:
> The ops aren't used in any SPI controller. Therefore, remove them

substituted SPI/SPI-NOR because the controller_ops struct is specific just for 
the SPI-NOR controllers.

> altogether.
> 
> Signed-off-by: Michael Walle <michael@walle.cc>
> ---
> This patch superseeds the following two patches (thus v2):
> https://lore.kernel.org/linux-mtd/20200107222317.3527-1-michael@walle.cc/
> https://lore.kernel.org/linux-mtd/20200107222317.3527-2-michael@walle.cc/
> 
>  drivers/mtd/spi-nor/aspeed-smc.c      |  4 +--
>  drivers/mtd/spi-nor/cadence-quadspi.c |  4 +--
>  drivers/mtd/spi-nor/hisi-sfc.c        |  4 +--
>  drivers/mtd/spi-nor/spi-nor.c         | 36 +++++++++++++--------------
>  include/linux/mtd/spi-nor.h           | 12 ++-------
>  5 files changed, 26 insertions(+), 34 deletions(-)

Applied to spi-nor/next.

Thanks,
ta


______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

      reply	other threads:[~2020-01-16 11:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-13 22:32 [PATCH v2] mtd: spi-nor: remove unused enum spi_nor_ops Michael Walle
2020-01-16 11:06 ` 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=2612409.6oCxq906ie@localhost.localdomain \
    --to=tudor.ambarus@microchip.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=michael@walle.cc \
    --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