linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v2 1/3] video: clps711x: Add new Cirrus Logic CLPS711X framebuffer driver
Date: Fri, 23 May 2014 14:32:08 +0000	[thread overview]
Message-ID: <537F5BE8.5020102@ti.com> (raw)
In-Reply-To: <1397285583-15187-1-git-send-email-shc_work@mail.ru>

[-- Attachment #1: Type: text/plain, Size: 890 bytes --]

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?

 Tomi



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2014-05-23 14:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-12  6:53 [PATCH v2 1/3] video: clps711x: Add new Cirrus Logic CLPS711X framebuffer driver Alexander Shiyan
2014-04-24  5:03 ` Alexander Shiyan
2014-04-24  7:57 ` Tomi Valkeinen
2014-04-24  8:39 ` Tomi Valkeinen
2014-04-30 11:14 ` Tomi Valkeinen
2014-05-05  5:06 ` Olof Johansson
2014-05-07  9:40 ` Tomi Valkeinen
2014-05-08 10:14 ` Tomi Valkeinen
2014-05-16 22:56 ` Olof Johansson
2014-05-23 12:31 ` Tomi Valkeinen
2014-05-23 12:43 ` Tomi Valkeinen
2014-05-23 13:48 ` Arnd Bergmann
2014-05-23 14:10 ` Tomi Valkeinen
2014-05-23 14:14 ` Arnd Bergmann
2014-05-23 14:26 ` Tomi Valkeinen
2014-05-23 14:32 ` Tomi Valkeinen [this message]

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=537F5BE8.5020102@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=linux-fbdev@vger.kernel.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).