stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Thomas Hellstrom <thellstrom@vmware.com>
Cc: stable@vger.kernel.org
Subject: Re: Stable list vs versioning
Date: Fri, 7 Oct 2016 05:52:36 +0200	[thread overview]
Message-ID: <20161007035236.GA16832@kroah.com> (raw)
In-Reply-To: <b9f14c7d-14a3-29f9-31ed-1e0696eb5829@vmware.com>

On Thu, Oct 06, 2016 at 06:54:43PM -0700, Thomas Hellstrom wrote:
> Hi, Stable!
> 
> As you might be aware of, some companies that maintain linux kernel
> drivers have the habit of assigning each driver change a new version
> number.

And, as you have found out, that's a horrible thing to do for Linux and
doesn't work at all :)

Just because it works for other slower-moving operating systems, I
wouldn't recommend doing it for Linux.

Is there any specific driver out there that we don't have merged into
the kernel tree that could be helped from doing this type of thing?

thanks,

greg k-h

  reply	other threads:[~2016-10-07  4:04 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 [this message]
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
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=20161007035236.GA16832@kroah.com \
    --to=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).