From: Leon Romanovsky <leon@kernel.org>
To: ksummit-discuss@lists.linux-foundation.org
Subject: [Ksummit-discuss] [MAINTAINERS SUMMIT] Driver and/or module versions
Date: Sun, 25 Jun 2017 10:24:23 +0300 [thread overview]
Message-ID: <20170625072423.GR1248@mtr-leonro.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 790 bytes --]
There is a steady flow of patches which bump driver and module versions.
The differences in views add [1] an email burden, which can be easily avoided
by adding policy into CodingStyle guide.
As an example of such patches: "Succeeded" [2] vs. "Failed" [3].
I think that maintainers summit with major code "pushers" is the right venue
to get the answers on the following questions:
* Can we come with unified policy about those patches?
* Can we remove them? If yes, is it possible to replace MODULE_VERSION in all patches to point to kernel version?
* Does such change fail under category "UAPI changes and we can't change" or not?
Thanks
[1] https://patchwork.kernel.org/patch/9735855/
[2] https://patchwork.ozlabs.org/patch/779864/
[3] https://patchwork.kernel.org/patch/7490321/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2017-06-25 7:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-25 7:24 Leon Romanovsky [this message]
2017-06-25 17:32 ` [Ksummit-discuss] [MAINTAINERS SUMMIT] Driver and/or module versions 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
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=20170625072423.GR1248@mtr-leonro.local \
--to=leon@kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).