linux-kernel - Re: [PATCH v3 5/9] VMware balloon: Show capabilities of balloon and resulting capabilities in the debug-fs node.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <D1E7C6C1.3AB16%jsavanyo@vmware.com>
Date:	Wed, 5 Aug 2015 21:11:46 +0000
From:	John Savanyo <jsavanyo@...are.com>
To:	"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
CC:	"dmitry.torokhov@...il.com" <dmitry.torokhov@...il.com>,
	Philip Moltmann <moltmann@...are.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"pv-drivers@...are.com" <pv-drivers@...are.com>,
	Xavier Deguillard <xdeguillard@...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.

On 8/5/15, 1:50 PM, "gregkh@...uxfoundation.org"
<gregkh@...uxfoundation.org> wrote:

>You have to always diff the code anyway, you can't trust that number,
>see my other email as to why.
>
>greg k-h

I agree that we need to look at the source code to 100% understand that
status of a driver. However, if VMware has a practice of bumping the
version number for our contributions to help with some of our internal
processes, then I don¹t see any harm in allowing this practice to
continue. We are not asking you personally to interpret these version
numbers in any way. So it should be of little consequence to you to just
accept them as part of our contributions in the future.

Thanks,
John

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/