From: Ido Schimmel <idosch@mellanox.com>
To: Ido Schimmel <idosch@idosch.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
Jiri Pirko <jiri@mellanox.com>, Petr Machata <petrm@mellanox.com>,
mlxsw <mlxsw@mellanox.com>
Subject: Re: [PATCH net-next 0/3] mlxsw: Update firmware version
Date: Mon, 28 Oct 2019 13:36:04 +0000 [thread overview]
Message-ID: <20191028133602.GA3999@splinter> (raw)
In-Reply-To: <20191024145149.6417-1-idosch@idosch.org>
On Thu, Oct 24, 2019 at 05:51:46PM +0300, Ido Schimmel wrote:
> From: Ido Schimmel <idosch@mellanox.com>
>
> This patch set updates the firmware version for Spectrum-1 and enforces
> a firmware version for Spectrum-2.
>
> The version adds support for querying port module type. It will be used
> by a followup patch set from Jiri to make port split code more generic.
>
> Patch #1 increases the size of an existing register in order to be
> compatible with the new firmware version. In the future the firmware
> will assign default values to fields not specified by the driver.
>
> Patch #2 bumps the firmware version for Spectrum-1.
>
> Patch #3 enforces a minimum firmware version for Spectrum-2.
Please ignore this patch set. I need to send v2 with another patch to
avoid regression with a particular system type.
Sorry for the noise.
prev parent reply other threads:[~2019-10-28 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 14:51 [PATCH net-next 0/3] mlxsw: Update firmware version Ido Schimmel
2019-10-24 14:51 ` [PATCH net-next 1/3] mlxsw: reg: Increase size of MPAR register Ido Schimmel
2019-10-24 14:51 ` [PATCH net-next 2/3] mlxsw: Bump firmware version to 13.2000.2308 Ido Schimmel
2019-10-24 14:51 ` [PATCH net-next 3/3] mlxsw: Enforce firmware version for Spectrum-2 Ido Schimmel
2019-10-28 13:36 ` Ido Schimmel [this message]
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=20191028133602.GA3999@splinter \
--to=idosch@mellanox.com \
--cc=davem@davemloft.net \
--cc=idosch@idosch.org \
--cc=jiri@mellanox.com \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=petrm@mellanox.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).