Linux wireless drivers development
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Amitkumar Karwar <amitkarwar@gmail.com>
Cc: linux-wireless@vger.kernel.org,
	Amitkumar Karwar <amit.karwar@redpinesignals.com>,
	Prameela Rani Garnepudi <prameela.j04cs@gmail.com>,
	Pavani Muthyala <pavani.muthyala@redpinesignals.com>
Subject: Re: [PATCH] rsi: add driver and firmware version info
Date: Tue, 19 Sep 2017 17:39:01 +0300	[thread overview]
Message-ID: <87mv5qah2y.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1504094535-6680-1-git-send-email-amitkarwar@gmail.com> (Amitkumar Karwar's message of "Wed, 30 Aug 2017 17:32:15 +0530")

Amitkumar Karwar <amitkarwar@gmail.com> writes:

> From: Pavani Muthyala <pavani.muthyala@redpinesignals.com>
>
> We will dump information about driver and firmware versions,
> firmware file name and operating mode during initialization.
>
> Signed-off-by: Pavani Muthyala <pavani.muthyala@redpinesignals.com>
> Signed-off-by: Amitkumar Karwar <amit.karwar@redpinesignals.com>

[...]

> +void rsi_print_version(struct rsi_common *common)
> +{
> +	memcpy(common->driver_ver, DRV_VER, ARRAY_SIZE(DRV_VER));
> +	common->driver_ver[ARRAY_SIZE(DRV_VER)] = '\0';
> +
> +	rsi_dbg(ERR_ZONE, "================================================\n");
> +	rsi_dbg(ERR_ZONE, "================ RSI Version Info ==============\n");
> +	rsi_dbg(ERR_ZONE, "================================================\n");
> +	rsi_dbg(ERR_ZONE, "FW Version\t: %d.%d.%d\n",
> +		common->lmac_ver.major, common->lmac_ver.minor,
> +		common->lmac_ver.release_num);
> +	rsi_dbg(ERR_ZONE, "Driver Version\t: %s", common->driver_ver);
> +	rsi_dbg(ERR_ZONE, "Operating mode\t: %d [%s]",
> +		common->oper_mode, opmode_str(common->oper_mode));
> +	rsi_dbg(ERR_ZONE, "Firmware file\t: %s", common->priv->fw_file_name);
> +	rsi_dbg(ERR_ZONE, "================================================\n");
> +}
> +

[...]

> +#define DRV_VER				"RS911X.NB0.NL.GNU.LNX.1.0"

The concept of a driver version does not really work with upstream
drivers. The history has shown multiple times that the driver version
won't be updated for years and thus it won't have any meaning. So better
remove driver_ver from the driver entirely.

-- 
Kalle Valo

  reply	other threads:[~2017-09-19 14:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-30 12:02 [PATCH] rsi: add driver and firmware version info Amitkumar Karwar
2017-09-19 14:39 ` Kalle Valo [this message]
2017-09-21 14:33   ` Amitkumar Karwar

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=87mv5qah2y.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=amit.karwar@redpinesignals.com \
    --cc=amitkarwar@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pavani.muthyala@redpinesignals.com \
    --cc=prameela.j04cs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox