netdev - Re: [PATCH v2 0/2] Update ethernet compatible string for SiFive FU540

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]

Message-Id: <20190828.140644.534529249197568915.davem@davemloft.net>
Date:   Wed, 28 Aug 2019 14:06:44 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     yash.shah@...ive.com
Cc:     netdev@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org,
        robh+dt@...nel.org, mark.rutland@....com,
        nicolas.ferre@...rochip.com, palmer@...ive.com,
        paul.walmsley@...ive.com, ynezz@...e.cz, sachin.ghadi@...ive.com
Subject: Re: [PATCH v2 0/2] Update ethernet compatible string for SiFive
 FU540

From: Yash Shah <yash.shah@...ive.com>
Date: Tue, 27 Aug 2019 10:36:02 +0530

> This patch series renames the compatible property to a more appropriate
> string. The patchset is based on Linux-5.3-rc6 and tested on SiFive
> Unleashed board

You should always base changes off of "net" or "net-next" and be explicitly
in your Subject lines which of those two trees your changes are for f.e.:

	Subject: [PATCH v2 net-next N/M] ...

> 
> Change history:
> Since v1:
> - Dropped PATCH3 because it's already merged
> - Change the reference url in the patch descriptions to point to a
>   'lore.kernel.org' link instead of 'lkml.org'

Series applied to 'net'.