Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: axboe@kernel.dk (Jens Axboe)
Subject: [PATCH] NVMe: Update module version major number
Date: Fri, 21 Nov 2014 18:23:36 -0700	[thread overview]
Message-ID: <546FE598.80704@kernel.dk> (raw)
In-Reply-To: <1416608192-15924-1-git-send-email-keith.busch@intel.com>

On 11/21/2014 03:16 PM, Keith Busch wrote:
> It's already near impossible to tell what bits someone is running based on
> a 'modinfo nvme', and I don't want to try guessing if someone is running
> blk-mq or bio-based. Let's make it obvious with the module version that
> the blk-mq conversion is a major change. Future bio-based versions can
> increment to 0.10 in a fork if revisions occur.

Thanks, added to the mix. In general I don't put much faith into version 
numbers, you should be able to tell when people report what kernel they 
are running. Distro backports sometimes make that difficult, though.

-- 
Jens Axboe

      reply	other threads:[~2014-11-22  1:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21 22:16 [PATCH] NVMe: Update module version major number Keith Busch
2014-11-22  1:23 ` Jens Axboe [this message]

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=546FE598.80704@kernel.dk \
    --to=axboe@kernel.dk \
    /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