All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Saugata Das <saugata.das@linaro.org>
Cc: Jaehoon Chung <jh80.chung@samsung.com>,
	Saugata Das <saugata.das@stericsson.com>,
	linux-mmc@vger.kernel.org
Subject: Re: [RFC] MMC-4.5 Context ID
Date: Sat, 11 Feb 2012 15:57:13 -0500	[thread overview]
Message-ID: <m2vcndks0m.fsf@bob.laptop.org> (raw)
In-Reply-To: <CAKLKtzcAqJVDTZFYpijicWStr7m76Quv2ic8hRZp+X_Wmd-bFQ@mail.gmail.com> (Saugata Das's message of "Mon, 6 Feb 2012 11:04:10 +0530")

Hi,

On Mon, Feb 06 2012, Saugata Das wrote:
> Thanks for the info. Perhaps the initial MMC-4.5 device samples do not
> implement this command well. Yes, this feature is good to have in the
> kernel. I shall wait for some more comments on the proposed
> implementation before submitting the patch.

I'm not very excited about merging features that offer no concrete
benefit, because it just grows the kernel (and list of places where bugs
can occur) for no benefit.  So, it would be great if we could find a
device that actually implements these contexts in a way that provides
a performance benefit, to prove that adding the code is worthwhile.

Thanks,

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

  reply	other threads:[~2012-02-11 20:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01 15:27 [RFC] MMC-4.5 Context ID Saugata Das
2012-02-02 16:08 ` S, Venkatraman
2012-02-03  2:45   ` Jaehoon Chung
2012-02-03  5:48     ` Saugata Das
2012-02-03  5:47   ` Saugata Das
2012-02-05  2:45 ` Chris Ball
2012-02-06  5:13   ` Saugata Das
2012-02-06  5:26     ` Jaehoon Chung
2012-02-06  5:34       ` Saugata Das
2012-02-11 20:57         ` Chris Ball [this message]
2012-02-13 20:37           ` Saugata Das
2012-02-14  2:16             ` Jaehoon Chung

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=m2vcndks0m.fsf@bob.laptop.org \
    --to=cjb@laptop.org \
    --cc=jh80.chung@samsung.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=saugata.das@linaro.org \
    --cc=saugata.das@stericsson.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.