All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Madhusudhan <madhu.cr@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: MMC related patches
Date: Wed, 11 Nov 2009 18:29:31 -0800	[thread overview]
Message-ID: <20091112022931.GV24837@atomide.com> (raw)
In-Reply-To: <00b401ca632b$8c84d6e0$544ff780@am.dhcp.ti.com>

* Madhusudhan <madhu.cr@ti.com> [091111 16:02]:
> Hi Tony,
> 
> Just a ping on the below patches. I did not see any comments on them. Are
> you planning to push them?
> 
> Regards,
> Madhu
> 
> http://marc.info/?l=linux-omap&m=125668573422479&w=2
> http://marc.info/?l=linux-omap&m=125624185318767&w=2

OK, adding.

> http://marc.info/?l=linux-omap&m=125623349405262&w=2

This needs to be refreshed against board-zoom-peripherals.c now
in omap for-next. But if it depends on 3630 mux patch,
let's wait on that until we have the new mux framework.

> http://marc.info/?l=linux-omap&m=125623339105103&w=2
> http://marc.info/?l=linux-omap&m=125623327504912&w=2

Adding.

Also, this needs to be refreshed:

http://patchwork.kernel.org/patch/45196/

Thanks for summarizing the patches, that always helps.
Maybe use patchwork.kernel.org links the next time,
as I can directly apply from those?

Or even better, just set a git branch against some static
commit :) (Not against for-next as that's still changing)

BTW, some of these patches I had to unwrap manually again..

Regards,

Tony

  reply	other threads:[~2009-11-12  2:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-12  0:03 MMC related patches Madhusudhan
2009-11-12  2:29 ` Tony Lindgren [this message]
2009-11-12 22:21   ` Madhusudhan
2009-11-12 22:53     ` 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=20091112022931.GV24837@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=madhu.cr@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.