linux-kernel - Re: [PATCH] drivers: wlan-ng: fixed a coding style issue

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1474584745.8253.39.camel@perches.com>
Date:   Thu, 22 Sep 2016 15:52:25 -0700
From:   Joe Perches <joe@...ches.com>
To:     becher.jannik@...il.com
Cc:     gregkh@...uxfoundation.org, devel@...verdev.osuosl.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] drivers: wlan-ng: fixed a coding style issue

On Fri, 2016-09-23 at 00:39 +0200, becher.jannik@...il.com wrote:
> On Thu, Sep 22, 2016 at 03:05:02PM -0700, Joe Perches wrote:
> > On Thu, 2016-09-22 at 23:56 +0200, Jannik Becher wrote:
> > >r emoved a space after a cast to obtain the coding style.
> > Better would be to change the subject to something like:
> > [PATCH] staging: wlan-ng: Remove unnecessary spaces before casts
> Should I resend the patch with this subject?
> Sorry for writing so many emails and asking questions. My problem is
> that I have no idea who to put in the cc if I'm responding to an email.

Yes, with an appropriate {PATCH V2] subject prefix.

Also do not leave the commit message blank.
Describe why you are making this change.
Maybe show the tool used to find and fix this issue too.