From: Arnd Bergmann <arnd@arndb.de>
To: Jaehoon Chung <jh80.chung@samsung.com>
Cc: linux-mmc <linux-mmc@vger.kernel.org>,
Chris Ball <chris@printf.net>,
Ulf Hansson <ulf.hansson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [RFC PATCH] mmc: mmc_oops: support mmc_oops feature
Date: Fri, 27 Feb 2015 12:36:34 +0100 [thread overview]
Message-ID: <3372849.Dqaz8KMKAB@wuerfel> (raw)
In-Reply-To: <54F03C05.7040009@samsung.com>
On Friday 27 February 2015 18:42:29 Jaehoon Chung wrote:
> Dear, Arnd.
>
> On 02/27/2015 05:31 PM, Arnd Bergmann wrote:
> > On Friday 27 February 2015 14:33:39 Jaehoon Chung wrote:
> >> --- a/drivers/mmc/card/Kconfig
> >> +++ b/drivers/mmc/card/Kconfig
> >> @@ -68,3 +68,11 @@ config MMC_TEST
> >>
> >> This driver is only of interest to those developing or
> >> testing a host driver. Most people should say N here.
> >> +
> >> +config MMC_OOPS
> >> + tristate "Log panic/oops to a MMC buffer"
> >> + depends on OF
> >> + help
> >> + This enables panic and oops messages to be logged to a circular
> >> + buffer in a MMC sectors where it can be read back at some
> >> + later point.
> >>
> >
> > This sounds a lot like the implementation should be using
> > the fs/pstore infrastructure like we do for ramoops, chromeos
> > and the EFI runtime services logger.
>
> I refer to it, so you can sound so. It's my wrong.
> I will rewrite the comment for MMC_OOPS config.
> Thanks for point out.
I don't exactly understand what you mean here, but I meant rewriting
the patch, not just the comment.
Arnd
prev parent reply other threads:[~2015-02-27 11:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 5:33 [RFC PATCH] mmc: mmc_oops: support mmc_oops feature Jaehoon Chung
2015-02-27 8:31 ` Arnd Bergmann
2015-02-27 9:42 ` Jaehoon Chung
2015-02-27 11:36 ` Arnd Bergmann [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=3372849.Dqaz8KMKAB@wuerfel \
--to=arnd@arndb.de \
--cc=chris@printf.net \
--cc=jh80.chung@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-mmc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=ulf.hansson@linaro.org \
/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