All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Danielle Ratson <danieller@nvidia.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"eric.dumazet@gmail.com" <eric.dumazet@gmail.com>,
	"mkubecek@suse.cz" <mkubecek@suse.cz>,
	"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
	"acardace@redhat.com" <acardace@redhat.com>,
	"irusskikh@marvell.com" <irusskikh@marvell.com>,
	"gustavo@embeddedor.com" <gustavo@embeddedor.com>,
	"magnus.karlsson@intel.com" <magnus.karlsson@intel.com>,
	"ecree@solarflare.com" <ecree@solarflare.com>,
	Ido Schimmel <idosch@nvidia.com>, Jiri Pirko <jiri@nvidia.com>,
	mlxsw <mlxsw@nvidia.com>
Subject: Re: [PATCH net v2 1/2] ethtool: Add link_mode parameter capability bit to ethtool_ops
Date: Sun, 4 Apr 2021 18:07:00 +0200	[thread overview]
Message-ID: <YGnkJIY6Dmk97w2b@lunn.ch> (raw)
In-Reply-To: <DM6PR12MB45163C0617DC03F24E6CCEA0D8789@DM6PR12MB4516.namprd12.prod.outlook.com>

> First, it is not the API structure that is passed to user space. Please pay attention

Yes, sorry. Jumped to assumptions without checking.

Let me try again.

    Andrew

  reply	other threads:[~2021-04-04 16:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-04  8:14 [PATCH net v2 0/2] Fix link_mode derived params functionality Danielle Ratson
2021-04-04  8:14 ` [PATCH net v2 1/2] ethtool: Add link_mode parameter capability bit to ethtool_ops Danielle Ratson
2021-04-04 14:18   ` Andrew Lunn
2021-04-04 15:04     ` Danielle Ratson
2021-04-04 16:07       ` Andrew Lunn [this message]
2021-04-04 16:32   ` Andrew Lunn
2021-04-05 17:01     ` Danielle Ratson
2021-04-04  8:14 ` [PATCH net v2 2/2] ethtool: Derive parameters from link_mode in ioctl path Danielle Ratson

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=YGnkJIY6Dmk97w2b@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=acardace@redhat.com \
    --cc=danieller@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=ecree@solarflare.com \
    --cc=eric.dumazet@gmail.com \
    --cc=f.fainelli@gmail.com \
    --cc=gustavo@embeddedor.com \
    --cc=idosch@nvidia.com \
    --cc=irusskikh@marvell.com \
    --cc=jiri@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=magnus.karlsson@intel.com \
    --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 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.