From: Jiri Kosina <jkosina@suse.cz>
To: Darren Hart <dvhart@infradead.org>
Cc: ksummit-discuss@lists.linux-foundation.org
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Driver and/or module versions
Date: Mon, 3 Jul 2017 22:41:16 +0200 (CEST) [thread overview]
Message-ID: <alpine.LSU.2.20.1707032238300.15036@cbobk.fhfr.pm> (raw)
In-Reply-To: <20170630162155.GB26257@fury>
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
next prev parent reply other threads:[~2017-07-03 20:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-25 7:24 Leon Romanovsky
2017-06-25 17:32 ` Linus Torvalds
2017-06-25 18:19 ` Leon Romanovsky
2017-06-25 18:37 ` Linus Torvalds
2017-06-25 19:05 ` Leon Romanovsky
2017-06-25 21:32 ` Alexandre Belloni
2017-06-26 4:51 ` Leon Romanovsky
2017-06-26 6:47 ` Geert Uytterhoeven
2017-06-26 5:00 ` Greg KH
2017-06-26 6:03 ` Leon Romanovsky
2017-06-26 15:21 ` Levin, Alexander (Sasha Levin)
2017-06-26 18:25 ` Leon Romanovsky
2017-06-30 16:21 ` Darren Hart
2017-07-03 20:41 ` Jiri Kosina [this message]
2017-07-03 21:25 ` Darren Hart
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=alpine.LSU.2.20.1707032238300.15036@cbobk.fhfr.pm \
--to=jkosina@suse.cz \
--cc=dvhart@infradead.org \
--cc=ksummit-discuss@lists.linux-foundation.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