All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] ARM: OMAP: add corrected DSS regulator supplies
Date: Wed, 12 Jun 2013 07:05:21 -0700	[thread overview]
Message-ID: <20130612140520.GT8164@atomide.com> (raw)
In-Reply-To: <51B84FA5.80409@ti.com>

* Tomi Valkeinen <tomi.valkeinen@ti.com> [130612 03:44]:
> On 31/05/13 10:37, Tomi Valkeinen wrote:
> > Hi Tony,
> > 
> > Here are a few patches adding corrected DSS regulator supplies. The current
> > ones in the board files are not really correct, although the dss driver works
> > ok with them.
> > 
> > So these patches add new regulator supply entries. When these are merged, I'll
> > change omapdss driver to use the new ones, instead of the old ones. After that,
> > we can remove the old ones from the board files.
> > 
> > Note that these patches were also present in the big DSS series I sent
> > yesterday. There's no reason for these patches to be there, so I'm sending them
> > separately, and will drop these from my DSS series.
> 
> Ping.

Thanks, applying into omap-for-v.311/fixes-non-critical.

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM: OMAP: add corrected DSS regulator supplies
Date: Wed, 12 Jun 2013 07:05:21 -0700	[thread overview]
Message-ID: <20130612140520.GT8164@atomide.com> (raw)
In-Reply-To: <51B84FA5.80409@ti.com>

* Tomi Valkeinen <tomi.valkeinen@ti.com> [130612 03:44]:
> On 31/05/13 10:37, Tomi Valkeinen wrote:
> > Hi Tony,
> > 
> > Here are a few patches adding corrected DSS regulator supplies. The current
> > ones in the board files are not really correct, although the dss driver works
> > ok with them.
> > 
> > So these patches add new regulator supply entries. When these are merged, I'll
> > change omapdss driver to use the new ones, instead of the old ones. After that,
> > we can remove the old ones from the board files.
> > 
> > Note that these patches were also present in the big DSS series I sent
> > yesterday. There's no reason for these patches to be there, so I'm sending them
> > separately, and will drop these from my DSS series.
> 
> Ping.

Thanks, applying into omap-for-v.311/fixes-non-critical.

Regards,

Tony

  reply	other threads:[~2013-06-12 14:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-31  7:37 [PATCH 0/3] ARM: OMAP: add corrected DSS regulator supplies Tomi Valkeinen
2013-05-31  7:37 ` Tomi Valkeinen
2013-05-31  7:37 ` [PATCH 1/3] ARM: OMAP: fix dsi regulator names Tomi Valkeinen
2013-05-31  7:37   ` Tomi Valkeinen
2013-05-31  7:37 ` [PATCH 2/3] ARM: OMAP: add vdds_dsi supply for omapdss_dpi.0 Tomi Valkeinen
2013-05-31  7:37   ` Tomi Valkeinen
2013-05-31  7:37 ` [PATCH 3/3] ARM: OMAP: add vdds_sdi supply for omapdss_sdi.0 Tomi Valkeinen
2013-05-31  7:37   ` Tomi Valkeinen
2013-06-12 10:38 ` [PATCH 0/3] ARM: OMAP: add corrected DSS regulator supplies Tomi Valkeinen
2013-06-12 10:38   ` Tomi Valkeinen
2013-06-12 14:05   ` Tony Lindgren [this message]
2013-06-12 14:05     ` 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=20130612140520.GT8164@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.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.