Hey Wolfram,
On Mon, Nov 24, 2014 at 10:31:16AM +0100, Wolfram Sang wrote:
> On Mon, Nov 24, 2014 at 09:05:09AM +0100, Uwe Kleine-König wrote:
> > Hello Max,
> >
> > On Mon, Nov 24, 2014 at 01:32:27AM +0100, Max Schwarz wrote:
> > > Now that we are using the clk notifier framework we get compile errors
> > > without COMMON_CLK. But the driver fails to probe without COMMON_CLK
> > > anyways, so just add that as a Kconfig dependency.
> > Hmm, I wonder how a kernel that fails to compile can even start probing
> > ... :-)
> >
> > Anyhow, it would be nice to quote the compiler error you fix here and
> > point out the patch that failed to add the needed dependency.
>
> Yes, that would be perfect. But for fixing the breakage in linux-next we
> created, this is good enough for me.
>
> Applied to for-next, thanks!
Just for me to learn: is your for-next stable once pushed?
As you didn't push out yet, it's
Fixes: 5a6f1566f6a0 ("i2c: rk3x: handle dynamic clock rate changes correctly")
party on,
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
