From: Andreas Schwab <schwab@suse.de>
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: "Mark Rutland" <mark.rutland@arm.com>,
devicetree@vger.kernel.org, "Albert Ou" <aou@eecs.berkeley.edu>,
netdev <netdev@vger.kernel.org>,
"Palmer Dabbelt" <palmer@sifive.com>,
"Nicolas Ferre" <Nicolas.Ferre@microchip.com>,
"linux-kernel@vger.kernel.org List"
<linux-kernel@vger.kernel.org>,
"Sachin Ghadi" <sachin.ghadi@sifive.com>,
"Yash Shah" <yash.shah@sifive.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Petr Štetiar" <ynezz@true.cz>,
linux-riscv@lists.infradead.org,
"David Miller" <davem@davemloft.net>
Subject: Re: [PATCH 2/3] macb: Update compatibility string for SiFive FU540-C000
Date: Tue, 20 Aug 2019 11:10:20 +0200 [thread overview]
Message-ID: <mvm5zmskxs3.fsf@suse.de> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1908131142150.5033@viisi.sifive.com> (Paul Walmsley's message of "Tue, 13 Aug 2019 11:42:49 -0700 (PDT)")
On Aug 13 2019, Paul Walmsley <paul.walmsley@sifive.com> wrote:
> Dave, Nicolas,
>
> On Mon, 22 Jul 2019, Yash Shah wrote:
>
>> On Fri, Jul 19, 2019 at 5:36 PM <Nicolas.Ferre@microchip.com> wrote:
>> >
>> > On 19/07/2019 at 13:10, Yash Shah wrote:
>> > > Update the compatibility string for SiFive FU540-C000 as per the new
>> > > string updated in the binding doc.
>> > > Reference: https://lkml.org/lkml/2019/7/17/200
>> >
>> > Maybe referring to lore.kernel.org is better:
>> > https://lore.kernel.org/netdev/CAJ2_jOFEVZQat0Yprg4hem4jRrqkB72FKSeQj4p8P5KA-+rgww@mail.gmail.com/
>>
>> Sure. Will keep that in mind for future reference.
>>
>> >
>> > > Signed-off-by: Yash Shah <yash.shah@sifive.com>
>> >
>> > Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
>>
>> Thanks.
>
> Am assuming you'll pick this up for the -net tree for v5.4-rc1 or earlier.
> If not, please let us know.
This is still missing in v5.4-rc5, which means that networking is broken.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Schwab <schwab@suse.de>
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: "Nicolas Ferre" <Nicolas.Ferre@microchip.com>,
"David Miller" <davem@davemloft.net>,
"Yash Shah" <yash.shah@sifive.com>,
"Rob Herring" <robh+dt@kernel.org>,
netdev <netdev@vger.kernel.org>,
devicetree@vger.kernel.org,
"linux-kernel@vger.kernel.org List"
<linux-kernel@vger.kernel.org>,
linux-riscv@lists.infradead.org,
"Mark Rutland" <mark.rutland@arm.com>,
"Palmer Dabbelt" <palmer@sifive.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Petr Štetiar" <ynezz@true.cz>,
"Sachin Ghadi" <sachin.ghadi@sifive.com>
Subject: Re: [PATCH 2/3] macb: Update compatibility string for SiFive FU540-C000
Date: Tue, 20 Aug 2019 11:10:20 +0200 [thread overview]
Message-ID: <mvm5zmskxs3.fsf@suse.de> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1908131142150.5033@viisi.sifive.com> (Paul Walmsley's message of "Tue, 13 Aug 2019 11:42:49 -0700 (PDT)")
On Aug 13 2019, Paul Walmsley <paul.walmsley@sifive.com> wrote:
> Dave, Nicolas,
>
> On Mon, 22 Jul 2019, Yash Shah wrote:
>
>> On Fri, Jul 19, 2019 at 5:36 PM <Nicolas.Ferre@microchip.com> wrote:
>> >
>> > On 19/07/2019 at 13:10, Yash Shah wrote:
>> > > Update the compatibility string for SiFive FU540-C000 as per the new
>> > > string updated in the binding doc.
>> > > Reference: https://lkml.org/lkml/2019/7/17/200
>> >
>> > Maybe referring to lore.kernel.org is better:
>> > https://lore.kernel.org/netdev/CAJ2_jOFEVZQat0Yprg4hem4jRrqkB72FKSeQj4p8P5KA-+rgww@mail.gmail.com/
>>
>> Sure. Will keep that in mind for future reference.
>>
>> >
>> > > Signed-off-by: Yash Shah <yash.shah@sifive.com>
>> >
>> > Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
>>
>> Thanks.
>
> Am assuming you'll pick this up for the -net tree for v5.4-rc1 or earlier.
> If not, please let us know.
This is still missing in v5.4-rc5, which means that networking is broken.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2019-08-20 9:10 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 11:10 [PATCH 1/3] macb: bindings doc: update sifive fu540-c000 binding Yash Shah
2019-07-19 11:10 ` Yash Shah
2019-07-19 11:10 ` [PATCH 2/3] macb: Update compatibility string for SiFive FU540-C000 Yash Shah
2019-07-19 11:10 ` Yash Shah
2019-07-19 12:05 ` Nicolas.Ferre
2019-07-19 12:05 ` Nicolas.Ferre
2019-07-19 12:05 ` Nicolas.Ferre
2019-07-22 4:39 ` Yash Shah
2019-07-22 4:39 ` Yash Shah
2019-08-13 18:42 ` Paul Walmsley
2019-08-13 18:42 ` Paul Walmsley
2019-08-20 9:10 ` Andreas Schwab [this message]
2019-08-20 9:10 ` Andreas Schwab
2019-08-20 10:16 ` Nicolas.Ferre
2019-08-20 10:16 ` Nicolas.Ferre
2019-08-20 10:16 ` Nicolas.Ferre
2019-07-22 20:02 ` Paul Walmsley
2019-07-22 20:02 ` Paul Walmsley
2019-07-22 21:46 ` Paul Walmsley
2019-07-22 21:46 ` Paul Walmsley
2019-07-19 11:10 ` [PATCH 3/3] riscv: dts: Add DT node for SiFive FU540 Ethernet controller driver Yash Shah
2019-07-19 11:10 ` Yash Shah
2019-07-19 11:53 ` Sagar Kadam
2019-07-19 11:53 ` Sagar Kadam
2019-07-19 13:26 ` Andrew Lunn
2019-07-19 13:26 ` Andrew Lunn
2019-07-22 8:27 ` Sagar Kadam
2019-07-22 8:27 ` Sagar Kadam
2019-07-22 21:48 ` Paul Walmsley
2019-07-22 21:48 ` Paul Walmsley
2019-08-12 23:33 ` Rob Herring
2019-08-12 23:33 ` Rob Herring
2019-07-19 12:02 ` [PATCH 1/3] macb: bindings doc: update sifive fu540-c000 binding Nicolas.Ferre
2019-07-19 12:02 ` Nicolas.Ferre
2019-07-19 12:02 ` Nicolas.Ferre
2019-07-22 19:59 ` Paul Walmsley
2019-07-22 19:59 ` Paul Walmsley
2019-08-12 23:32 ` Rob Herring
2019-08-12 23:32 ` Rob Herring
2019-08-12 23:32 ` Rob Herring
2019-08-13 18:41 ` Paul Walmsley
2019-08-13 18:41 ` Paul Walmsley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mvm5zmskxs3.fsf@suse.de \
--to=schwab@suse.de \
--cc=Nicolas.Ferre@microchip.com \
--cc=aou@eecs.berkeley.edu \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=sachin.ghadi@sifive.com \
--cc=yash.shah@sifive.com \
--cc=ynezz@true.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.