From: "Uwe Kleine-König" <u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
Cc: "Max Schwarz"
<max.schwarz-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org>,
"Doug Anderson"
<dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
"Linux I2C" <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Jean Delvare" <jdelvare-l3A5Bk7waGM@public.gmane.org>,
"Heiko Stübner" <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
Subject: Re: [PATCH] i2c: rk3x: add Kconfig dependency on COMMON_CLK
Date: Mon, 24 Nov 2014 10:59:55 +0100 [thread overview]
Message-ID: <20141124095954.GR4431@pengutronix.de> (raw)
In-Reply-To: <20141124095800.GE3733@katana>
On Mon, Nov 24, 2014 at 10:58:00AM +0100, Wolfram Sang wrote:
>
> > > Applied to for-next, thanks!
> > Just for me to learn: is your for-next stable once pushed?
>
> Nope, I push manually when I feel comfortable. That might change,
> though.
>
> > As you didn't push out yet, it's
> >
> > Fixes: 5a6f1566f6a0 ("i2c: rk3x: handle dynamic clock rate changes correctly")
>
> Actually, it is 249051f49907. I rebased my internal i2c/for-3.19 tree to
> fix an authorship and merged that into i2c/for-next. For those reasons,
> my current policy is to use "Fixes:" only for commits which hit the
> linus-tree. I probably shouldn't do such things, but as long as I was
> working on my own, this worked pretty well ;)
If it's not stable you can even squash in the fix. In this case the
commit log drill was superfluous for this commit, but (hopefully) still
useful for the future.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2014-11-24 9:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 0:32 [PATCH] i2c: rk3x: add Kconfig dependency on COMMON_CLK Max Schwarz
2014-11-24 8:05 ` Uwe Kleine-König
[not found] ` <20141124080509.GK4431-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2014-11-24 9:31 ` Wolfram Sang
2014-11-24 9:38 ` Uwe Kleine-König
[not found] ` <20141124093823.GN4431-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2014-11-24 9:58 ` Wolfram Sang
2014-11-24 9:59 ` Uwe Kleine-König [this message]
[not found] ` <20141124095954.GR4431-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2014-11-24 10:06 ` Wolfram Sang
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=20141124095954.GR4431@pengutronix.de \
--to=u.kleine-koenig-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org \
--cc=jdelvare-l3A5Bk7waGM@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=max.schwarz-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.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).