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 00/14] ethtool: Use memory maps for EEPROM parsing
Date: Wed, 17 Nov 2021 12:37:05 +0200 [thread overview]
Message-ID: <YZTbUVAvmR4hmOXl@shredder> (raw)
In-Reply-To: <YXnMG6e7mglldHIZ@shredder>
On Thu, Oct 28, 2021 at 01:01:05AM +0300, Ido Schimmel wrote:
> On Wed, Oct 27, 2021 at 10:30:45PM +0200, Michal Kubecek wrote:
> > On Tue, Oct 12, 2021 at 04:25:11PM +0300, Ido Schimmel wrote:
> > > From: Ido Schimmel <idosch@nvidia.com>
> > >
> > > This patchset prepares ethtool(8) for retrieval and parsing of optional
> > > and banked module EEPROM pages, such as the ones present in CMIS. This
> > > is done by better integration of the recent 'MODULE_EEPROM_GET' netlink
> > > interface into ethtool(8).
> >
> > I still need to take a closer look at some of the patches but just to be
> > sure: the only reason to leave this series for 5.16 cycle is that it's
> > rather big and intrusive change (i.e. it does not depend on any kernel
> > functionality not present in 5.15), right?
>
> Right, it does not depend on any kernel functionality not present in
> 5.15
Can the patchset be applied to ethtool-next please? It is marked as
"Under Review" for over a month now and I would like to make progress
with other patches I have in the queue.
Thanks
next prev parent reply other threads:[~2021-11-17 10:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 13:25 [PATCH ethtool-next 00/14] ethtool: Use memory maps for EEPROM parsing Ido Schimmel
2021-10-12 13:25 ` [PATCH ethtool-next 01/14] cmis: Rename CMIS parsing functions Ido Schimmel
2021-10-12 13:25 ` [PATCH ethtool-next 02/14] cmis: Initialize CMIS memory map Ido Schimmel
2021-10-12 13:25 ` [PATCH ethtool-next 03/14] cmis: Use memory map during parsing Ido Schimmel
2021-10-12 13:25 ` [PATCH ethtool-next 04/14] cmis: Consolidate code between IOCTL and netlink paths Ido Schimmel
2021-10-12 13:25 ` [PATCH ethtool-next 05/14] sff-8636: Rename SFF-8636 parsing functions Ido Schimmel
2021-10-12 13:25 ` [PATCH ethtool-next 06/14] sff-8636: Initialize SFF-8636 memory map Ido Schimmel
2021-10-12 13:25 ` [PATCH ethtool-next 07/14] sff-8636: Use memory map during parsing Ido Schimmel
2021-10-12 13:25 ` [PATCH ethtool-next 08/14] sff-8636: Consolidate code between IOCTL and netlink paths Ido Schimmel
2021-10-12 13:25 ` [PATCH ethtool-next 09/14] sff-8079: Split SFF-8079 parsing function Ido Schimmel
2021-10-12 13:25 ` [PATCH ethtool-next 10/14] netlink: eeprom: Export a function to request an EEPROM page Ido Schimmel
2021-10-12 13:25 ` [PATCH ethtool-next 11/14] cmis: Request specific pages for parsing in netlink path Ido Schimmel
2021-10-12 13:25 ` [PATCH ethtool-next 12/14] sff-8636: " Ido Schimmel
2021-10-12 13:25 ` [PATCH ethtool-next 13/14] sff-8079: " Ido Schimmel
2021-10-12 13:25 ` [PATCH ethtool-next 14/14] netlink: eeprom: Defer page requests to individual parsers Ido Schimmel
2021-10-27 20:30 ` [PATCH ethtool-next 00/14] ethtool: Use memory maps for EEPROM parsing Michal Kubecek
2021-10-27 22:00 ` Ido Schimmel
2021-11-17 10:37 ` Ido Schimmel [this message]
2021-11-21 23:20 ` 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=YZTbUVAvmR4hmOXl@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.