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>,
linux-block <linux-block@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>
Subject: Re: [EXT] Re: [PATCH v5 1/2] mmc: Support kmsg dumper based on pstore/blk
Date: Tue, 8 Jun 2021 18:14:22 +0200 [thread overview]
Message-ID: <20210608161422.GA10298@lst.de> (raw)
In-Reply-To: <CAPDyKFrVQbALjSeFBckaZQgkgwcBVuwHy563pdBxHQNA7bxRnQ@mail.gmail.com>
Given that Kees was unwilling to take the series to unbreak the pstore
block support I've sent a patch to Jens to mark it broken and thus
effectively disable it. We can't really let this spread any further.
next prev parent reply other threads:[~2021-06-08 16:14 UTC|newest]
Thread overview: 14+ 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
2021-06-08 16:14 ` Christoph Hellwig [this message]
2021-06-08 17:33 ` Kees Cook
2021-01-20 16:11 ` kernel test robot
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=20210608161422.GA10298@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=bbudiredla@marvell.com \
--cc=ccross@android.com \
--cc=keescook@chromium.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.