All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
Cc: linux-fbdev@vger.kernel.org,
	linux-omap mailing list <linux-omap@vger.kernel.org>
Subject: Re: [GIT PULL] OMAP DSS fixes for 3.2-rc
Date: Wed, 23 Nov 2011 07:31:16 +0000	[thread overview]
Message-ID: <1322033476.3015.3.camel@deskari> (raw)
In-Reply-To: <4ECC9DAF.3000005@gmx.de>

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

On Wed, 2011-11-23 at 07:15 +0000, Florian Tobias Schandinat wrote:
> Hi Tomi,
> 
> On 11/18/2011 08:16 AM, Tomi Valkeinen wrote:
> > Hi Florian,
> > 
> > Here are a few OMAP display subsystem fixes for 3.2-rc.
> > 
> > One for the old omapfb, which was missing include module.h, and two for
> > the omapdss fixing issues related to HDMI.
> 
> Pulled, but...

Thanks!

> > The following changes since commit cfcfc9eca2bcbd26a8e206baeb005b055dbf8e37:
> > 
> >   Linux 3.2-rc2 (2011-11-15 15:02:59 -0200)
> 
> ...could you please try to base on something that is already in my tree, perhaps
> just add patches on top of the last pull request you sent me. If you need
> something more recent, that is okay, but don't force me to needlessly update my
> tree.

Ah, of course. I didn't think of that. I'll base the patches on top of
your tree from now on.

 Tomi


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
Cc: linux-fbdev@vger.kernel.org,
	linux-omap mailing list <linux-omap@vger.kernel.org>
Subject: Re: [GIT PULL] OMAP DSS fixes for 3.2-rc
Date: Wed, 23 Nov 2011 09:31:16 +0200	[thread overview]
Message-ID: <1322033476.3015.3.camel@deskari> (raw)
In-Reply-To: <4ECC9DAF.3000005@gmx.de>

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

On Wed, 2011-11-23 at 07:15 +0000, Florian Tobias Schandinat wrote:
> Hi Tomi,
> 
> On 11/18/2011 08:16 AM, Tomi Valkeinen wrote:
> > Hi Florian,
> > 
> > Here are a few OMAP display subsystem fixes for 3.2-rc.
> > 
> > One for the old omapfb, which was missing include module.h, and two for
> > the omapdss fixing issues related to HDMI.
> 
> Pulled, but...

Thanks!

> > The following changes since commit cfcfc9eca2bcbd26a8e206baeb005b055dbf8e37:
> > 
> >   Linux 3.2-rc2 (2011-11-15 15:02:59 -0200)
> 
> ...could you please try to base on something that is already in my tree, perhaps
> just add patches on top of the last pull request you sent me. If you need
> something more recent, that is okay, but don't force me to needlessly update my
> tree.

Ah, of course. I didn't think of that. I'll base the patches on top of
your tree from now on.

 Tomi


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2011-11-23  7:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-18  8:16 [GIT PULL] OMAP DSS fixes for 3.2-rc Tomi Valkeinen
2011-11-18  8:16 ` Tomi Valkeinen
2011-11-23  7:15 ` Florian Tobias Schandinat
2011-11-23  7:31   ` Tomi Valkeinen [this message]
2011-11-23  7:31     ` Tomi Valkeinen

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=1322033476.3015.3.camel@deskari \
    --to=tomi.valkeinen@ti.com \
    --cc=FlorianSchandinat@gmx.de \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-omap@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 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.