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]
Date:   Fri, 01 Feb 2019 11:38:10 +1100
From:   tom burkart <tom@...sec.com>
To:     Joe Perches <joe@...ches.com>
Cc:     Rodolfo Giometti <giometti@...eenne.com>,
        Linux kernel mailing list <linux-kernel@...r.kernel.org>
Subject: Re: Fwd: [PATCH v14 0/3] PPS: pps-gpio PPS ECHO implementation

Quoting Joe Perches <joe@...ches.com>:

> On Thu, 2019-01-31 at 12:40 +1100, tom burkart wrote:
>> Quoting Rodolfo Giometti <giometti@...eenne.com>:
>> --------
>> Subject	Re: [PATCH v14 2/3] dt-bindings: pps: pps-gpio PPS ECHO  
>> implementation
>>
>> I think this patch it's OK but I'm asking to myself if it should be
>> merged with
>> next one... logically it describes what patch 3/3 does so why do we  
>> keep them
>> separated?
>> -------
>> I have separated it because scripts/checkpatch.pl insists it needs to
>> be separated.
>
> checkpatch doesn't insist on anything.  It's a stupid script.
>
> Always prefer your best judgment over a stupid script.

Further references:

 From Documentation/devicetree/bindings/submitting-patches.txt:

1) The Documentation/ and include/dt-bindings/ portion of the patch should
      be a separate patch. The preferred subject prefix for binding patches is:

      "dt-bindings: <binding dir>: ..."

Tom

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ