From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Mon, 3 Jul 2017 22:41:16 +0200 (CEST) From: Jiri Kosina To: Darren Hart In-Reply-To: <20170630162155.GB26257@fury> Message-ID: References: <20170625072423.GR1248@mtr-leonro.local> <20170630162155.GB26257@fury> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Cc: ksummit-discuss@lists.linux-foundation.org Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Driver and/or module versions List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Fri, 30 Jun 2017, Darren Hart wrote: > New features also fall into the independent tracking bucket, although > your point about feature masks could reduce that need. Is there a > definitive mechanism for the feature mask approach? I see a lot of > sysfs_filename:value key:value pairs for this kind of thing. Adding those sysfs attributes seems like exactly the thing that people will keep forgetting to do, as there is no (real) functionality depending on them. I doubt there is any better 'description' of the 'state' of the driver than SHA of the topmost commit + the tree it's related to. -- Jiri Kosina SUSE Labs