Netdev List
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: David Miller <davem@davemloft.net>, venza@brownhat.org
Cc: sergej.benilov@googlemail.com, netdev@vger.kernel.org
Subject: Re: [PATCH] sis900: increment revision number
Date: Sun, 23 Jun 2019 09:26:26 -0700	[thread overview]
Message-ID: <76a3c9ed832dd1183a5c38bf5e581a4b080d06c0.camel@perches.com> (raw)
In-Reply-To: <20190623.083724.172652862205625872.davem@davemloft.net>

On Sun, 2019-06-23 at 08:37 -0700, David Miller wrote:
> From: Daniele Venzano <venza@brownhat.org>
> Date: Sun, 23 Jun 2019 11:13:28 +0200
> 
> > Hello,
> > 
> > I think it is good to know just by looking at the sources that the
> > driver is still kept up-to-date, so I am in favor of this patch.
> 
> I absolutely, strongly, disagree.
> 
> These are pointless.

Perhaps (most)? all the .get_drvinfo function calls where the
driver version is returned should use the default release.

This is similar to net/wireless/ethtool.c

Maybe:
---
 net/core/ethtool.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/net/core/ethtool.c b/net/core/ethtool.c
index 4d1011b2e24f..644a2043714c 100644
--- a/net/core/ethtool.c
+++ b/net/core/ethtool.c
@@ -23,6 +23,7 @@
 #include <linux/rtnetlink.h>
 #include <linux/sched/signal.h>
 #include <linux/net.h>
+#include <linux/utsname.h>
 #include <net/devlink.h>
 #include <net/xdp_sock.h>
 #include <net/flow_offload.h>
@@ -806,6 +807,8 @@ static noinline_for_stack int ethtool_get_drvinfo(struct net_device *dev,
 		devlink_compat_running_version(dev, info.fw_version,
 					       sizeof(info.fw_version));
 
+	strlcpy(info.version, init_utsname()->release, sizeof(info.version));
+
 	if (copy_to_user(useraddr, &info, sizeof(info)))
 		return -EFAULT;
 	return 0;



  reply	other threads:[~2019-06-23 16:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-23  7:47 [PATCH] sis900: increment revision number Sergej Benilov
2019-06-23  8:57 ` Daniele Venzano
2019-06-23  9:10 ` Joe Perches
2019-06-23  9:13   ` Daniele Venzano
2019-06-23 15:37     ` David Miller
2019-06-23 16:26       ` Joe Perches [this message]
2019-06-23 15:36 ` David Miller

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=76a3c9ed832dd1183a5c38bf5e581a4b080d06c0.camel@perches.com \
    --to=joe@perches.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=sergej.benilov@googlemail.com \
    --cc=venza@brownhat.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