All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Linus Walleij <linus.walleij@stericsson.com>
Cc: Ohad Ben-Cohen <ohad@wizery.com>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	Ghorai Sukumar <s-ghorai@ti.com>,
	Nicolas Pitre <nico@fluxnic.net>,
	Adrian Hunter <adrian.hunter@nokia.com>,
	David Vrabel <david.vrabel@csr.com>,
	Kyungmin Park <kmpark@infradead.org>,
	"jh80.chung@samsung.com" <jh80.chung@samsung.com>
Subject: Re: [PATCH 1/2] mmc: agressive clocking framework v8
Date: Wed, 10 Nov 2010 16:34:48 +0000	[thread overview]
Message-ID: <20101110163448.GA27440@void.printf.net> (raw)
In-Reply-To: <4CDAC787.3040005@stericsson.com>

Hi Linus,

On Wed, Nov 10, 2010 at 05:25:43PM +0100, Linus Walleij wrote:
> Chris, do you want an incremental patch or shall I spin an all-new
> v10 patch?

I think incremental patches make sense from here on out, now that it's
in -next.  We can decide whether it's worth performing any rebasing
once the patch is looking complete, before it goes into mainline. 

Thanks!

-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

  reply	other threads:[~2010-11-10 16:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-03  9:22 [PATCH 1/2] mmc: agressive clocking framework v8 Linus Walleij
2010-11-08  9:26 ` Linus Walleij
2010-11-08 22:30   ` Linus Walleij
2010-11-09  3:59     ` Chris Ball
2010-11-09 10:18       ` Linus Walleij
2010-11-22 23:27       ` Chris Ball
2010-11-24 13:15         ` Linus Walleij
2010-11-24 13:38           ` Chris Ball
2010-11-10  9:05 ` Ohad Ben-Cohen
2010-11-10 16:25   ` Linus Walleij
2010-11-10 16:34     ` Chris Ball [this message]
2010-11-10 19:22     ` Ohad Ben-Cohen
2010-12-21 20:24 ` Chris Ball
2010-12-22  8:12   ` Linus Walleij
2010-12-22  8:24     ` David Vrabel
2010-12-22  8:50       ` Linus Walleij
2010-12-23  0:09         ` Chris Ball

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=20101110163448.GA27440@void.printf.net \
    --to=cjb@laptop.org \
    --cc=adrian.hunter@nokia.com \
    --cc=david.vrabel@csr.com \
    --cc=jh80.chung@samsung.com \
    --cc=kmpark@infradead.org \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=nico@fluxnic.net \
    --cc=ohad@wizery.com \
    --cc=s-ghorai@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.