From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>,
linux-fbdev@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/4] OMAP: DSS2: Remove suspicous and unused TAAL regulator API usage
Date: Thu, 03 May 2012 13:39:53 +0000 [thread overview]
Message-ID: <20120503133952.GH3955@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1336051407.14378.13.camel@deskari>
[-- Attachment #1: Type: text/plain, Size: 524 bytes --]
On Thu, May 03, 2012 at 04:23:27PM +0300, Tomi Valkeinen wrote:
> On Thu, 2012-05-03 at 14:21 +0100, Mark Brown wrote:
> > On Thu, May 03, 2012 at 04:11:00PM +0300, Tomi Valkeinen wrote:
> > > I've already applied this and the three other patches that you sent in
> > > March to my omapdss tree. Have there been any changes?
> > No, it's a resend - if you've applied these changes they're not showing
> > up in -next.
> Yes, I seem to have forgotten to update my for-next branch. I'll do it
> right away.
Great, thanks!
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>,
linux-fbdev@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/4] OMAP: DSS2: Remove suspicous and unused TAAL regulator API usage
Date: Thu, 3 May 2012 14:39:53 +0100 [thread overview]
Message-ID: <20120503133952.GH3955@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1336051407.14378.13.camel@deskari>
[-- Attachment #1: Type: text/plain, Size: 524 bytes --]
On Thu, May 03, 2012 at 04:23:27PM +0300, Tomi Valkeinen wrote:
> On Thu, 2012-05-03 at 14:21 +0100, Mark Brown wrote:
> > On Thu, May 03, 2012 at 04:11:00PM +0300, Tomi Valkeinen wrote:
> > > I've already applied this and the three other patches that you sent in
> > > March to my omapdss tree. Have there been any changes?
> > No, it's a resend - if you've applied these changes they're not showing
> > up in -next.
> Yes, I seem to have forgotten to update my for-next branch. I'll do it
> right away.
Great, thanks!
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-05-03 13:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 10:57 [PATCH 1/4] OMAP: DSS2: Remove suspicous and unused TAAL regulator API usage Mark Brown
2012-05-03 10:57 ` Mark Brown
2012-05-03 10:57 ` [PATCH 2/4] OMAPDSS: VENC: Check for errors from regulator_enable() Mark Brown
2012-05-03 10:57 ` Mark Brown
2012-05-03 10:57 ` [PATCH 3/4] OMAPDSS: TPO-TD03MTEA1: " Mark Brown
2012-05-03 10:57 ` Mark Brown
2012-05-03 10:57 ` [PATCH 4/4] OMAPDSS: TPO-TD03MTEA1: Correct comment for power on delay Mark Brown
2012-05-03 10:57 ` Mark Brown
2012-05-03 13:11 ` [PATCH 1/4] OMAP: DSS2: Remove suspicous and unused TAAL regulator API usage Tomi Valkeinen
2012-05-03 13:11 ` Tomi Valkeinen
2012-05-03 13:21 ` Mark Brown
2012-05-03 13:21 ` Mark Brown
2012-05-03 13:23 ` Tomi Valkeinen
2012-05-03 13:23 ` Tomi Valkeinen
2012-05-03 13:39 ` Mark Brown [this message]
2012-05-03 13:39 ` Mark Brown
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=20120503133952.GH3955@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=FlorianSchandinat@gmx.de \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@ti.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.