[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190808.183756.2198405327467483431.davem@davemloft.net>
Date: Thu, 08 Aug 2019 18:37:56 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: gregkh@...uxfoundation.org
Cc: netdev@...r.kernel.org
Subject: Re: [PATCH 00/17] Networking driver debugfs cleanups
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Date: Tue, 6 Aug 2019 18:11:11 +0200
> There is no need to test the result of any debugfs call anymore. The
> debugfs core warns the user if something fails, and the return value of
> a debugfs call can always be fed back into another debugfs call with no
> problems.
>
> Also, debugfs is for debugging, so if there are problems with debugfs
> (i.e. the system is out of memory) the rest of the kernel should not
> change behavior, so testing for debugfs calls is pointless and not the
> goal of debugfs at all.
>
> This series cleans up a lot of networking drivers and some wimax code
> that was calling debugfs and trying to do something with the return
> value that it didn't need to. Removing this logic makes the code
> smaller, easier to understand, and use less run-time memory in some
> cases, all good things.
>
> The series is against net-next, and have no dependancies between any of
> them if they want to go through any random tree/order. Or, if wanted,
> I can take them through my driver-core tree where other debugfs cleanups
> are being slowly fed during major merge windows.
I applied this without patch #17 which you said you would respin in order
to get rid of the now unused local variable.
Thanks.
Powered by blists - more mailing lists