From: Ido Schimmel <idosch@idosch.org>
To: Michal Kubecek <mkubecek@suse.cz>
Cc: netdev@vger.kernel.org, popadrian1996@gmail.com, andrew@lunn.ch,
mlxsw@nvidia.com, moshe@nvidia.com,
Ido Schimmel <idosch@nvidia.com>
Subject: Re: [PATCH ethtool-next 0/8] ethtool: Add support for CMIS diagnostic information
Date: Thu, 2 Dec 2021 23:52:59 +0200 [thread overview]
Message-ID: <YalAO4PwKrJaFAZ4@shredder> (raw)
In-Reply-To: <20211202214518.rwhrmzwhdmzs3kue@lion.mk-sys.cz>
On Thu, Dec 02, 2021 at 10:45:18PM +0100, Michal Kubecek wrote:
> The series looks good to me and I'm ready to merge it but as it is
> marked "ethtool-next", I better make sure: is it OK to merge it into
> master branch (targeting ethtool 5.16)? In other words, do I see
> correctly that it does not depend on any features that would be missing
> in 5.16 kernel?
Yes
next prev parent reply other threads:[~2021-12-02 21:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 17:40 [PATCH ethtool-next 0/8] ethtool: Add support for CMIS diagnostic information Ido Schimmel
2021-11-23 17:40 ` [PATCH ethtool-next 1/8] sff-8636: Use an SFF-8636 specific define for maximum number of channels Ido Schimmel
2021-11-23 17:40 ` [PATCH ethtool-next 2/8] sff-common: Move OFFSET_TO_U16_PTR() to common header file Ido Schimmel
2021-12-02 21:55 ` Michal Kubecek
2021-11-23 17:40 ` [PATCH ethtool-next 3/8] cmis: Initialize Page 02h in memory map Ido Schimmel
2021-11-23 17:40 ` [PATCH ethtool-next 4/8] cmis: Initialize Banked Page 11h " Ido Schimmel
2021-11-23 17:40 ` [PATCH ethtool-next 5/8] cmis: Parse and print diagnostic information Ido Schimmel
2021-11-23 17:41 ` [PATCH ethtool-next 6/8] cmis: Print Module State and Fault Cause Ido Schimmel
2021-11-23 17:41 ` [PATCH ethtool-next 7/8] cmis: Print Module-Level Controls Ido Schimmel
2021-11-23 17:41 ` [PATCH ethtool-next 8/8] sff-8636: Print Power set and Power override bits Ido Schimmel
2021-12-02 21:45 ` [PATCH ethtool-next 0/8] ethtool: Add support for CMIS diagnostic information Michal Kubecek
2021-12-02 21:52 ` Ido Schimmel [this message]
2021-12-02 22:01 ` Michal Kubecek
2021-12-02 22:00 ` patchwork-bot+netdevbpf
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=YalAO4PwKrJaFAZ4@shredder \
--to=idosch@idosch.org \
--cc=andrew@lunn.ch \
--cc=idosch@nvidia.com \
--cc=mkubecek@suse.cz \
--cc=mlxsw@nvidia.com \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=popadrian1996@gmail.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