Hi Greg, > 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. > > Because we don't care if debugfs works or not, this trickles back a bit > so we can clean things up by making some functions return void instead > of an error value that is never going to fail. > > Cc: Alexander Aring <alex.ar...@gmail.com> > Cc: Jukka Rissanen <jukka.rissa...@linux.intel.com> > Cc: "David S. Miller" <da...@davemloft.net> > Cc: linux-blueto...@vger.kernel.org > Cc: linux-w...@vger.kernel.org > Cc: netdev@vger.kernel.org > Signed-off-by: Greg Kroah-Hartman <gre...@linuxfoundation.org> > --- > net/6lowpan/6lowpan_i.h | 16 ++----- > net/6lowpan/core.c | 8 +--- > net/6lowpan/debugfs.c | 97 +++++++++++------------------------------ > 3 files changed, 32 insertions(+), 89 deletions(-)
patch has been applied to bluetooth-next tree. Regards Marcel
