public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Girish K S <girish.shivananjappa@linaro.org>
Cc: Aaron Lu <aaron.lu@amd.com>, Philip Rakity <prakity@marvell.com>,
	linux-mmc@vger.kernel.org, Aaron Lu <aaron.lwe@gmail.com>
Subject: Re: [PATCH 2/2] mmc: sd: Fix sd current limit setting
Date: Thu, 19 Jul 2012 01:03:25 -0400	[thread overview]
Message-ID: <87txx49wbm.fsf@octavius.laptop.org> (raw)
In-Reply-To: <CAGxe1ZGoLWr-m6OAriOC4noXGz6SMBGMdMYrk1+wJQw7nwud3g@mail.gmail.com> (Girish K. S.'s message of "Thu, 19 Jul 2012 10:17:27 +0530")

Hi,

On Thu, Jul 19 2012, Girish K S wrote:
> Looks like a better solution than earlier one.
> Reviewed By: Girish K S <girish.shivananjappa@linaro.org>

Thanks.

> Chris,
> How about the holes created by removal of caps2 macros. Will they be
> adjusted to follow the sequence or left as it is for future use.

There actually isn't a hole in caps2, since yesterday I told Seungwon
and Maya that I think the packed-write patches are not ready for 3.6 and
probably should wait another cycle:

http://marc.info/?l=linux-mmc&m=134259666416161&w=2

I'll be removing them from mmc-next, unless something changes.
There aren't any other caps creating a hole in caps2.

There's a hole in caps1, though.  I think we'll just wait for the next
patches that want caps to take the place of the hole in caps1 without
renumbering any extant caps.  Let me know if you disagree.

Thanks,

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

      reply	other threads:[~2012-07-19  5:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-03  6:16 [PATCH 0/2] SD current limit setting fix Aaron Lu
2012-07-03  6:16 ` [PATCH 1/2] mmc: core: Simplify and fix for SD switch processing Aaron Lu
2012-07-04  0:48   ` Chris Ball
2012-07-03  6:16 ` [PATCH 2/2] mmc: sd: Fix sd current limit setting Aaron Lu
2012-07-03 14:18   ` Philip Rakity
2012-07-04  0:52   ` Chris Ball
2012-07-04  5:31     ` [PATCH v2 " Aaron Lu
2012-07-09  1:23       ` Philip Rakity
2012-07-10  2:57       ` Chris Ball
2012-07-17  9:34   ` [PATCH " Girish K S
2012-07-17 13:43     ` Aaron Lu
2012-07-17 15:43       ` Chris Ball
2012-07-18  5:09         ` Aaron Lu
2012-07-18  5:28           ` Chris Ball
2012-07-18  6:22             ` Aaron Lu
2012-07-19  2:41               ` Chris Ball
2012-07-19  3:47                 ` Philip Rakity
2012-07-19  6:25                 ` Chris Ball
2012-07-19  4:47               ` Girish K S
2012-07-19  5:03                 ` Chris Ball [this message]

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=87txx49wbm.fsf@octavius.laptop.org \
    --to=cjb@laptop.org \
    --cc=aaron.lu@amd.com \
    --cc=aaron.lwe@gmail.com \
    --cc=girish.shivananjappa@linaro.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=prakity@marvell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox