[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJ2_jOGiTgGZ0TEZt6hBVB3oFxWkrrKVGQ6n__G4Zf_-ijY10Q@mail.gmail.com>
Date: Thu, 29 Aug 2019 15:24:58 +0530
From: Yash Shah <yash.shah@...ive.com>
To: David Miller <davem@...emloft.net>
Cc: netdev <netdev@...r.kernel.org>, devicetree@...r.kernel.org,
"linux-kernel@...r.kernel.org List" <linux-kernel@...r.kernel.org>,
linux-riscv@...ts.infradead.org, Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Nicolas Ferre <nicolas.ferre@...rochip.com>,
Palmer Dabbelt <palmer@...ive.com>,
Paul Walmsley <paul.walmsley@...ive.com>,
Petr Štetiar <ynezz@...e.cz>,
Sachin Ghadi <sachin.ghadi@...ive.com>
Subject: Re: [PATCH v2 0/2] Update ethernet compatible string for SiFive FU540
On Thu, Aug 29, 2019 at 2:36 AM David Miller <davem@...emloft.net> wrote:
>
> 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] ...
I will keep this in mind for future patches.
>
> >
> > 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'.
Thanks!
- Yash
Powered by blists - more mailing lists