[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1438806166.31263.203.camel@vmware.com>
Date: Wed, 5 Aug 2015 20:22:35 +0000
From: Philip Moltmann <moltmann@...are.com>
To: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
CC: "dmitry.torokhov@...il.com" <dmitry.torokhov@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"pv-drivers@...are.com" <pv-drivers@...are.com>,
Xavier Deguillard <xdeguillard@...are.com>,
John Savanyo <jsavanyo@...are.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>
Subject: Re: [PATCH v3 5/9] VMware balloon: Show capabilities of balloon and
resulting capabilities in the debug-fs node.
Hi,
> > MODULE_AUTHOR("VMware, Inc.");
> > MODULE_DESCRIPTION("VMware Memory Control (Balloon) Driver");
> > -MODULE_VERSION("1.3.2.0-k");
> > +MODULE_VERSION("1.3.3.0-k");
>
> This constant change of module version is annoying, is it really even
> needed?
>
> I'll take this, but seriously consider just dropping it entirely as
> it
> doesn't mean anything now that the driver is in the kernel tree.
I think this is meant so that we can track which patches got backported
into RHEL and SLES.
CC-ing John as the policy comes from him.
Philip
Powered by blists - more mailing lists