All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: "S, Venkatraman" <svenkatr@ti.com>
Cc: Saugata Das <saugata.das@stericsson.com>, linux-mmc@vger.kernel.org
Subject: Re: [PATCH] MMC-4.5 Data Tag Support
Date: Thu, 12 Jan 2012 14:18:24 -0500	[thread overview]
Message-ID: <m2ehv4bugv.fsf@bob.laptop.org> (raw)
In-Reply-To: <CANfBPZ9gDkHK01bsMjf_CpkA-8s1U3X4WnAxO_=q9XdGODuf7w@mail.gmail.com> (Venkatraman S.'s message of "Thu, 12 Jan 2012 19:58:29 +0530")

Hi,

On Thu, Jan 12 2012, S, Venkatraman wrote:
> On Wed, Dec 21, 2011 at 1:09 PM, Saugata Das <saugata.das@stericsson.com> wrote:
>> From: Saugata Das <saugata.das@linaro.org>
>>
>> MMC-4.5 data tag feature will be used to store the file system
>> meta-data in the
>> tagged region of eMMC. This will improve the write and subsequent
>> read transfer
>> time for the meta data.
>>
>> Signed-off-by: Saugata Das <saugata.das@linaro.org>
>
> I tested this on a device which supports a data tag unit size of 8K.
> Tested-by: Venkatraman S <svenkatr@ti.com>

Thanks for testing!  I've pushed it to mmc-next.

> Chris,
>   Can this go into 3.3 ?

I think 3.4 would be better after a full round of linux-next testing,
since this sounds like it could expose card-dependent quirks that could
destroy filesystems.  Better to be safe.

Thanks,

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

  reply	other threads:[~2012-01-12 19:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-21  7:39 [PATCH] MMC-4.5 Data Tag Support Saugata Das
2011-12-21 10:04 ` S, Venkatraman
2011-12-21 10:53 ` Girish K S
2011-12-21 11:12   ` Saugata Das
2011-12-21 11:31     ` Girish K S
2011-12-21 11:58       ` Saugata Das
2012-01-12 14:28 ` S, Venkatraman
2012-01-12 19:18   ` Chris Ball [this message]
2012-01-13 10:10     ` Kyungmin Park
2012-01-16 10:37       ` S, Venkatraman
2012-01-16 13:09         ` Kyungmin Park
2012-01-17 13:40           ` S, Venkatraman
2012-01-18 13:15             ` Kyungmin Park
2012-01-18 14:50               ` Saugata Das

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=m2ehv4bugv.fsf@bob.laptop.org \
    --to=cjb@laptop.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=saugata.das@stericsson.com \
    --cc=svenkatr@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.