From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754110AbbHEUWk (ORCPT ); Wed, 5 Aug 2015 16:22:40 -0400 Received: from smtp-outbound-2.vmware.com ([208.91.2.13]:55600 "EHLO smtp-outbound-2.vmware.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753731AbbHEUWh (ORCPT ); Wed, 5 Aug 2015 16:22:37 -0400 From: Philip Moltmann To: "gregkh@linuxfoundation.org" CC: "dmitry.torokhov@gmail.com" , "linux-kernel@vger.kernel.org" , "pv-drivers@vmware.com" , Xavier Deguillard , John Savanyo , "akpm@linux-foundation.org" Subject: Re: [PATCH v3 5/9] VMware balloon: Show capabilities of balloon and resulting capabilities in the debug-fs node. Thread-Topic: [PATCH v3 5/9] VMware balloon: Show capabilities of balloon and resulting capabilities in the debug-fs node. Thread-Index: AQHQpT+vwwbuBIoJOEGl7QdYGCqGGZ3+oaeAgAACLQA= Date: Wed, 5 Aug 2015 20:22:35 +0000 Message-ID: <1438806166.31263.203.camel@vmware.com> References: <20150612161513.GA23859@dtor-pixel> <1434134610-2831-6-git-send-email-moltmann@vmware.com> <20150805201459.GA16009@kroah.com> In-Reply-To: <20150805201459.GA16009@kroah.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-mailer: Evolution 3.16.4 (3.16.4-2.fc22) x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.113.160.246] Content-Type: text/plain; charset="utf-8" Content-ID: <62E00A1A2B8BAF4E9FA4ADE11E0ABF6E@pa-exch1.vmware.com> MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id t75KMltQ010628 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{.n++%ݶw{.n+{G{ayʇڙ,jfhz_(階ݢj"mG?&~iOzv^m ?I