Re: [PATCH v2 5/5] iio: light: tcs3472: move standalone return to default case
Aldo Conte <[email protected]>
| Newsgroups | dev.linux.lists.linux-kernel-mentees,org.kernel.vger.linux-iio,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
On 5/13/26 13:23, Andy Shevchenko wrote: > On Wed, May 13, 2026 at 12:32:15AM +0200, Aldo Conte wrote: >> Move the trailing 'return -EINVAL' statements at the end of >> tcs3472_read_raw() and tcs3472_write_raw() into explicit default: >> cases inside the respective switch statements. >> >> This removes the need for a separate return statement after the switch. >> >> No functional change. > > Reviewed-by: Andy Shevchenko <[email protected]> > Hi Andy, Joshua, Thanks for the review. Before I send v3, I want to make sure I split the series the way you want. My plan is to split v2 into 7 patches: 1. sort headers (same as v2) 2. convert locking to guard(mutex) (drop Suggested-by, clean up trigger_handler) 3. replace == NULL with ! (add Suggested-by: Joshua Crofts) 4. use devm for resource management (drop Suggested-by, remove the dev_info change, add devm_mutex_init) 5. use 'dev' for dev_info() calls (new, taken out of patch 4) 6. implement wait time and sampling_frequency (drop Suggested-by, fix macro style, simplify cycle_us and all the other revisions) 7. move standalone return to default case (same as v2) Two things I am not sure about: - Should patch 3 ("replace == NULL with !") really be its own patch, or do you prefer it inside patch 4, since that line is right next to devm_iio_device_alloc? - Is patch 5 (dev_info refactor) in the right place after the devm patch? Aldo