netdev - Re: [PATCH v1 1/4] net: ag71xx: port to phylink

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 15:32:15 +0200
From:   Andrew Lunn <andrew@...n.ch>
To:     Oleksij Rempel <o.rempel@...gutronix.de>
Cc:     Chris Snook <chris.snook@...il.com>,
        Florian Fainelli <f.fainelli@...il.com>,
        James Hogan <jhogan@...nel.org>,
        Jay Cliburn <jcliburn@...il.com>,
        Mark Rutland <mark.rutland@....com>,
        Paul Burton <paul.burton@...s.com>,
        Ralf Baechle <ralf@...ux-mips.org>,
        Rob Herring <robh+dt@...nel.org>,
        Russell King <linux@...linux.org.uk>,
        Vivien Didelot <vivien.didelot@...il.com>,
        Pengutronix Kernel Team <kernel@...gutronix.de>,
        "David S. Miller" <davem@...emloft.net>, 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

On Wed, Oct 16, 2019 at 02:24:01PM +0200, Oleksij Rempel wrote:
> On Wed, Oct 16, 2019 at 02:12:16PM +0200, Andrew Lunn wrote:
> > On Mon, Oct 14, 2019 at 08:15:46AM +0200, Oleksij Rempel wrote:
> > > The port to phylink was done as close as possible to initial
> > > functionality.
> > > Theoretically this HW can support flow control, practically seems to be not
> > > enough to just enable it. So, more work should be done.
> > > 
> > > Signed-off-by: Oleksij Rempel <o.rempel@...gutronix.de>
> > 
> > Hi Oleksij
> > 
> > Please include Russell King in Cc: in future.
> 
> He was included in To:. Do you mean, I need to move him from To to Cc?

Ah, sorry. Missed him among all the other To:

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.

    Andrew