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:   Wed, 16 Oct 2019 13:45:03 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     andrew@...n.ch
Cc:     o.rempel@...gutronix.de, chris.snook@...il.com,
        f.fainelli@...il.com, jhogan@...nel.org, jcliburn@...il.com,
        mark.rutland@....com, paul.burton@...s.com, ralf@...ux-mips.org,
        robh+dt@...nel.org, linux@...linux.org.uk,
        vivien.didelot@...il.com, kernel@...gutronix.de,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
        devicetree@...r.kernel.org, linux-mips@...r.kernel.org
Subject: Re: [PATCH v1 1/4] net: ag71xx: port to phylink

From: Andrew Lunn <andrew@...n.ch>
Date: Wed, 16 Oct 2019 15:32:15 +0200

> I don't know if there are any strict rules, but i tend to use To: for
> the maintainer you expect to merge the patch, and Cc: for everybody
> else, and the lists.

This is a good way to handle things.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ