Re: [PATCH v4 0/2] tty/nozomi: general module cleanup

2018-04-25 Thread Joey Pabalinas
On Wed, Apr 25, 2018 at 08:05:13AM +0200, Greg Kroah-Hartman wrote: > What changed between versions of this series? Ah no changes, I thought this was normal convention when doing a resend, but after looking through other LKML patches they just use a giant RESEND instead of bumping the version.

Re: [PATCH v4 0/2] tty/nozomi: general module cleanup

2018-04-25 Thread Joey Pabalinas
On Wed, Apr 25, 2018 at 08:05:13AM +0200, Greg Kroah-Hartman wrote: > What changed between versions of this series? Ah no changes, I thought this was normal convention when doing a resend, but after looking through other LKML patches they just use a giant RESEND instead of bumping the version.

Re: [PATCH v4 0/2] tty/nozomi: general module cleanup

2018-04-25 Thread Greg Kroah-Hartman
On Tue, Apr 24, 2018 at 07:48:02PM -1000, Joey Pabalinas wrote: > The nozomi module has a few sections which could use a bit of cleanup; > both style and clarity could be improved while maintaining equivalent > semantics. > > Cleanup messy portions of the module code while preserving existing >

Re: [PATCH v4 0/2] tty/nozomi: general module cleanup

2018-04-25 Thread Greg Kroah-Hartman
On Tue, Apr 24, 2018 at 07:48:02PM -1000, Joey Pabalinas wrote: > The nozomi module has a few sections which could use a bit of cleanup; > both style and clarity could be improved while maintaining equivalent > semantics. > > Cleanup messy portions of the module code while preserving existing >

[PATCH v4 0/2] tty/nozomi: general module cleanup

2018-04-24 Thread Joey Pabalinas
The nozomi module has a few sections which could use a bit of cleanup; both style and clarity could be improved while maintaining equivalent semantics. Cleanup messy portions of the module code while preserving existing behavior by: - Replacing constructs like `len__ > TMP_BUF_MAX ? TMP_BUF_MAX

[PATCH v4 0/2] tty/nozomi: general module cleanup

2018-04-24 Thread Joey Pabalinas
The nozomi module has a few sections which could use a bit of cleanup; both style and clarity could be improved while maintaining equivalent semantics. Cleanup messy portions of the module code while preserving existing behavior by: - Replacing constructs like `len__ > TMP_BUF_MAX ? TMP_BUF_MAX