All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Kevin Hilman <khilman@linaro.org>,
	Olof Johansson <olof@lixom.net>
Subject: Re: [GIT PULL] OMAPDSS: use new display drivers
Date: Thu, 29 Aug 2013 09:26:21 +0300	[thread overview]
Message-ID: <521EE98D.9070209@ti.com> (raw)
In-Reply-To: <20130829061923.GM7656@atomide.com>

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

On 29/08/13 09:19, Tony Lindgren wrote:
> * Tomi Valkeinen <tomi.valkeinen@ti.com> [130828 00:59]:
>> Hi,
>>
>> Here's a pull request for the board file changes to take the new display
>> drivers into use.
> 
> OK great.
>  
>> If there's an "early" pull request going to Linus during the merge window, it'd
>> be nice to have these in that request. That would give me time to send a pull
>> request to Linus containing removal of the old, no longer used, drivers.
> 
> Nice to see that this is not conflicting with anything in linux next :)

Did you add the series to your for-next branch?

> I suggest you keep this branch immutable in case it need to be merged to arm-soc
> tree, and merge it yourself along with the DSS patches. That way you

I do feel a bit uneasy with merging lots of arch changes via fbdev tree,
but yes, I guess I can do that. Is that an "ack" from you for all the
patches? If I do merge it via fbdev, I want to have at least acked-by in
the commits. If that was an ack, I'll add them, but it means I need to
update the branch.

> don't have a dependency to arm-soc for removal of the old drivers.

The dependency is run-time dependency, so the removal series does not
need to be based on this. As long as this series is merged first, things
should work.

 Tomi



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

WARNING: multiple messages have this Message-ID (diff)
From: tomi.valkeinen@ti.com (Tomi Valkeinen)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] OMAPDSS: use new display drivers
Date: Thu, 29 Aug 2013 09:26:21 +0300	[thread overview]
Message-ID: <521EE98D.9070209@ti.com> (raw)
In-Reply-To: <20130829061923.GM7656@atomide.com>

On 29/08/13 09:19, Tony Lindgren wrote:
> * Tomi Valkeinen <tomi.valkeinen@ti.com> [130828 00:59]:
>> Hi,
>>
>> Here's a pull request for the board file changes to take the new display
>> drivers into use.
> 
> OK great.
>  
>> If there's an "early" pull request going to Linus during the merge window, it'd
>> be nice to have these in that request. That would give me time to send a pull
>> request to Linus containing removal of the old, no longer used, drivers.
> 
> Nice to see that this is not conflicting with anything in linux next :)

Did you add the series to your for-next branch?

> I suggest you keep this branch immutable in case it need to be merged to arm-soc
> tree, and merge it yourself along with the DSS patches. That way you

I do feel a bit uneasy with merging lots of arch changes via fbdev tree,
but yes, I guess I can do that. Is that an "ack" from you for all the
patches? If I do merge it via fbdev, I want to have at least acked-by in
the commits. If that was an ack, I'll add them, but it means I need to
update the branch.

> don't have a dependency to arm-soc for removal of the old drivers.

The dependency is run-time dependency, so the removal series does not
need to be based on this. As long as this series is merged first, things
should work.

 Tomi


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 901 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130829/0cc4166d/attachment-0001.sig>

  reply	other threads:[~2013-08-29  6:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-28  7:52 [GIT PULL] OMAPDSS: use new display drivers Tomi Valkeinen
2013-08-28  7:52 ` Tomi Valkeinen
2013-08-29  6:19 ` Tony Lindgren
2013-08-29  6:19   ` Tony Lindgren
2013-08-29  6:26   ` Tomi Valkeinen [this message]
2013-08-29  6:26     ` Tomi Valkeinen
2013-08-29  6:35     ` Tony Lindgren
2013-08-29  6:35       ` Tony Lindgren
2013-08-29  6:58       ` Tomi Valkeinen
2013-08-29  6:58         ` Tomi Valkeinen
2013-08-29  7:07         ` Tony Lindgren
2013-08-29  7:07           ` Tony Lindgren

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=521EE98D.9070209@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=khilman@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=tony@atomide.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.