From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] pinctrl: rockchip: fix offset of mux registers for rk3188
Date: Thu, 03 Apr 2014 16:20:45 +0200 [thread overview]
Message-ID: <1810753.STDdFhitt6@diego> (raw)
In-Reply-To: <CACRpkda9Lh19sfkxs3=dNWbg4FgkAtY2tJdMQik=TGs8wUkYfA@mail.gmail.com>
Am Donnerstag, 3. April 2014, 16:10:46 schrieb Linus Walleij:
> On Mon, Mar 24, 2014 at 11:36 PM, Beniamino Galvani <b.galvani@gmail.com>
wrote:
> > The correct value of .mux_offset for rk3188 seems to be 0x60
> > instead of 0x68.
> >
> > Signed-off-by: Beniamino Galvani <b.galvani@gmail.com>
>
> Patch applied to fixes with Heiko's Review tag and also
> copied some info from the conversation into the commit message.
small protest note
"Heikki adds:" - sounds somehow finish or swedish, but who is this guy? ;-)
But it doesn't really matter, so no need to roll it back
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Beniamino Galvani <b.galvani@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pinctrl: rockchip: fix offset of mux registers for rk3188
Date: Thu, 03 Apr 2014 16:20:45 +0200 [thread overview]
Message-ID: <1810753.STDdFhitt6@diego> (raw)
In-Reply-To: <CACRpkda9Lh19sfkxs3=dNWbg4FgkAtY2tJdMQik=TGs8wUkYfA@mail.gmail.com>
Am Donnerstag, 3. April 2014, 16:10:46 schrieb Linus Walleij:
> On Mon, Mar 24, 2014 at 11:36 PM, Beniamino Galvani <b.galvani@gmail.com>
wrote:
> > The correct value of .mux_offset for rk3188 seems to be 0x60
> > instead of 0x68.
> >
> > Signed-off-by: Beniamino Galvani <b.galvani@gmail.com>
>
> Patch applied to fixes with Heiko's Review tag and also
> copied some info from the conversation into the commit message.
small protest note
"Heikki adds:" - sounds somehow finish or swedish, but who is this guy? ;-)
But it doesn't really matter, so no need to roll it back
Heiko
next prev parent reply other threads:[~2014-04-03 14:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 22:36 [PATCH] pinctrl: rockchip: fix offset of mux registers for rk3188 Beniamino Galvani
2014-03-24 22:36 ` Beniamino Galvani
2014-03-24 23:14 ` Heiko Stübner
2014-03-24 23:14 ` Heiko Stübner
2014-03-25 19:43 ` Beniamino Galvani
2014-03-25 19:43 ` Beniamino Galvani
2014-03-25 23:56 ` [PATCH 0/2] pinctrl: rockchip: fix handling of first pinbank Heiko Stübner
2014-03-25 23:56 ` Heiko Stübner
2014-03-25 23:57 ` [PATCH 1/2] pinctrl: rockchip: add return value to rockchip_set_mux Heiko Stübner
2014-03-25 23:57 ` Heiko Stübner
2014-03-25 23:57 ` [PATCH 2/2] pinctrl: rockchip: handle first half of rk3188-bank0 correctly Heiko Stübner
2014-03-25 23:57 ` Heiko Stübner
2014-04-03 14:13 ` [PATCH 0/2] pinctrl: rockchip: fix handling of first pinbank Linus Walleij
2014-04-03 14:13 ` Linus Walleij
2014-04-03 14:10 ` [PATCH] pinctrl: rockchip: fix offset of mux registers for rk3188 Linus Walleij
2014-04-03 14:10 ` Linus Walleij
2014-04-03 14:20 ` Heiko Stübner [this message]
2014-04-03 14:20 ` Heiko Stübner
2014-04-03 15:27 ` Linus Walleij
2014-04-03 15:27 ` Linus Walleij
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=1810753.STDdFhitt6@diego \
--to=heiko@sntech.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.