[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fac46880-ec04-0c7d-1746-e0c1a1e270ad@omp.ru>
Date: Mon, 11 Oct 2021 15:08:10 +0300
From: Sergey Shtylyov <s.shtylyov@....ru>
To: Biju Das <biju.das.jz@...renesas.com>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>
CC: Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@...renesas.com>,
"Andrew Lunn" <andrew@...n.ch>,
Geert Uytterhoeven <geert+renesas@...der.be>,
"Adam Ford" <aford173@...il.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@...esas.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-renesas-soc@...r.kernel.org"
<linux-renesas-soc@...r.kernel.org>,
Chris Paterson <Chris.Paterson2@...esas.com>,
Biju Das <biju.das@...renesas.com>
Subject: Re: [PATCH 00/14] Add functional support for Gigabit Ethernet driver
On 10/10/21 1:31 PM, Biju Das wrote:
[...]
>>>>>>>> The DMAC and EMAC blocks of Gigabit Ethernet IP found on RZ/G2L
>>>>>>>> SoC are similar to the R-Car Ethernet AVB IP.
>>>>>>>>
>>>>>>>> The Gigabit Ethernet IP consists of Ethernet controller (E-MAC),
>>>>>>>> Internal TCP/IP Offload Engine (TOE) and Dedicated Direct memory
>>>>>>>> access controller (DMAC).
>>>>>>>>
>>>>>>>> With a few changes in the driver we can support both IPs.
>>>>>>>>
>>>>>>>> This patch series is aims to add functional support for Gigabit
>>>>>>>> Ethernet driver by filling all the stubs except set_features.
>>>>>>>>
>>>>>>>> set_feature patch will send as separate RFC patch along with
>>>>>>>> rx_checksum patch, as it needs detailed discussion related to HW
>>>>>>> checksum.
>>>>>>>>
>>>>>>>> Ref:-
>>>>>>>>
>>>>>>>> https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2
>>>>>>>> Fp
>>>>>>>> atc
>>>>>>>> hwork.kernel.org%2Fproject%2Flinux-renesas-soc%2Flist%2F%3Fseries
>>>>>>>> %3
>>>>>>>> D55
>>>>>>>> 7655&data=04%7C01%7Cbiju.das.jz%40bp.renesas.com%7C25bc7b9155
>>>>>>>> d8
>>>>>>>> 402
>>>>>>>> a191808d98b5ae62f%7C53d82571da1947e49cb4625a166a4a2a%7C0%7C0%7C63
>>>>>>>> 76
>>>>>>>> 940
>>>>>>>> 44814904836%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV
>>>>>>>> 2l
>>>>>>>> uMz
>>>>>>>> IiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Vktj5v0GvrNf%2B
>>>>>>>> DN
>>>>>>>> IFs
>>>>>>>> e6xjCUm6OjtzwHvK3q8aG1E5Y%3D&reserved=0
>>>>>>>>
>>>>>>>> RFC->V1:
>>>>>>>> * Removed patch#3 will send it as RFC
>>>>>>>> * Removed rx_csum functionality from patch#7, will send it as
>>>>>>>> RFC
>>>>>>>> * Renamed "nc_queue" -> "nc_queues"
>>>>>>>> * Separated the comment patch into 2 separate patches.
>>>>>>>> * Documented PFRI register bit
>>>>>>>> * Added Sergy's Rb tag
>>>>>>>
>>>>>>> It's Sergey. :-)
>>>>>>
>>>>>> My Bad. Sorry will taken care this in future. I need to send V2, as
>>>>>> accidentally I have added 2 macros in patch #6 As part of RFC
>>>>>> discussion into v1. I will send V2 to remove this.
>>>>>
>>>>> I'm not seeing patches #2, #4, and #9 in my inboxes... :-/
>>>>
>>>> Seeing them now in the linux-renesas-soc folder in the GMail
>> account.
>>>> But they should have landed on the OMP account too. :-/
>>>
>>> Can you please confirm latest series[1] lands on your OMP account?
>>> [1]
>>> https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatc
>>> hwork.kernel.org%2Fproject%2Fnetdevbpf%2Flist%2F%3Fseries%3D560617&
>>> ;data=04%7C01%7Cbiju.das.jz%40bp.renesas.com%7C4ba52eb2327b42fb997c08d
>>> 98bd48373%7C53d82571da1947e49cb4625a166a4a2a%7C0%7C0%7C637694567141278
>>> 405%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTi
>>> I6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=LyurKu2sR%2BujQkts4LRyLMfPxw
>>> 7xmjON91zgS7f5Ktg%3D&reserved=0
>>
>> No, as I've told you already. Was unclear again. :-)
>
> Which patch doesn't have OMP account?
As I said, #2, #4, and #9.
> I am sure, I have added your OMP account
> As first cc list in the latest series.
Still not seeing them in v2.
> Regards,
> Biju
MBR, Sergey
Powered by blists - more mailing lists