From: Greg KH <gregkh@suse.de>
To: Hank Janssen <hjanssen@microsoft.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
Haiyang Zhang <haiyangz@microsoft.com>
Subject: Re: [PATCH 1/2] Staging: hv: Add proper versioning to HV drivers
Date: Thu, 11 Feb 2010 13:36:51 -0800 [thread overview]
Message-ID: <20100211213651.GA29557@suse.de> (raw)
In-Reply-To: <8AFC7968D54FB448A30D8F38F259C56212E88287@TK5EX14MBXC118.redmond.corp.microsoft.com>
On Thu, Feb 11, 2010 at 09:32:29PM +0000, Hank Janssen wrote:
>
> Provide proper versioning information for all HV drivers.
>
>
> Cc: Greg Kroah-Hartman <gregkh@suse.de>
> Signed-off-by: Hank Janssen <hjanssen@microsoft.com>
> Signed-off-by: Haiyang Zhang <haiyang@microsoft.com>
>
>
> drivers/staging/hv/VersionInfo.h | 11 ++++++++---
> drivers/staging/hv/Vmbus.c | 8 ++++----
> drivers/staging/hv/blkvsc_drv.c | 2 ++
> drivers/staging/hv/netvsc_drv.c | 5 +++--
> drivers/staging/hv/storvsc_drv.c | 2 ++
> drivers/staging/hv/vmbus_drv.c | 2 ++
> 6 files changed, 21 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/staging/hv/VersionInfo.h b/drivers/staging/hv/VersionInfo.h
> index 9c3641d..e729b9e 100644
> --- a/drivers/staging/hv/VersionInfo.h
> +++ b/drivers/staging/hv/VersionInfo.h
> @@ -24,8 +24,13 @@
> #ifndef __HV_VERSION_INFO
> #define __HV_VERSION_INFO
>
> -static const char VersionDate[] = __DATE__;
> -static const char VersionTime[] = __TIME__;
> -static const char VersionDesc[] = "Version 2.0";
> +static const char hv_build_date[] = __DATE__;
> +static const char hv_build_time[] = __TIME__;
This should not be needed at all, as it make absolutely no sense.
> +/*
> + * We use the same version numbering for all Hyper-V modules.
> + */
> +#define HV_DRV_VERSION "3.0.0"
Is this really needed? Now that the code is in the kernel tree,
shouldn't you be tracking this based on kernel release version (like 90%
of the drivers are tracked), or is there some requirement for a version
number?
And what decides when this number is changed? What does it "mean"?
What is it tracking?
thanks,
greg k-h
next prev parent reply other threads:[~2010-02-11 21:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 21:32 [PATCH 1/2] Staging: hv: Add proper versioning to HV drivers Hank Janssen
2010-02-11 21:36 ` Greg KH [this message]
2010-02-11 22:15 ` Hank Janssen
2010-02-11 22:27 ` Greg KH
2010-02-11 23:11 ` Hank Janssen
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=20100211213651.GA29557@suse.de \
--to=gregkh@suse.de \
--cc=devel@driverdev.osuosl.org \
--cc=haiyangz@microsoft.com \
--cc=hjanssen@microsoft.com \
--cc=linux-kernel@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