linux-kernel - Re: [PATCH v2 1/5] dt-bindings: spi/spi-pxa2xx: add PXA2xx SSP SPI Controller

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]

Date:   Tue, 18 Sep 2018 08:42:07 -0700
From:   Mark Brown <broonie@...nel.org>
To:     Lubomir Rintel <lkundrak@...sk>
Cc:     linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        devicetree@...r.kernel.org, linux-spi@...r.kernel.org,
        Rob Herring <robh+dt@...nel.org>,
        Mark Rutland <mark.rutland@....com>
Subject: Re: [PATCH v2 1/5] dt-bindings: spi/spi-pxa2xx: add PXA2xx SSP SPI
 Controller

On Tue, Sep 18, 2018 at 02:15:12PM +0200, Lubomir Rintel wrote:

> Should I've Cc'd everyone on the full series, even if only a patch or
> two might be really interesting to them? How do I decide whether the

It's a judgement call about who gets the patches but in general it's
good to either do that or make sure that everyone sees the cover letter
which explains what the whole series is.

> recipient needs to be in the commit's commit message (as opposed to
> just --cc on a command line)?

Using CCs in the commit message is entirely optional TBH - a lot of
people just don't do it at all, often when it is done it's a list of
everyone who got the mail.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)