[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4aa1f6ae3ac72a5eb3303740242d53d46a338d6b.camel@sipsolutions.net>
Date: Mon, 25 Mar 2024 17:48:09 +0100
From: Johannes Berg <johannes@...solutions.net>
To: José Roberto de Souza <jose.souza@...el.com>,
linux-kernel@...r.kernel.org, intel-xe@...ts.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@...el.com>, Mukesh Ojha
<quic_mojha@...cinc.com>, Jonathan Cavitt <jonathan.cavitt@...el.com>
Subject: Re: [PATCH v3 1/4] devcoredump: Add dev_coredump_put()
On Mon, 2024-03-04 at 06:39 -0800, José Roberto de Souza wrote:
> It is useful for modules that do not want to keep coredump available
> after its unload.
Why not though? Maybe if this is a common case we should have devm_...
coredump functions? Dunno.
Anyway, I'm fine with this, even though I'd like to see a bit more
discussion than "do not want". Code looks good.
Reviewed-by: Johannes Berg <johannes@...solutions.net>
johannes
Powered by blists - more mailing lists