All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Franklin S Cooper Jr <fcooper@ti.com>,
	tony@atomide.com, robh+dt@kernel.org, broonie@kernel.org,
	linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
	andy.shevchenko@gmail.com, robert.jarzmik@free.fr,
	nsekhar@ti.com
Subject: Re: [RFC] [PATCH v3 2/4] spi: spi-omap2-mcspi: Select SPI_SPLIT
Date: Thu, 7 Jul 2016 10:33:54 -0700	[thread overview]
Message-ID: <577E9282.1070105@infradead.org> (raw)
In-Reply-To: <1467911871-4508-3-git-send-email-fcooper@ti.com>

On 07/07/16 10:17, Franklin S Cooper Jr wrote:
> The function spi_split will be used by spi-omap2-mcspi to handle a SoC

s/spi_split/sg_split/

> workaround in the SPI driver. Therefore, select SPI_SPLIT so this function

s/SPI_SPLIT/SG_SPLIT/ on line above and in $Subject.

> is available to the driver.
> 
> Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com>
> ---
>  drivers/spi/Kconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig
> index 4b931ec..d6fb8d4 100644
> --- a/drivers/spi/Kconfig
> +++ b/drivers/spi/Kconfig
> @@ -411,6 +411,7 @@ config SPI_OMAP24XX
>  	tristate "McSPI driver for OMAP"
>  	depends on HAS_DMA
>  	depends on ARCH_OMAP2PLUS || COMPILE_TEST
> +	select SG_SPLIT
>  	help
>  	  SPI master controller for OMAP24XX and later Multichannel SPI
>  	  (McSPI) modules.
> 


-- 
~Randy

WARNING: multiple messages have this Message-ID (diff)
From: rdunlap@infradead.org (Randy Dunlap)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] [PATCH v3 2/4] spi: spi-omap2-mcspi: Select SPI_SPLIT
Date: Thu, 7 Jul 2016 10:33:54 -0700	[thread overview]
Message-ID: <577E9282.1070105@infradead.org> (raw)
In-Reply-To: <1467911871-4508-3-git-send-email-fcooper@ti.com>

On 07/07/16 10:17, Franklin S Cooper Jr wrote:
> The function spi_split will be used by spi-omap2-mcspi to handle a SoC

s/spi_split/sg_split/

> workaround in the SPI driver. Therefore, select SPI_SPLIT so this function

s/SPI_SPLIT/SG_SPLIT/ on line above and in $Subject.

> is available to the driver.
> 
> Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com>
> ---
>  drivers/spi/Kconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig
> index 4b931ec..d6fb8d4 100644
> --- a/drivers/spi/Kconfig
> +++ b/drivers/spi/Kconfig
> @@ -411,6 +411,7 @@ config SPI_OMAP24XX
>  	tristate "McSPI driver for OMAP"
>  	depends on HAS_DMA
>  	depends on ARCH_OMAP2PLUS || COMPILE_TEST
> +	select SG_SPLIT
>  	help
>  	  SPI master controller for OMAP24XX and later Multichannel SPI
>  	  (McSPI) modules.
> 


-- 
~Randy

  reply	other threads:[~2016-07-07 17:33 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-07 17:17 [RFC] [PATCH v3 0/4] spi: omap2-mcspi: Use the SPI framework to handle DMA mapping Franklin S Cooper Jr
2016-07-07 17:17 ` Franklin S Cooper Jr
2016-07-07 17:17 ` [RFC] [PATCH v3 2/4] spi: spi-omap2-mcspi: Select SPI_SPLIT Franklin S Cooper Jr
2016-07-07 17:17   ` Franklin S Cooper Jr
2016-07-07 17:33   ` Randy Dunlap [this message]
2016-07-07 17:33     ` Randy Dunlap
     [not found]   ` <1467911871-4508-3-git-send-email-fcooper-l0cyMroinI0@public.gmane.org>
2016-07-08  8:49     ` Applied "spi: omap2-mcspi: Select SPI_SPLIT" to the spi tree Mark Brown
2016-07-08  8:49       ` Mark Brown
2016-07-08  8:49       ` Mark Brown
2016-07-08  8:49       ` Mark Brown
2016-07-08  8:54       ` Sekhar Nori
2016-07-08  8:54         ` Sekhar Nori
2016-07-08  8:54         ` Sekhar Nori
2016-07-08  8:54         ` Sekhar Nori
     [not found] ` <1467911871-4508-1-git-send-email-fcooper-l0cyMroinI0@public.gmane.org>
2016-07-07 17:17   ` [RFC] [PATCH v3 1/4] spi: omap2-mcspi: Add comments for RX only DMA buffer workaround Franklin S Cooper Jr
2016-07-07 17:17     ` Franklin S Cooper Jr
2016-07-07 17:17     ` Franklin S Cooper Jr
     [not found]     ` <1467911871-4508-2-git-send-email-fcooper-l0cyMroinI0@public.gmane.org>
2016-07-08  8:46       ` Mark Brown
2016-07-08  8:46         ` Mark Brown
2016-07-08  8:46         ` Mark Brown
2016-07-07 17:17   ` [RFC] [PATCH v3 3/4] spi: omap2-mcspi: Use the SPI framework to handle DMA mapping Franklin S Cooper Jr
2016-07-07 17:17     ` Franklin S Cooper Jr
2016-07-07 17:17     ` Franklin S Cooper Jr
     [not found]     ` <1467911871-4508-4-git-send-email-fcooper-l0cyMroinI0@public.gmane.org>
2016-07-08  8:49       ` Applied "spi: omap2-mcspi: Use the SPI framework to handle DMA mapping" to the spi tree Mark Brown
2016-07-08  8:49         ` Mark Brown
2016-07-08  8:49         ` Mark Brown
2016-07-08  8:49         ` Mark Brown
2016-07-07 17:17   ` [RFC] [PATCH v3 4/4] ARM: dts: am335x-icev2: Add SPI based NOR Franklin S Cooper Jr
2016-07-07 17:17     ` Franklin S Cooper Jr
2016-07-07 17:17     ` Franklin S Cooper Jr

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=577E9282.1070105@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=andy.shevchenko@gmail.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=fcooper@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=nsekhar@ti.com \
    --cc=robert.jarzmik@free.fr \
    --cc=robh+dt@kernel.org \
    --cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.