[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5eac186c-918a-87d6-8cc7-85d4d24c4837@nvidia.com>
Date: Sat, 5 Feb 2022 09:12:29 +0000
From: Chaitanya Kulkarni <chaitanyak@...dia.com>
To: Yang Shi <shy828301@...il.com>
CC: "linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"xiyou.wangcong@...il.com" <xiyou.wangcong@...il.com>,
"rostedt@...dmis.org" <rostedt@...dmis.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"axboe@...nel.dk" <axboe@...nel.dk>,
"hch@...radead.org" <hch@...radead.org>
Subject: Re: [v6 PATCH] block: introduce block_rq_error tracepoint
>> since if I remember correctly we need to define a event class
>> instead of duplicating a tracepoint with similar reporting.
>
> Very good point. I did overlook it. The original post did have disk
> name and didn't have cmd, now the two tracepoints look much more
> similar than the original post, so I agree the duplicate could be
> combined into an event class.
>
I sent out a V7 with a prep patch and testlog keeping your
original authorship from this patch.
If you find anything wrong with that please send out V8 on the
top of V7.
>>
>> -ck
>>
>>
Powered by blists - more mailing lists