Re: [PATCH v2 09/23] staging: iio: tsl2583: cleaned up logging

2016-11-08 Thread Brian Masney
On Tue, Nov 08, 2016 at 02:29:20AM -0800, Joe Perches wrote: > On Tue, 2016-11-08 at 05:16 -0500, Brian Masney wrote: > > There are several places in the code where the function name is > > hardcoded in the log message. Use the __func__ constant string to build > > the log message. This also clarif

Re: [PATCH v2 09/23] staging: iio: tsl2583: cleaned up logging

2016-11-08 Thread Joe Perches
On Tue, 2016-11-08 at 05:16 -0500, Brian Masney wrote: > There are several places in the code where the function name is > hardcoded in the log message. Use the __func__ constant string to build > the log message. This also clarifies some of the error messages to match > the code and ensures that t

[PATCH v2 09/23] staging: iio: tsl2583: cleaned up logging

2016-11-08 Thread Brian Masney
There are several places in the code where the function name is hardcoded in the log message. Use the __func__ constant string to build the log message. This also clarifies some of the error messages to match the code and ensures that the correct priority is used since the message is already being