On 23/05/14 17:27, Alexander Shiyan wrote:

quoted

But I don't want to make this more difficult for you than it needs to.
As I said, I'm fine with the current patches, if we skip 3.16 and get
them to linux-next right after the merge window. If nobody would use the
new driver in 3.16 anyway (in your proposal above), would this be the
easiest way?

This is the only way to announce initial multiplatform support (in case we will
use two differrent drivers).
Another (easiest) way is to use the current patchset...

If the old driver doesn't even play well with multiplatform, and is thus
blocking moving the SoC to multiplatform, I'd just get done with it in
one go.

So I would recommend pushing the new driver and the removal of the old
one for 3.17, and having those changes in linux-next right after the
3.16 merge window.

Is that ok?

 Tomi