Re: [PATCH 2/7] crypto: ccrree: no need to check return value of debugfs_create functions

2019-01-23 Thread Gilad Ben-Yossef
On Wed, Jan 23, 2019 at 3:37 PM Greg Kroah-Hartman wrote: > > On Wed, Jan 23, 2019 at 02:58:22PM +0200, Gilad Ben-Yossef wrote: > > Hi, > > > > On Tue, Jan 22, 2019 at 5:14 PM Greg Kroah-Hartman > > wrote: > > > > > > When calling debugfs functions, there is no need to ever check the > > >

Re: [PATCH 2/7] crypto: ccrree: no need to check return value of debugfs_create functions

2019-01-23 Thread Greg Kroah-Hartman
On Wed, Jan 23, 2019 at 02:58:22PM +0200, Gilad Ben-Yossef wrote: > Hi, > > On Tue, Jan 22, 2019 at 5:14 PM Greg Kroah-Hartman > wrote: > > > > When calling debugfs functions, there is no need to ever check the > > return value. The function can work or not, but the code logic should > > never

Re: [PATCH 2/7] crypto: ccrree: no need to check return value of debugfs_create functions

2019-01-23 Thread Gilad Ben-Yossef
Hi, On Tue, Jan 22, 2019 at 5:14 PM Greg Kroah-Hartman wrote: > > When calling debugfs functions, there is no need to ever check the > return value. The function can work or not, but the code logic should > never do something different based on this. I get the part about not failing loading

[PATCH 2/7] crypto: ccrree: no need to check return value of debugfs_create functions

2019-01-22 Thread Greg Kroah-Hartman
When calling debugfs functions, there is no need to ever check the return value. The function can work or not, but the code logic should never do something different based on this. Cc: Yael Chemla Cc: Gilad Ben-Yossef Cc: Herbert Xu Cc: "David S. Miller" Cc: linux-cry...@vger.kernel.org