From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keller, Jacob E Date: Tue, 3 Nov 2015 23:05:12 +0000 Subject: [Intel-wired-lan] [PATCH v2] fm10k: don't initialize fm10k_workqueue at global level In-Reply-To: <804857E1F29AAC47BF68C404FC60A1847EC762DE@ORSMSX105.amr.corp.intel.com> References: <1446579302-11494-1-git-send-email-jacob.e.keller@intel.com> <804857E1F29AAC47BF68C404FC60A1847EC762DE@ORSMSX105.amr.corp.intel.com> Message-ID: <1446591912.3990.28.camel@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: intel-wired-lan@osuosl.org List-ID: On Tue, 2015-11-03 at 22:40 +0000, Allan, Bruce W wrote: > > -----Original Message----- > > From: Keller, Jacob E > > Sent: Tuesday, November 03, 2015 11:35 AM > > To: Intel Wired LAN > > Cc: Allan, Bruce W; Keller, Jacob E > > Subject: [PATCH v2] fm10k: don't initialize fm10k_workqueue at > > global level > > > > From: Bruce Allan > > > > Cleans up checkpatch GLOBAL_INITIALIZERS error > > > > Signed-off-by: Bruce Allan > > Signed-off-by: Jacob Keller > > --- > > -v2 > > * Fix title from checkpatch complaint > > Out of curiosity, what was wrong with the original v1 patch title and > what was the exact checkpatch complaint? > checkpatch.pl results for patch "[PATCH] fm10k: fix checkpatch GLOBAL_INITIALISERS error" WARNING:EMAIL_SUBJECT: A patch subject line should describe the change not the tool that found it #4: Subject: [PATCH] fm10k: fix checkpatch GLOBAL_INITIALISERS error total: 0 errors, 1 warnings, 0 checks, 24 lines checked Regards, Jake