From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Grygorii Strashko <grygorii.strashko-l0cyMroinI0@public.gmane.org>
Cc: santosh.shilimkar-l0cyMroinI0@public.gmane.org,
linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
m-karicheri2-l0cyMroinI0@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org
Subject: Re: [PATCH 1/2] spi: davinci: fix SPI_NO_CS functionality
Date: Thu, 21 Aug 2014 13:10:15 -0500 [thread overview]
Message-ID: <20140821181015.GL24407@sirena.org.uk> (raw)
In-Reply-To: <1408634706-5762-2-git-send-email-grygorii.strashko-l0cyMroinI0@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 310 bytes --]
On Thu, Aug 21, 2014 at 06:25:05PM +0300, Grygorii Strashko wrote:
> The driver should not touch CS lines if SPI_NO_CS flag is set.
> This patch fixes it as this functionality was broken accidentally
> by
> commit a88e34ea213e1b ("spi: davinci: add support to configure gpio cs through dt").
Applied, thanks.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-08-21 18:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 15:25 [PATCH 0/2] spi: davinci: fixes and updates Grygorii Strashko
[not found] ` <1408634706-5762-1-git-send-email-grygorii.strashko-l0cyMroinI0@public.gmane.org>
2014-08-21 15:25 ` [PATCH 1/2] spi: davinci: fix SPI_NO_CS functionality Grygorii Strashko
[not found] ` <1408634706-5762-2-git-send-email-grygorii.strashko-l0cyMroinI0@public.gmane.org>
2014-08-21 18:10 ` Mark Brown [this message]
2014-08-21 15:25 ` [PATCH 2/2] spi: davinci: support adding delay between transmission Grygorii Strashko
[not found] ` <1408634706-5762-3-git-send-email-grygorii.strashko-l0cyMroinI0@public.gmane.org>
2014-08-21 18:20 ` Mark Brown
[not found] ` <20140821182035.GM24407-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-08-22 13:33 ` Grygorii Strashko
[not found] ` <53F74695.3010902-l0cyMroinI0@public.gmane.org>
2014-08-22 15:06 ` Mark Brown
[not found] ` <20140822150644.GX24407-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-09-05 14:21 ` Grygorii Strashko
[not found] ` <5409C704.5070303-l0cyMroinI0@public.gmane.org>
2014-09-06 14:31 ` Mark Brown
[not found] ` <20140906143113.GI2601-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-09-08 13:30 ` Grygorii Strashko
[not found] ` <540DAF91.6090002-l0cyMroinI0@public.gmane.org>
2014-09-08 14:39 ` 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=20140821181015.GL24407@sirena.org.uk \
--to=broonie-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=grygorii.strashko-l0cyMroinI0@public.gmane.org \
--cc=ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=m-karicheri2-l0cyMroinI0@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=santosh.shilimkar-l0cyMroinI0@public.gmane.org \
/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).