From: Philipp Zabel <p.zabel@pengutronix.de>
To: Horatiu Vultur <horatiu.vultur@microchip.com>,
robh+dt@kernel.org, lars.povlsen@microchip.com,
Steen.Hegelund@microchip.com, UNGLinuxDriver@microchip.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH v4 2/2] reset: mchp: sparx5: Extend support for lan966x
Date: Mon, 18 Oct 2021 12:43:55 +0200 [thread overview]
Message-ID: <46235d88ea5d3621eb8ab6fe150e9fcb3f9ebe1f.camel@pengutronix.de> (raw)
In-Reply-To: <20211018091522.1113510-3-horatiu.vultur@microchip.com>
On Mon, 2021-10-18 at 11:15 +0200, Horatiu Vultur wrote:
> This patch extends sparx5 driver to support also the lan966x. The
> process to reset the switch is the same only it has different offsets.
> Therefore make the driver more generic and add support for lan966x.
>
> Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
> Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Reviewed-by: Philipp Zabel <p.zabel@pengutronix.de>
regards
Philipp
next prev parent reply other threads:[~2021-10-18 10:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 9:15 [PATCH v4 0/2] Extend Sparx5 switch reset driver for lan966x Horatiu Vultur
2021-10-18 9:15 ` [PATCH v4 1/2] dt-bindings: reset: Add lan966x support Horatiu Vultur
2021-10-18 9:15 ` [PATCH v4 2/2] reset: mchp: sparx5: Extend support for lan966x Horatiu Vultur
2021-10-18 10:43 ` Philipp Zabel [this message]
2021-10-18 12:01 ` Steen Hegelund
2021-10-18 15:01 ` [PATCH v4 0/2] Extend Sparx5 switch reset driver " Philipp Zabel
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=46235d88ea5d3621eb8ab6fe150e9fcb3f9ebe1f.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=horatiu.vultur@microchip.com \
--cc=lars.povlsen@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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).