From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: imx6qdl-sabresd: set swbst_reg as vbus's parent reg
Date: Thu, 12 Mar 2015 10:19:19 +0800 [thread overview]
Message-ID: <20150312021917.GD20455@dragon> (raw)
In-Reply-To: <20150312015417.GA31064@shlinux2>
On Thu, Mar 12, 2015 at 09:54:18AM +0800, Peter Chen wrote:
> On Wed, Mar 11, 2015 at 09:24:25AM +0800, Shawn Guo wrote:
> > On Fri, Mar 06, 2015 at 04:04:20PM +0800, Peter Chen wrote:
> > > USB vbus 5V is from PMIC SWBST, so set swbst_reg as vbus's
> > > parent reg, it fixed a bug that the voltage of vbus is incorrect
> > > due to swbst_reg is disabled after boots up.
> > >
> > > Cc: stable <stable@vger.kernel.org>
> >
> > It's more idiomatic to put the line in this way:
> >
> > Cc: stable at vger.kernel.org
> >
>
> One benefit for using <stable@vger.kernel.org> over than
> stable at vger.kernel.org directly is it can add "# v3.x+"
> at the last of Cc tag if you want git send Cc tag.
>
> Cc: <stable@vger.kernel.org> #3.x+ /* git can work */
>
> Cc: stable at vger.kernel.org #3.x+ /* git can't work */
Yeah, that's true. What I was really questioning is not
< >, but the alias 'stable' right before it.
Shawn
prev parent reply other threads:[~2015-03-12 2:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 8:04 [PATCH 1/2] ARM: imx6qdl-sabresd: set swbst_reg as vbus's parent reg Peter Chen
2015-03-06 8:04 ` [PATCH 2/2] ARM: imx6sl-evk: " Peter Chen
2015-03-11 1:24 ` [PATCH 1/2] ARM: imx6qdl-sabresd: " Shawn Guo
2015-03-11 9:57 ` Greg KH
2015-03-12 1:54 ` Peter Chen
2015-03-12 2:19 ` Shawn Guo [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=20150312021917.GD20455@dragon \
--to=shawn.guo@linaro.org \
--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).