ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: ksummit-discuss@lists.linux-foundation.org
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Driver and/or module versions
Date: Mon, 26 Jun 2017 07:00:52 +0200	[thread overview]
Message-ID: <20170626050052.GE17296@kroah.com> (raw)
In-Reply-To: <20170625190529.GV1248@mtr-leonro.local>

On Sun, Jun 25, 2017 at 10:05:29PM +0300, Leon Romanovsky wrote:
> On Sun, Jun 25, 2017 at 11:37:12AM -0700, Linus Torvalds wrote:
> > On Sun, Jun 25, 2017 at 11:19 AM, Leon Romanovsky <leon@kernel.org> wrote:
> > >
> > > Great, so why are we continuing to allow patches with MODULE_VERSION and
> > > DRIVER_VERSION changes?
> >
> > I suspect they just haven't caused problems elsewhere.
> >
> > And honestly, they aren't that common. Grepping for MODULE_VERSION and
> > DRIVER_VERSION shows more than I would like, but we're talking
> > hundreds, not thousands (and lots of them are basically dead, stale
> > code - ATA etc, or just joke names - usb).
> 
> I see it differently, from my point of view, it is pretty active,
> especially in the subsystems where new drivers are added more often,

It takes a few years for companies to realize that the version numbers
mean nothing.  So give it time, it will slow down.  Or you can just
delete all of them at once, making it easier for you in the end.

thanks,

greg k-h

  parent reply	other threads:[~2017-06-26  5:00 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 [this message]
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=20170626050052.GE17296@kroah.com \
    --to=greg@kroah.com \
    --cc=ksummit-discuss@lists.linux-foundation.org \
    --cc=leon@kernel.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