From: Mark Brown <broonie@kernel.org>
To: Sven Van Asbroeck <thesven73@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Lukas Wunner <lukas@wunner.de>,
linux-spi <linux-spi@vger.kernel.org>,
Simon Han <z.han@kunbus.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Charles Keepax <ckeepax@opensource.cirrus.com>
Subject: Re: [PATCH v1] spi: fix client driver breakages when using GPIO descriptors
Date: Wed, 11 Nov 2020 16:32:00 +0000 [thread overview]
Message-ID: <20201111163200.GC4847@sirena.org.uk> (raw)
In-Reply-To: <CAGngYiVAdPSCEQm5pJdFQ+3VpwNH1vGD6rPNK1_SQK3Uvfbt5A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 367 bytes --]
On Wed, Nov 11, 2020 at 11:24:14AM -0500, Sven Van Asbroeck wrote:
> Now that our minds are still focused on this subject, should
> commit 138c9c32f090 ("spi: spidev: Fix CS polarity if GPIO descriptors
> are used")
> be reverted?
If you think changes should be made to the code please propose patches
making them - reverts are just normal patches with changelogs.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-11-11 16:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 15:07 [PATCH v1] spi: fix client driver breakages when using GPIO descriptors Sven Van Asbroeck
2020-11-09 14:25 ` Andy Shevchenko
2020-11-09 14:41 ` Sven Van Asbroeck
2020-11-11 1:05 ` Linus Walleij
2020-11-11 12:33 ` Mark Brown
2020-11-11 13:36 ` Linus Walleij
2020-11-16 21:06 ` Mark Brown
2020-11-18 1:03 ` Linus Walleij
2020-11-18 11:40 ` Mark Brown
2020-11-24 15:21 ` Linus Walleij
2020-11-24 16:40 ` Mark Brown
2020-11-25 9:19 ` Grant Likely
2020-11-25 9:17 ` Grant Likely
2020-11-11 1:08 ` Linus Walleij
2020-11-11 15:48 ` Mark Brown
2020-11-11 16:24 ` Sven Van Asbroeck
2020-11-11 16:32 ` Mark Brown [this message]
2020-11-12 11:41 ` Charles Keepax
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=20201111163200.GC4847@sirena.org.uk \
--to=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=jonathan.cameron@huawei.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=thesven73@gmail.com \
--cc=z.han@kunbus.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;
as well as URLs for NNTP newsgroup(s).