From: Christoph Hellwig <hch@lst.de>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Bhaskara Budiredla <bbudiredla@marvell.com>,
Kees Cook <keescook@chromium.org>,
Colin Cross <ccross@android.com>, Tony Luck <tony.luck@intel.com>,
Sunil Kovvuri Goutham <sgoutham@marvell.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [EXT] Re: [PATCH v1 1/2] mmc: Support kmsg dumper based on pstore/blk
Date: Tue, 24 Nov 2020 17:18:51 +0100 [thread overview]
Message-ID: <20201124161851.GA10535@lst.de> (raw)
In-Reply-To: <CAPDyKFqZomrJDgjKWvxeOornENnZFXSX+NWTWEerNHf=zf1L8g@mail.gmail.com>
On Tue, Nov 24, 2020 at 03:40:21PM +0100, Ulf Hansson wrote:
> It looks like Christoph is planning for some rewrite of the pstore
> code, so let's see what that means in regards to this.
Here is what I posted last month:
http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/pstore
Kees wanted to chime in with a few thing he'd like to see done
differently, but I've not seen the actual comments yet.
In respect to the eMMC support what I've done should mostly
just work, it would have to adopt to the slightly different
registration interface and just call register_pstore_device() with
its own ops.
next prev parent reply other threads:[~2020-11-24 16:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 6:24 [PATCH v1 0/2] mmc: support crash logging to MMC block devices Bhaskara Budiredla
2020-11-12 6:24 ` [PATCH v1 1/2] mmc: Support kmsg dumper based on pstore/blk Bhaskara Budiredla
2020-11-13 13:58 ` kernel test robot
2020-11-20 13:20 ` Ulf Hansson
2020-11-23 5:41 ` [EXT] " Bhaskara Budiredla
2020-11-23 12:18 ` Ulf Hansson
2020-11-24 4:09 ` Bhaskara Budiredla
2020-11-24 14:40 ` Ulf Hansson
2020-11-24 16:18 ` Christoph Hellwig [this message]
2020-11-26 5:00 ` Bhaskara Budiredla
2020-11-12 6:24 ` [PATCH v1 2/2] mmc:cavium: Add MMC polling method to support kmsg panic/oops write Bhaskara Budiredla
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=20201124161851.GA10535@lst.de \
--to=hch@lst.de \
--cc=bbudiredla@marvell.com \
--cc=ccross@android.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=sgoutham@marvell.com \
--cc=tony.luck@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).