[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <168679586333.2051714.1943947298850230853.b4-ty@kernel.dk>
Date: Wed, 14 Jun 2023 20:24:23 -0600
From: Jens Axboe <axboe@...nel.dk>
To: hch@....de, dgilbert@...erlog.com, jejb@...ux.ibm.com,
martin.petersen@...cle.com, Yu Kuai <yukuai1@...weicloud.com>
Cc: linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-scsi@...r.kernel.org, yukuai3@...wei.com,
yi.zhang@...wei.com, yangerkun@...wei.com
Subject: Re: [PATCH v5 0/3] fix blktrace debugfs entries leakage
On Sat, 10 Jun 2023 10:20:00 +0800, Yu Kuai wrote:
> Changes in v5:
> - blk_trace_shutdown() can't be used for module, add a new patch to use
> inline function for blk_trace_remove() to fix build warning from v3.
> - add review tag for patch 2,3 that is the same from v3.
>
> Changes in v4:
> - blk_trace_remove() will trigger build warning if blktrace config is
> not enabled, use blk_trace_shutdown() instead.
>
> [...]
Applied, thanks!
[1/3] blktrace: use inline function for blk_trace_remove() while blktrace is disabled
commit: cbe7cff4a76bc749dd70264ca5cf924e2adf9296
[2/3] scsi: sg: fix blktrace debugfs entries leakage
commit: db59133e927916d8a25ee1fd8264f2808040909d
[3/3] block: fix blktrace debugfs entries leakage
commit: dd7de3704af9989b780693d51eaea49a665bd9c2
Best regards,
--
Jens Axboe
Powered by blists - more mailing lists