From: Roger Quadros <rogerq@kernel.org>
To: Diogo Ivo <diogo.ivo@siemens.com>,
danishanwar@ti.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, andrew@lunn.ch,
linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org
Cc: jan.kiszka@siemens.com
Subject: Re: [PATCH net-next v4 04/10] net: ti: icssg-prueth: Add SR1.0-specific configuration bits
Date: Thu, 7 Mar 2024 14:48:20 +0200 [thread overview]
Message-ID: <286349b6-bcc9-4382-a4d0-29170cea1017@kernel.org> (raw)
In-Reply-To: <20240305114045.388893-5-diogo.ivo@siemens.com>
On 05/03/2024 13:40, Diogo Ivo wrote:
> Define the firmware configuration structure and commands needed to
> communicate with SR1.0 firmware, as well as SR1.0 buffer information
> where it differs from SR2.0.
>
> Based on the work of Roger Quadros, Murali Karicheri and
> Grygorii Strashko in TI's 5.10 SDK [1].
>
> [1]: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/?h=ti-linux-5.10.y
>
> Co-developed-by: Jan Kiszka <jan.kiszka@siemens.com>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> Signed-off-by: Diogo Ivo <diogo.ivo@siemens.com>
Reviewed-by: Roger Quadros <rogerq@kernel.org>
--
cheers,
-roger
next prev parent reply other threads:[~2024-03-07 12:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 11:40 [PATCH net-next v4 00/10] Support ICSSG-based Ethernet on AM65x SR1.0 devices Diogo Ivo
2024-03-05 11:40 ` [PATCH net-next v4 01/10] dt-bindings: net: Add support for AM65x SR1.0 in ICSSG Diogo Ivo
2024-03-05 11:40 ` [PATCH net-next v4 02/10] eth: Move IPv4/IPv6 multicast address bases to their own symbols Diogo Ivo
2024-03-05 11:40 ` [PATCH net-next v4 03/10] net: ti: icssg-prueth: Move common functions into a separate file Diogo Ivo
2024-03-05 11:40 ` [PATCH net-next v4 04/10] net: ti: icssg-prueth: Add SR1.0-specific configuration bits Diogo Ivo
2024-03-07 12:48 ` Roger Quadros [this message]
2024-03-05 11:40 ` [PATCH net-next v4 05/10] net: ti: icssg-prueth: Add SR1.0-specific description bits Diogo Ivo
2024-03-05 14:41 ` Russell King (Oracle)
2024-03-06 11:26 ` Diogo Ivo
2024-03-05 11:40 ` [PATCH net-next v4 06/10] net: ti: icssg-prueth: Adjust IPG configuration for SR1.0 Diogo Ivo
2024-03-05 11:40 ` [PATCH net-next v4 07/10] net: ti: icssg-prueth: Adjust the number of TX channels " Diogo Ivo
2024-03-05 11:40 ` [PATCH net-next v4 08/10] net: ti: icssg-prueth: Add functions to configure SR1.0 packet classifier Diogo Ivo
2024-03-07 13:13 ` Roger Quadros
2024-03-05 11:40 ` [PATCH net-next v4 09/10] net: ti: icssg-prueth: Modify common functions for SR1.0 Diogo Ivo
2024-03-07 13:15 ` Roger Quadros
2024-03-05 11:40 ` [PATCH net-next v4 10/10] net: ti: icssg-prueth: Add ICSSG Ethernet driver for AM65x SR1.0 platforms Diogo Ivo
2024-03-12 11:36 ` [PATCH net-next v4 00/10] Support ICSSG-based Ethernet on AM65x SR1.0 devices MD Danish Anwar
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=286349b6-bcc9-4382-a4d0-29170cea1017@kernel.org \
--to=rogerq@kernel.org \
--cc=andrew@lunn.ch \
--cc=danishanwar@ti.com \
--cc=davem@davemloft.net \
--cc=diogo.ivo@siemens.com \
--cc=edumazet@google.com \
--cc=jan.kiszka@siemens.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).