[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4a58caee3b6b8975f4ff632bf6d2a6673788157d.camel@sipsolutions.net>
Date: Fri, 09 Oct 2020 12:21:54 +0200
From: Johannes Berg <johannes@...solutions.net>
To: Taehee Yoo <ap420073@...il.com>
Cc: Nicolai Stange <nstange@...e.de>,
David Laight <David.Laight@...lab.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"kuba@...nel.org" <kuba@...nel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
"wil6210@....qualcomm.com" <wil6210@....qualcomm.com>,
"brcm80211-dev-list@...ress.com" <brcm80211-dev-list@...ress.com>,
"b43-dev@...ts.infradead.org" <b43-dev@...ts.infradead.org>,
"linux-bluetooth@...r.kernel.org" <linux-bluetooth@...r.kernel.org>
Subject: Re: [PATCH net 000/117] net: avoid to remove module when its
debugfs is being used
On Fri, 2020-10-09 at 19:15 +0900, Taehee Yoo wrote:
>
> Okay, as you mentioned earlier in 001/117 patch thread,
> I will squash patches into per-driver/subsystem then send them as v2.
Give me a bit. I think I figured out a less intrusive way that at least
means we don't have to do it if the fops doesn't have ->release(), which
is the vast majority.
johannes
Powered by blists - more mailing lists