From: Willy Tarreau <w@1wt.eu>
To: Thomas Hellstrom <thellstrom@vmware.com>
Cc: Greg KH <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Subject: Re: Stable list vs versioning
Date: Sat, 8 Oct 2016 07:57:03 +0200 [thread overview]
Message-ID: <20161008055703.GC11221@1wt.eu> (raw)
In-Reply-To: <86846714-1e66-ff3f-4a27-ca664fc2bff9@vmware.com>
On Fri, Oct 07, 2016 at 10:35:19AM -0700, Thomas Hellstrom wrote:
> So my end goal here is to find a way for the vmware paravirtual in-tree
> kernel modules to stop bumping version numbers on each commit / commit
> series and start pushing important bugfixes to stable, while making
> kernel maintainers happy and company people happy.
Here it's better to simply drop module version at all, because not all
patches will be backported to stable, and the version becomes confusing.
>From time to time when we backport fixes to older kernels, we find a
driver fix refusing to apply because it also updates the version to
something much higher than what we have. It shows how inappropriate
these versions are. Enumerating patches between branches is not hard,
is much more accurate than relying on a version which a single patch
could increase while still missing other important patches.
Willy
next prev parent reply other threads:[~2016-10-08 5:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 1:54 Stable list vs versioning Thomas Hellstrom
2016-10-07 3:52 ` Greg KH
2016-10-07 4:19 ` Thomas Hellstrom
2016-10-07 4:22 ` Greg KH
2016-10-07 4:51 ` Thomas Hellstrom
2016-10-07 12:48 ` Greg KH
2016-10-07 13:47 ` Thomas Hellstrom
2016-10-07 14:18 ` Greg KH
2016-10-07 15:05 ` Thomas Hellstrom
2016-10-07 15:26 ` Greg KH
2016-10-07 15:33 ` Josh Boyer
2016-10-07 15:45 ` Thomas Hellstrom
2016-10-07 17:13 ` Greg KH
2016-10-07 17:35 ` Thomas Hellstrom
2016-10-07 20:39 ` Greg KH
2016-10-08 5:57 ` Willy Tarreau [this message]
2016-10-10 9:30 ` Thomas Hellstrom
2016-10-07 15:13 ` Willy Tarreau
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=20161008055703.GC11221@1wt.eu \
--to=w@1wt.eu \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=thellstrom@vmware.com \
/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 NNTP newsgroup(s).