linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Benjamin Poirier <benjamin.poirier@gmail.com>
Cc: Netanel Belgazal <netanel@annapurnalabs.com>,
	netdev@vger.kernel.org, davem@davemloft.net,
	linux-kernel@vger.kernel.org, zorik@annapurnalabs.com,
	saeed@annapurnalabs.com, alex@annapurnalabs.com, msw@amazon.com,
	aliguori@amazon.com, ben@decadent.org.uk, romieu@fr.zoreil.com,
	rami.rosen@intel.com, antoine.tenart@free-electrons.com
Subject: Re: [PATCH net-next V3] net: ena: Add a driver for Amazon Elastic Network Adapters (ENA)
Date: Fri, 15 Jul 2016 18:47:48 +0300	[thread overview]
Message-ID: <20160715154748.GA10556@leon.nu> (raw)
In-Reply-To: <20160715151759.lfsncj62gi2b7mas@f1.synalogic.ca>

[-- Attachment #1: Type: text/plain, Size: 2141 bytes --]

On Fri, Jul 15, 2016 at 08:17:59AM -0700, Benjamin Poirier wrote:
> On 2016/07/15 08:00, Leon Romanovsky wrote:
> > On Thu, Jul 14, 2016 at 09:46:14AM +0300, Netanel Belgazal wrote:
> > > This is a driver for the ENA family of networking devices.
> > > 
> > > Signed-off-by: Netanel Belgazal <netanel@annapurnalabs.com>
> > > ---
> > > 
> > > Notes:
> > 
> > ...
> > 
> > >     - Increase driver version to 1.0.2
> > 
> > ...
> > 
> > > +static void ena_get_drvinfo(struct net_device *dev,
> > > +			    struct ethtool_drvinfo *info)
> > > +{
> > > +	struct ena_adapter *adapter = netdev_priv(dev);
> > > +
> > > +	strlcpy(info->driver, DRV_MODULE_NAME, sizeof(info->driver));
> > > +	strlcpy(info->version, DRV_MODULE_VERSION, sizeof(info->version));
> > 
> > Does module version give anything valuable in real life usage?
> > Do you plan to bump version after every patch?
> > 
> > Hint, NO.
> > 
> [...]
> > > +
> > > +#define DRV_MODULE_VER_MAJOR	1
> > > +#define DRV_MODULE_VER_MINOR	0
> > > +#define DRV_MODULE_VER_SUBMINOR 1
> > > +
> > > +#define DRV_MODULE_NAME		"ena"
> > > +#ifndef DRV_MODULE_VERSION
> > > +#define DRV_MODULE_VERSION \
> > > +	__stringify(DRV_MODULE_VER_MAJOR) "."	\
> > > +	__stringify(DRV_MODULE_VER_MINOR) "."	\
> > > +	__stringify(DRV_MODULE_VER_SUBMINOR)
> > > +#endif
> > > +#define DRV_MODULE_RELDATE      "22-JUNE-2016"
> > 
> > Please remove it, driver version is useless in real life kernel usage.
> > 
> 
> The release date might be a bit overkill but the driver version is
> useful in the context of distribution kernels where users sometimes mix
> and match newer drivers (ex: the intel sf.net drivers) with older
> kernels. When a bug is reported, a quick look at the module version can
> help indicate the provenance of the driver.

We already discussed it in a number of occasions, for example this is
response of Greg Kroah-Hartman to similar attempt to bump driver version
[1].

And as I said before, mostly this driver will change without any
reflection in driver version.

[1] http://www.spinics.net/lists/linux-rdma/msg29855.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-07-15 15:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-14  6:46 [PATCH net-next V3] net: ena: Add a driver for Amazon Elastic Network Adapters (ENA) Netanel Belgazal
2016-07-14 15:22 ` Matt Wilson
2016-07-14 16:08   ` Benjamin Poirier
2016-07-14 16:15     ` Matt Wilson
2016-07-15 18:29       ` David Miller
2016-07-15  5:00 ` Leon Romanovsky
2016-07-15 15:17   ` Benjamin Poirier
2016-07-15 15:47     ` Leon Romanovsky [this message]
2016-07-19 11:09   ` Netanel Belgazal
2016-07-19 17:26     ` Leon Romanovsky
2016-07-19 17:49       ` Joe Perches
2016-07-25  5:06         ` Leon Romanovsky
2016-07-19 18:39       ` Netanel Belgazal

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=20160715154748.GA10556@leon.nu \
    --to=leon@kernel.org \
    --cc=alex@annapurnalabs.com \
    --cc=aliguori@amazon.com \
    --cc=antoine.tenart@free-electrons.com \
    --cc=ben@decadent.org.uk \
    --cc=benjamin.poirier@gmail.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=msw@amazon.com \
    --cc=netanel@annapurnalabs.com \
    --cc=netdev@vger.kernel.org \
    --cc=rami.rosen@intel.com \
    --cc=romieu@fr.zoreil.com \
    --cc=saeed@annapurnalabs.com \
    --cc=zorik@annapurnalabs.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;
as well as URLs for NNTP newsgroup(s).