All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Sanchayan Maity <maitysanchayan@gmail.com>
Cc: stefan@agner.ch, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org
Subject: Re: [PATCH v2 1/4] spi: spi-fsl-dspi: Fix SPI transfer issue when using multiple SPI_IOC_MESSAGE
Date: Mon, 21 Nov 2016 19:18:47 +0000	[thread overview]
Message-ID: <20161121191847.vg32cwople4qmini@sirena.org.uk> (raw)
In-Reply-To: <bbdbc8df434dd2af74eb351b799a2812a1c1967e.1479706671.git.maitysanchayan@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 485 bytes --]

On Mon, Nov 21, 2016 at 11:24:01AM +0530, Sanchayan Maity wrote:
> Current DMA implementation had a bug where the DMA transfer would
> exit the loop in dspi_transfer_one_message after the completion of
> a single transfer. This results in a multi message transfer submitted
> with SPI_IOC_MESSAGE to terminate incorrectly without an error.

Please don't resend already applied patches.  If there are any changes
needed please send incremental changes on top of what's already applied.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Sanchayan Maity <maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: stefan-XLVq0VzYD2Y@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2 1/4] spi: spi-fsl-dspi: Fix SPI transfer issue when using multiple SPI_IOC_MESSAGE
Date: Mon, 21 Nov 2016 19:18:47 +0000	[thread overview]
Message-ID: <20161121191847.vg32cwople4qmini@sirena.org.uk> (raw)
In-Reply-To: <bbdbc8df434dd2af74eb351b799a2812a1c1967e.1479706671.git.maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 485 bytes --]

On Mon, Nov 21, 2016 at 11:24:01AM +0530, Sanchayan Maity wrote:
> Current DMA implementation had a bug where the DMA transfer would
> exit the loop in dspi_transfer_one_message after the completion of
> a single transfer. This results in a multi message transfer submitted
> with SPI_IOC_MESSAGE to terminate incorrectly without an error.

Please don't resend already applied patches.  If there are any changes
needed please send incremental changes on top of what's already applied.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/4] spi: spi-fsl-dspi: Fix SPI transfer issue when using multiple SPI_IOC_MESSAGE
Date: Mon, 21 Nov 2016 19:18:47 +0000	[thread overview]
Message-ID: <20161121191847.vg32cwople4qmini@sirena.org.uk> (raw)
In-Reply-To: <bbdbc8df434dd2af74eb351b799a2812a1c1967e.1479706671.git.maitysanchayan@gmail.com>

On Mon, Nov 21, 2016 at 11:24:01AM +0530, Sanchayan Maity wrote:
> Current DMA implementation had a bug where the DMA transfer would
> exit the loop in dspi_transfer_one_message after the completion of
> a single transfer. This results in a multi message transfer submitted
> with SPI_IOC_MESSAGE to terminate incorrectly without an error.

Please don't resend already applied patches.  If there are any changes
needed please send incremental changes on top of what's already applied.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20161121/59a1e93d/attachment.sig>

  reply	other threads:[~2016-11-21 19:19 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-21  5:54 [PATCH v2 0/4] Fixes for Vybrid SPI DMA implementation Sanchayan Maity
2016-11-21  5:54 ` Sanchayan Maity
2016-11-21  5:54 ` Sanchayan Maity
2016-11-21  5:54 ` [PATCH v2 1/4] spi: spi-fsl-dspi: Fix SPI transfer issue when using multiple SPI_IOC_MESSAGE Sanchayan Maity
2016-11-21  5:54   ` Sanchayan Maity
2016-11-21  5:54   ` Sanchayan Maity
2016-11-21 19:18   ` Mark Brown [this message]
2016-11-21 19:18     ` Mark Brown
2016-11-21 19:18     ` Mark Brown
2016-11-21 19:14     ` maitysanchayan
2016-11-21 19:14       ` maitysanchayan at gmail.com
2016-11-21 19:14       ` maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w
2016-11-21 19:18       ` maitysanchayan
2016-11-21 19:18         ` maitysanchayan at gmail.com
2016-11-22 16:22         ` Mark Brown
2016-11-22 16:22           ` Mark Brown
2016-11-22 16:22           ` Mark Brown
2016-11-21  5:54 ` [PATCH v2 2/4] spi: spi-fsl-dspi: Fix continuous selection format Sanchayan Maity
2016-11-21  5:54   ` Sanchayan Maity
2016-11-21  5:54   ` Sanchayan Maity
2016-11-21 23:15   ` Stefan Agner
2016-11-21 23:15     ` Stefan Agner
2016-11-22  6:11     ` maitysanchayan
2016-11-22  6:11       ` maitysanchayan at gmail.com
2016-11-22  6:11       ` maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w
2016-11-21  5:54 ` [PATCH v2 3/4] spi: spi-fsl-dspi: Fix incorrect DMA setup Sanchayan Maity
2016-11-21  5:54   ` Sanchayan Maity
2016-11-21 23:16   ` Stefan Agner
2016-11-21 23:16     ` Stefan Agner
2016-11-21 23:16     ` Stefan Agner
2016-11-22 17:26   ` Applied "spi: spi-fsl-dspi: Fix incorrect DMA setup" to the spi tree Mark Brown
2016-11-22 17:26     ` Mark Brown
2016-11-21  5:54 ` [PATCH v2 4/4] spi: spi-fsl-dspi: Minor code cleanup and error path fixes Sanchayan Maity
2016-11-21  5:54   ` Sanchayan Maity
2016-11-21 23:22   ` Stefan Agner
2016-11-21 23:22     ` Stefan Agner
2016-11-21 23:22     ` Stefan Agner
2016-11-22  6:12     ` maitysanchayan
2016-11-22  6:12       ` maitysanchayan at gmail.com

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=20161121191847.vg32cwople4qmini@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=maitysanchayan@gmail.com \
    --cc=stefan@agner.ch \
    /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.