[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <22f324ce-552a-4f6a-b4e5-2d84a00010aa@web.de>
Date: Sun, 14 Apr 2024 11:16:34 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Li Nan <linan122@...wei.com>, linux-mtd@...ts.infradead.org,
kernel-janitors@...r.kernel.org, Miquel Raynal <miquel.raynal@...tlin.com>,
Richard Weinberger <richard@....at>, Vignesh Raghavendra <vigneshr@...com>,
Zhihao Cheng <chengzhihao1@...wei.com>
Cc: LKML <linux-kernel@...r.kernel.org>, Hou Tao <houtao1@...wei.com>,
Yang Erkun <yangerkun@...wei.com>, Yu Kuai <yukuai3@...wei.com>,
Zhang Yi <yi.zhang@...wei.com>
Subject: Re: [PATCH v2] ubi: block: fix memleak in ubiblock_create()
Can it be nicer to use the term “memory leak” instead of “memleak”
in the patch subject?
…
> 'gd' will not be put anymore. Fix it by putting 'gd' directly.
Would the following wording variant be more desirable?
… anymore.
Thus pass the variable “gd” to a put_disk() call directly.
Would you like to add the tag “Fixes” accordingly?
Regards,
Markus
Powered by blists - more mailing lists