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/ |
--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
