From: Kees Cook <keescook@chromium.org>
To: Bhaskara Budiredla <bbudiredla@marvell.com>,
Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>
Cc: Ulf Hansson <ulf.hansson@linaro.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>,
linux-block <linux-block@vger.kernel.org>
Subject: Re: [EXT] Re: [PATCH v5 1/2] mmc: Support kmsg dumper based on pstore/blk
Date: Tue, 8 Jun 2021 10:31:58 -0700 [thread overview]
Message-ID: <202106081024.09E42DA400@keescook> (raw)
In-Reply-To: <CY4PR1801MB2070B09D27404F8B7A84D446DE389@CY4PR1801MB2070.namprd18.prod.outlook.com>
On Mon, Jun 07, 2021 at 12:37:07PM +0000, Bhaskara Budiredla wrote:
> [...]
> >What patches are you referring to?
>
> I was referring to this patch.
> http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/pstore
I applied the first three:
https://lore.kernel.org/lkml/160685706687.2724892.9289969466453217944.b4-ty@chromium.org/
and explained my aversion to the others. Christoph never replied to my
notes on patch 8/9:
https://lore.kernel.org/lkml/202012011149.5650B9796@keescook/
-Kees
--
Kees Cook
next prev parent reply other threads:[~2021-06-08 17:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 12:10 [PATCH v5 0/2] mmc: support crash logging to MMC block devices Bhaskara Budiredla
2021-01-20 12:10 ` [PATCH v5 1/2] mmc: Support kmsg dumper based on pstore/blk Bhaskara Budiredla
2021-01-20 15:06 ` Ulf Hansson
2021-06-05 10:31 ` [EXT] " Bhaskara Budiredla
2021-06-07 11:17 ` Ulf Hansson
2021-06-07 12:37 ` Bhaskara Budiredla
2021-06-07 14:07 ` Ulf Hansson
2021-06-07 16:28 ` Bhaskara Budiredla
2021-06-08 17:31 ` Kees Cook [this message]
2021-06-08 16:14 ` Christoph Hellwig
2021-06-08 17:33 ` Kees Cook
2021-01-20 16:11 ` kernel test robot
2021-01-20 12:10 ` [PATCH v5 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=202106081024.09E42DA400@keescook \
--to=keescook@chromium.org \
--cc=axboe@kernel.dk \
--cc=bbudiredla@marvell.com \
--cc=ccross@android.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.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).