public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: "S, Venkatraman" <svenkatr@ti.com>
Cc: Namjae Jeon <linkinjeon@gmail.com>,
	linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
	awarkentin@vmware.com, adrian.hunter@intel.com,
	linus.walleij@linaro.org, james_p_freyensee@linux.intel.com,
	sebras@gmail.com, Ulf.Hansson@stericsson.com,
	stefan.xk.nilsson@stericsson.com, per.forlin@stericsson.com,
	johan.rudholm@stericsson.com
Subject: Re: [PATCH v10] mmc : general purpose partition support.
Date: Tue, 04 Oct 2011 14:25:46 -0400	[thread overview]
Message-ID: <m2y5x0k40l.fsf@bob.laptop.org> (raw)
In-Reply-To: <CANfBPZ_aet5iF2zQ6zaqX0cjVB4LUnq6wLcHh2t_WNst3zXKAA@mail.gmail.com> (Venkatraman S.'s message of "Tue, 4 Oct 2011 23:49:13 +0530")

Hi,

On Tue, Oct 04 2011, S, Venkatraman wrote:
> Stupid question - This will affect all MMC instances, right ? Doesn't
> this constitute a ABI breakage for user space scripts ?

As I understand it, these partitions were simply not accessible before
this patch:  we're not renaming mmcblkNpY to anything else, we're adding
support for mmcblkNgpY partitions, which are part of the "MMC General
Purpose Partition" spec, and are partitioned separately and not
currently available to userspace.

So, I don't see what would constitute breakage.  Does that clear it up?

Thanks,

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

  reply	other threads:[~2011-10-04 18:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-04 17:45 [PATCH v10] mmc : general purpose partition support Namjae Jeon
2011-10-04 18:19 ` S, Venkatraman
2011-10-04 18:25   ` Chris Ball [this message]
2011-10-04 18:27     ` S, Venkatraman
2011-10-04 20:20 ` Andrei Warkentin
2011-10-05  9:12 ` Adrian Hunter
2011-10-05 10:21   ` NamJae Jeon
2011-10-05 10:53     ` Adrian Hunter
2011-10-05 11:21       ` NamJae Jeon
2011-10-05 11:22         ` NamJae Jeon
2011-10-05 11:37           ` Adrian Hunter
2011-10-05 11:49             ` NamJae Jeon

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=m2y5x0k40l.fsf@bob.laptop.org \
    --to=cjb@laptop.org \
    --cc=Ulf.Hansson@stericsson.com \
    --cc=adrian.hunter@intel.com \
    --cc=awarkentin@vmware.com \
    --cc=james_p_freyensee@linux.intel.com \
    --cc=johan.rudholm@stericsson.com \
    --cc=linkinjeon@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=per.forlin@stericsson.com \
    --cc=sebras@gmail.com \
    --cc=stefan.xk.nilsson@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox