From: Paul Cercueil <paul@crapouillou.net>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Paul Burton <paul.burton@mips.com>,
James Hogan <jhogan@kernel.org>,
od@zcrc.me, linux-mips@vger.kernel.org,
linux-kernel@vger.kernel.org, stable <stable@vger.kernel.org>
Subject: Re: [PATCH] MIPS: lb60: Fix pin mappings
Date: Sat, 08 Jun 2019 12:14:06 +0200 [thread overview]
Message-ID: <1559988846.1815.1@crapouillou.net> (raw)
In-Reply-To: <CACRpkdbKg22OyViYhXS=Vyps=2zQ_dmm23Xr8+dBp+uwwjheuQ@mail.gmail.com>
Le sam. 8 juin 2019 à 0:10, Linus Walleij <linus.walleij@linaro.org> a
écrit :
> On Tue, Jun 4, 2019 at 6:34 PM Paul Cercueil <paul@crapouillou.net>
> wrote:
>
>> The pin mappings introduced in commit 636f8ba67fb6
>> ("MIPS: JZ4740: Qi LB60: Add pinctrl configuration for several
>> drivers")
>> are completely wrong. The pinctrl driver name is incorrect, and the
>> function and group fields are swapped.
>>
>> Fixes: 636f8ba67fb6 ("MIPS: JZ4740: Qi LB60: Add pinctrl
>> configuration for several drivers")
>> Cc: <stable@vger.kernel.org>
>> Signed-off-by: Paul Cercueil <paul@crapouillou.net>
>
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
>
> Such things happen. Are you planning to phase all the board files over
> to use devicetree eventually?
Yes, that's definitely what's planned; right now the blockers are
patchsets [1] and [2]. [1] is ignored by everybody because there's no
maintainer for drivers/memory/. [2] is a year-long effort that still
doesn't show me the light at the end of the tunnel.
[1] https://lkml.org/lkml/2019/6/4/743
[2] https://lkml.org/lkml/2019/5/21/679
Cheers
-Paul
next prev parent reply other threads:[~2019-06-08 10:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 16:33 [PATCH] MIPS: lb60: Fix pin mappings Paul Cercueil
2019-06-07 22:10 ` Linus Walleij
2019-06-08 10:14 ` Paul Cercueil [this message]
2019-06-08 13:39 ` Linus Walleij
2019-06-08 20:25 ` Paul Cercueil
2019-06-11 22:04 ` Paul Burton
2019-06-11 22:22 ` Paul Burton
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=1559988846.1815.1@crapouillou.net \
--to=paul@crapouillou.net \
--cc=jhogan@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=od@zcrc.me \
--cc=paul.burton@mips.com \
--cc=ralf@linux-mips.org \
--cc=stable@vger.kernel.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