From: javier.martinez@collabora•co.uk (Javier Martinez Canillas)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 1/4] Revert "spi: s3c64xx: Added provision for dedicated cs pin"
Date: Thu, 17 Jul 2014 21:33:35 +0200 [thread overview]
Message-ID: <53C8250F.6070006@collabora.co.uk> (raw)
In-Reply-To: <20140717184656.GB17528@sirena.org.uk>
Hello Mark,
On 07/17/2014 08:46 PM, Mark Brown wrote:
> On Wed, Jul 16, 2014 at 05:19:07PM +0200, Javier Martinez Canillas wrote:
>> This reverts commit 3146beec21b64f4551fcf0ac148381d54dc41b1b.
>
> For the benefit of those who haven't memorized the SHA1s of every commit
> that's "spi: s3c64xx: Added provision for dedicated cs pin" - please
> include the human readable format whenever you reference a SHA1.
>
Ok, I'll take into account for the next time.
> I've applied this.
>
Thanks a lot for your help and sorry for all the inconveniences that this series
caused to you.
Best regards,
Javier
next prev parent reply other threads:[~2014-07-17 19:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 15:19 [PATCH 0/4] spi: s3c64xx: fix DT binding breakage Javier Martinez Canillas
2014-07-16 15:19 ` [PATCH 1/4] Revert "spi: s3c64xx: Added provision for dedicated cs pin" Javier Martinez Canillas
2014-07-17 18:46 ` Mark Brown
2014-07-17 19:33 ` Javier Martinez Canillas [this message]
2014-07-16 15:19 ` [PATCH 2/4] spi: s3c64xx: use the generic SPI "cs-gpios" property Javier Martinez Canillas
2014-07-17 18:48 ` Mark Brown
2014-07-16 15:19 ` [PATCH 3/4] spi: samsung: Update binding documentation Javier Martinez Canillas
2014-07-17 18:48 ` Mark Brown
2014-07-16 15:19 ` [PATCH 4/4] ARM: DTS: fix the chip select gpios definition in the SPI nodes Javier Martinez Canillas
2014-07-17 18:49 ` Mark Brown
2014-07-18 19:16 ` Kukjin Kim
2014-07-16 15:50 ` [PATCH 0/4] spi: s3c64xx: fix DT binding breakage Naveen Krishna Ch
2014-07-16 16:02 ` Mark Brown
2014-07-16 16:33 ` Javier Martinez Canillas
2014-07-16 16:47 ` Naveen Krishna Ch
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=53C8250F.6070006@collabora.co.uk \
--to=javier.martinez@collabora$(echo .)co.uk \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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