netdev - Re: [PATCH 0/1] net: phy: mscc: add support for VSC8514 PHY

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]

Message-Id: <20190326.114130.1439471441091297640.davem@davemloft.net>
Date:   Tue, 26 Mar 2019 11:41:30 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     Kavyasree.Kotagiri@...rochip.com
Cc:     andrew@...n.ch, f.fainelli@...il.com, hkallweit1@...il.com,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
        quentin.schulz@...tlin.com
Subject: Re: [PATCH 0/1] net: phy: mscc: add support for VSC8514 PHY

This is formatted improperly.

The "[PATCH 0/N]" posting should just provide a commit message that
explains what the patch series is doing, how it is doing it, and why
it is doing it that way.

Then you have "[PATCH 1/N]", "[PATCH 2/N]" that actually contain the
patches of the series.

Have a look at how other developers submit a patch series on this
list.

Thanks.