From: Simon Horman <horms@verge.net.au>
To: linux-mmc@vger.kernel.org
Cc: Jaehoon Chung <jh80.chung@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Chris Ball <cjb@laptop.org>, Philip Rakity <prakity@marvell.com>,
'Andrew Morton' <akpm@linux-foundation.org>,
Matt Fleming <matt@console-pimps.org>
Subject: mmcoops + mmcblk
Date: Tue, 12 Jul 2011 15:32:25 +0900 [thread overview]
Message-ID: <20110712063225.GA12742@verge.net.au> (raw)
Hi,
I am looking over the "[RFC] mmcoops with panic/oops" and is strikes
me that although platform data is used to limit the area of the MMC
device to which the oops is witten, the entire device has to belong
(be bound to) the mmc_oops driver and as such no part of the device
can be used for anything else.
I am wondering if I am missing something?
In particular, I would like to allow a single MMC chip to be
used both by mmcblk (as a filesystem) and as mmc_oops (a small
area reserved for writing oops messages).
next reply other threads:[~2011-07-12 6:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-12 6:32 Simon Horman [this message]
2011-07-14 4:28 ` mmcoops + mmcblk 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=20110712063225.GA12742@verge.net.au \
--to=horms@verge.net.au \
--cc=akpm@linux-foundation.org \
--cc=cjb@laptop.org \
--cc=jh80.chung@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-mmc@vger.kernel.org \
--cc=matt@console-pimps.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