Re: checkpatch changes for 4.16

2018-01-31 Thread Tobin C. Harding
On Wed, Jan 31, 2018 at 03:56:19PM -0800, Joe Perches wrote: > On Thu, 2018-02-01 at 10:23 +1100, Tobin C. Harding wrote: > > On Wed, Jan 31, 2018 at 02:48:56PM -0800, Joe Perches wrote: > > > On Thu, 2018-02-01 at 08:46 +1100, Tobin C. Harding wrote: > > > > Hi Joe, > > > > > > > > Can I please b

Re: checkpatch changes for 4.16

2018-01-31 Thread Joe Perches
On Thu, 2018-02-01 at 10:23 +1100, Tobin C. Harding wrote: > On Wed, Jan 31, 2018 at 02:48:56PM -0800, Joe Perches wrote: > > On Thu, 2018-02-01 at 08:46 +1100, Tobin C. Harding wrote: > > > Hi Joe, > > > > > > Can I please bother you with a maintainer question. I know everyone is > > > super bus

Re: checkpatch changes for 4.16

2018-01-31 Thread Tobin C. Harding
On Wed, Jan 31, 2018 at 02:48:56PM -0800, Joe Perches wrote: > On Thu, 2018-02-01 at 08:46 +1100, Tobin C. Harding wrote: > > Hi Joe, > > > > Can I please bother you with a maintainer question. I know everyone is > > super busy right now, I'm asking for a smidgen of your time instead of > > doing

Re: checkpatch changes for 4.16

2018-01-31 Thread Joe Perches
On Thu, 2018-02-01 at 08:46 +1100, Tobin C. Harding wrote: > Hi Joe, > > Can I please bother you with a maintainer question. I know everyone is > super busy right now, I'm asking for a smidgen of your time instead of > doing it wrong and taking up some of Linus' time since it's merge window > and

checkpatch changes for 4.16

2018-01-31 Thread Tobin C. Harding
o a GIT PULL to Linus. My concern is that the subject line may not be unique if checkpatch changes are coming in from various trees this merge window. I have tagged the pull request with checkpatch-4.16-rc1 with the subject line [GIT PULL] checkpatch changes for 4.16-rc1 If the