ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Levin, Alexander (Sasha Levin)" <alexander.levin@verizon.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: "ksummit-discuss@lists.linux-foundation.org"
	<ksummit-discuss@lists.linux-foundation.org>
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Driver and/or module versions
Date: Mon, 26 Jun 2017 15:21:10 +0000	[thread overview]
Message-ID: <20170626152115.fs2c7qosncoeu54d@sasha-lappy> (raw)
In-Reply-To: <20170626060332.GA1248@mtr-leonro.local>

On Mon, Jun 26, 2017 at 09:03:32AM +0300, Leon Romanovsky wrote:
>OK, let's start in small scale and limit myself to MODULE_VERSION at this stage.
>https://patchwork.kernel.org/patch/9808651/

Isn't it the case that something like this will actually break the ABI?

I assume that a bunch of different companies have scripts that pull out the module version out of the module and make sure that it's at some value that works with the rest of their tools, right?

I also have to assume that these scripts will horribly break when the value just disappears.

-- 

Thanks,
Sasha

  reply	other threads:[~2017-06-26 15:21 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) [this message]
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=20170626152115.fs2c7qosncoeu54d@sasha-lappy \
    --to=alexander.levin@verizon.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