linux-kernel - Re: [PATCH] leds: as3645a: Fix checkpatch warnings

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <799ae164-701a-87ce-fadf-8278f01c10d6@ti.com>
Date:   Wed, 13 Dec 2017 14:49:38 -0600
From:   Dan Murphy <dmurphy@...com>
To:     Jacek Anaszewski <jacek.anaszewski@...il.com>,
        <robh+dt@...nel.org>, <mark.rutland@....com>, <rpurdie@...ys.net>,
        <pavel@....cz>, <sakari.ailus@....fi>,
        <laurent.pinchart@...asonboard.com>
CC:     <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <linux-leds@...r.kernel.org>
Subject: Re: [PATCH] leds: as3645a: Fix checkpatch warnings

Pavel and Laurent

On 12/13/2017 02:43 PM, Jacek Anaszewski wrote:
> Dan,
> 
> On 12/13/2017 09:41 PM, Dan Murphy wrote:
>> Jacek
>>
>> On 12/13/2017 02:29 PM, Jacek Anaszewski wrote:
>>> Hi Dan,
>>>
>>> checkpatch.pl doesn't want to be mentioned in the patch subject :-)
>>>
>>
>> Ack
>>
>>> "WARNING: A patch subject line should describe the change not the tool
>>> that found it"
>>>
>>> Preferably I'd see two separate patches.
>>>
>>
>> So you want me to split them up? I have no issue with that.
> 
> Yeah, it will be easier to come up with concise but meaningful
> subjects.
> 

When I split these up can I add your Acked-by to each patch or would you prefer to resend your
Acked-by for each patch?

Dan

>>> Also, line length limit for the commit description is 75 characters.
>>> Please use whole available space.
>>>
>>
>>
> 


-- 
------------------
Dan Murphy