All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: adrian.hunter@nokia.com
Cc: madhu.cr@ti.com, paul@pwsan.com, linux-omap@vger.kernel.org,
	linux-mmc@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH V2 0/10] omap_hsmmc changes V2
Date: Fri, 22 Jan 2010 09:14:27 -0800	[thread overview]
Message-ID: <20100122171427.GQ23467@atomide.com> (raw)
In-Reply-To: <1264149200.1920.11.camel@Nokia-N900-51-1>

* adrian.hunter@nokia.com <adrian.hunter@nokia.com> [100122 00:31]:
> Madhu wrote
> >
> >
> > > -----Original Message-----
> > > From: Adrian Hunter [mailto:adrian.hunter@nokia.com]
> > > Sent: Saturday, January 16, 2010 7:33 PM
> > > To: Tony Lindgren
> > > Cc: Adrian Hunter; Madhusudhan Chikkature; Paul Walmsley; linux-omap
> > > Mailing List; linux-mmc Mailing List; Andrew Morton
> > > Subject: [PATCH V2 0/10] omap_hsmmc changes V2
> > >
> > > Hi
> > >
> > > Here are some changes we need for omap_hsmmc.  They are dependent on
> > OMAP
> > > board files so it would be simplest if the patches all went via the
> > OMAP
> > > tree.
> > >
> > > This is version 2 of this patch set.  Thank you Tony, Paul and Madhu
> > for
> > > your comments.
> > >
> > > Changes from version 1:
> > >              - amended patch 'omap_hsmmc: Move gpio and regulator control
> > from
> > >              board file' so that system control functions remain in the
> > board
> > >              file
> > >              - for clarity, split patch 'omap: Rename mmc-twl4030 to hsmmc'
> > into
> > >              'omap: Rename mmc-twl4030 files to hsmmc' and
> > >              'omap: Rename hsmmc symbols to reflect independence from
> > twl4030'
> > >              - removed patch 'omap_hsmmc: set DVFS/PM constraints'
> > >              - added patch 'omap: Add functions for dynamic remuxing of
> > pins'
> > >              - renamed and reworked patch 'omap: RX51: Remux to pull eMMC
> > lines
> > >              down when powering off' (was 'omap_hsmmc: RX51: set padconfs to
> > pull
> > >              down when powering off eMMC')
> > >              - added patch 'omap_hsmmc: Ensure regulator enable / disable
> > are
> > >              paired'
> > >              - fixed mistakes in patch 'omap_hsmmc: Allow for a shared VccQ'
> > >
> > Reviewed the omap_hsmmc changes and did a sanity test on Zoom2.
> > Acked-by: Madhusudhan Chikkature <madhu.cr@ti.com<mailto:madhu.cr@ti.com>>
> >
> > Regards,
> > Madhu
> 
> Thanks Madhu. Tony, are you ok taking these patches into your tree?

Looks good to me, will queue them into omap for-next.

Regards,

Tony

       reply	other threads:[~2010-01-22 17:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1264149200.1920.11.camel@Nokia-N900-51-1>
2010-01-22 17:14 ` Tony Lindgren [this message]
2010-02-02  3:12   ` [PATCH V2 0/10] omap_hsmmc changes V2 Tony Lindgren
2010-02-02  9:22     ` Adrian Hunter
2010-02-03  2:17       ` Tony Lindgren
2010-01-17  1:32 Adrian Hunter
2010-01-21 17:29 ` Madhusudhan
2010-01-22  8:41   ` Adrian Hunter
  -- strict thread matches above, loose matches on Subject: below --
2010-01-17  1:28 Adrian Hunter

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=20100122171427.GQ23467@atomide.com \
    --to=tony@atomide.com \
    --cc=adrian.hunter@nokia.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=madhu.cr@ti.com \
    --cc=paul@pwsan.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.