public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Adrian Hunter <ext-adrian.hunter@nokia.com>
Cc: "linux-omap@vger.kernel.org Mailing List"
	<linux-omap@vger.kernel.org>,
	"Lavinen Jarkko (Nokia-M/Helsinki)" <jarkko.lavinen@nokia.com>
Subject: Re: [PATCH 1/9] OMAP: HSMMC: Make driver support dynamic idle
Date: Tue, 9 Dec 2008 12:02:13 -0800	[thread overview]
Message-ID: <20081209200212.GT4593@atomide.com> (raw)
In-Reply-To: <492E5DBD.8030605@nokia.com>

* Adrian Hunter <ext-adrian.hunter@nokia.com> [081127 00:34]:
> Tony Lindgren wrote:
>> * Adrian Hunter <ext-adrian.hunter@nokia.com> [081121 01:15]:
>>> Add a timer that is kept active by MMC requests. FCLK is disabled on timeout
>>
>> Let's keep these patches on hold until we have the hsmmc.c driver in
>> mainline, then get them integrated via LKML.
>>
>> Meanwhile, maybe you want to set up a git branch for hsmmc to queue these?
>> And then I could mirror your hsmmc branch.
>
> As you wish.
>
> tree is:
>
> git://git.infradead.org/users/ahunter/omap_hsmmc.git
>
> branch is:
>
> omap_hsmmc

Thanks, I'm now mirroring that branch in my git tree, and I've merged
it to linux-omap tree.

Please rebase your omap_hsmmc branch against the mainline tree once
we have the current mmc patches in my hsmmc branch integrated to
mainline. That way the omap_hsmmc queue will be ready for next merge
window.

Regards,

Tony

  reply	other threads:[~2008-12-09 20:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-21  9:24 [PATCH 1/9] OMAP: HSMMC: Make driver support dynamic idle Adrian Hunter
2008-11-26 19:11 ` Tony Lindgren
2008-11-27  8:43   ` Adrian Hunter
2008-12-09 20:02     ` Tony Lindgren [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-11-21  9:23 [PATCH 0/9] OMAP: HSMMC: Patches Adrian Hunter
2008-11-21  9:37 ` Adrian Hunter
2008-11-21  9:43   ` [PATCH 1/9] OMAP: HSMMC: Make driver support dynamic idle 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=20081209200212.GT4593@atomide.com \
    --to=tony@atomide.com \
    --cc=ext-adrian.hunter@nokia.com \
    --cc=jarkko.lavinen@nokia.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox