Fri, 23 May 2014 17:32:08 +0300 от Tomi Valkeinen <tomi.valkeinen@xxxxxx>:
> On 23/05/14 17:27, Alexander Shiyan wrote:
>
> >> 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?
For me it is OK, of course. Do I understand correctly that in this case I need
to update patchset which only adds new driver and new Kconfig symbol?
Probably I am add "depend on BROKEN if !ARCH_MULTIPLATFORM" to
the old driver...
---
��.n��������+%������w��{.n�����{����n�r������&��z�ޗ�zf���h���~����������_��+v���)ߣ�
