From: Ido Schimmel <idosch@idosch.org>
To: Michal Kubecek <mkubecek@suse.cz>
Cc: netdev@vger.kernel.org, kuba@kernel.org, mlxsw@nvidia.com,
Ido Schimmel <idosch@nvidia.com>
Subject: Re: [RFC PATCH ethtool] ethtool: Improve compatibility between netlink and ioctl interfaces
Date: Thu, 5 Nov 2020 14:43:29 +0200 [thread overview]
Message-ID: <20201105124329.GA1287772@shredder> (raw)
In-Reply-To: <20201104100515.GA988778@shredder>
On Wed, Nov 04, 2020 at 12:05:18PM +0200, Ido Schimmel wrote:
> On Wed, Nov 04, 2020 at 12:55:01AM +0100, Michal Kubecek wrote:
> > On Tue, Nov 03, 2020 at 04:24:30PM +0200, Ido Schimmel wrote:
> > >
> > > I have the changes you requested here:
> > > https://github.com/idosch/ethtool/commit/b34d15839f2662808c566c04eda726113e20ee59
> > >
> > > Do you want to integrate it with your nl_parse() rework or should I?
> >
> > I pushed the combined series to
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/mkubecek/ethtool.git
> >
> > as branch mk/master/advertise-all. I only ran few quick tests so far,
> > it's not submission ready yet.
> >
> > First two patches are unrelated fixes found while testing, I'm going to
> > submit and push them separately. Third patch reworks nl_parser()
> > handling of multiple request messages as indicated in my previous mail.
> > Fourth patch is the ioctl compatibility fix.
>
> Great, thank you. I pushed the patches to our regression. Will go over
> the results tomorrow and let you know.
Looks OK. Thanks again.
prev parent reply other threads:[~2020-11-05 12:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 18:40 [RFC PATCH ethtool] ethtool: Improve compatibility between netlink and ioctl interfaces Ido Schimmel
2020-11-02 22:58 ` Michal Kubecek
2020-11-03 14:24 ` Ido Schimmel
2020-11-03 23:55 ` Michal Kubecek
2020-11-04 10:05 ` Ido Schimmel
2020-11-05 12:43 ` 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=20201105124329.GA1287772@shredder \
--to=idosch@idosch.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=mkubecek@suse.cz \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.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).