[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CY4PR1801MB2070D4B45E08B05F05D195E9DEF90@CY4PR1801MB2070.namprd18.prod.outlook.com>
Date: Thu, 26 Nov 2020 05:00:12 +0000
From: Bhaskara Budiredla <bbudiredla@...vell.com>
To: Christoph Hellwig <hch@....de>,
Ulf Hansson <ulf.hansson@...aro.org>
CC: Kees Cook <keescook@...omium.org>,
Colin Cross <ccross@...roid.com>,
"Tony Luck" <tony.luck@...el.com>,
Sunil Kovvuri Goutham <sgoutham@...vell.com>,
"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: RE: [EXT] Re: [PATCH v1 1/2] mmc: Support kmsg dumper based on
pstore/blk
Sure, I will tune to those discussions and would wait for that.
- Bhaskara
>-----Original Message-----
>From: Christoph Hellwig <hch@....de>
>Sent: Tuesday, November 24, 2020 9:49 PM
>To: Ulf Hansson <ulf.hansson@...aro.org>
>Cc: Bhaskara Budiredla <bbudiredla@...vell.com>; Kees Cook
><keescook@...omium.org>; Colin Cross <ccross@...roid.com>; Tony Luck
><tony.luck@...el.com>; Sunil Kovvuri Goutham <sgoutham@...vell.com>;
>linux-mmc@...r.kernel.org; Linux Kernel Mailing List <linux-
>kernel@...r.kernel.org>; Christoph Hellwig <hch@....de>
>Subject: Re: [EXT] Re: [PATCH v1 1/2] mmc: Support kmsg dumper based on
>pstore/blk
>
>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:
>
>https://urldefense.proofpoint.com/v2/url?u=http-
>3A__git.infradead.org_users_hch_misc.git_shortlog_refs_heads_pstore&d=
>DwIBAg&c=nKjWec2b6R0mOyPaz7xtfQ&r=9P_lSljSO7KnQNkCGsgu9x_Op4ms
>tSdqWN3Olr4bUv0&m=q8IjbcWL5TERE5I_titSsMtZA2l6QrRmBgu0lc8wpko&s=
>T6P9lsMAsulOHqb4szJ553K0z2eYB5Tliq7UqFMth-g&e=
>
>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.
Powered by blists - more mailing lists