From: icenowy@aosc.io (icenowy at aosc.io)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] clk: sunxi-ng: v3s: Fix usb otg device reset bit
Date: Sat, 06 May 2017 22:51:25 +0800 [thread overview]
Message-ID: <a7ef1477b9dec8009e9c40bce5d42267@aosc.io> (raw)
In-Reply-To: <20170505200440.zje5s7x2seglxzi6@lukather>
? 2017-05-06 04:04?Maxime Ripard ???
> Hi,
>
> On Fri, May 05, 2017 at 06:31:57PM +0800, Yong Deng wrote:
>> V3S's usb otg device reset bit should be 24, not 23.
>>
>> Signed-off-by: Yong Deng <iemdey@gmail.com>
>> Reviewed-By: Icenowy Zheng <icenowy@aosc.io>
>
> Applied, thanks.
> Maxime
Maybe it should also apply to 4.11 stable?
Cc: stable at vger.kernel.org
next prev parent reply other threads:[~2017-05-06 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 10:31 [PATCH v2] clk: sunxi-ng: v3s: Fix usb otg device reset bit Yong Deng
2017-05-05 20:04 ` Maxime Ripard
2017-05-06 14:51 ` icenowy at aosc.io [this message]
2017-05-09 19:09 ` Maxime Ripard
-- strict thread matches above, loose matches on Subject: below --
2017-05-05 10:38 Yong Deng
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=a7ef1477b9dec8009e9c40bce5d42267@aosc.io \
--to=icenowy@aosc.io \
--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;
as well as URLs for NNTP newsgroup(s).