From: maxime.ripard@bootlin.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: dts: sunxi: Switch MMC nodes away from cd-inverted property
Date: Fri, 2 Feb 2018 09:54:42 +0100 [thread overview]
Message-ID: <20180202085442.adhkkuymltlw5r2t@flea.lan> (raw)
In-Reply-To: <1517498160.5907.6.camel@tuxera.com>
Hi,
On Thu, Feb 01, 2018 at 05:16:00PM +0200, Tuomas Tynkkynen wrote:
> Hi Maxime,
>
> On Thu, 2018-01-04 at 16:03 +0100, Maxime Ripard wrote:
> > On Fri, Dec 22, 2017 at 10:57:37PM +0200, Tuomas Tynkkynen wrote:
> > > Using the cd-inverted property is not useful when GPIOs are used as
> > > card
> > > detects since the polarity can be specified with the usual
> > > GPIO_ACTIVE_(HIGH|LOW) GPIO flags. It has also caused confusion for
> > > U-Boot developers, so migrate all sunxi boards away from cd-
> > > inverted.
> > >
> > > Signed-off-by: Tuomas Tynkkynen <tuomas@tuxera.com>
> >
> > Acked-by: Maxime Ripard <maxime.ripard@free-electrons.com>
>
> I was assuming these patches will go in through the sunxi tree but I
> don't see them applied anywhere, have these patches fallen through the
> cracks perhaps?
It did, sorry.
I queued both for 4.17, thanks!
Maxime
--
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180202/89e6bdd6/attachment.sig>
prev parent reply other threads:[~2018-02-02 8:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 20:57 [PATCH 1/2] ARM: dts: sunxi: Switch MMC nodes away from cd-inverted property Tuomas Tynkkynen
2017-12-22 20:57 ` [PATCH 2/2] arm64: " Tuomas Tynkkynen
2018-01-04 15:04 ` Maxime Ripard
2018-01-04 15:03 ` [PATCH 1/2] ARM: " Maxime Ripard
2018-02-01 15:16 ` Tuomas Tynkkynen
2018-02-02 8:54 ` Maxime Ripard [this message]
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=20180202085442.adhkkuymltlw5r2t@flea.lan \
--to=maxime.ripard@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.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