From: Jens Axboe <axboe@kernel.dk>
To: "Matias Bjørling" <mb@lightnvm.io>
Cc: Javier Gonzalez <javier@cnexlabs.com>,
"Konopko, Igor J" <igor.j.konopko@intel.com>,
"marcin.dziegielewski@intel.com" <marcin.dziegielewski@intel.com>,
Hans Holmberg <hans.holmberg@cnexlabs.com>,
Heiner Litz <hlitz@ucsc.edu>,
Young Tack Tack Jin <youngtack.jin@circuitblvd.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] lightnvm: remove minor version check for 2.0
Date: Sun, 5 Aug 2018 08:26:14 -0600 [thread overview]
Message-ID: <e2436194-0de5-df6a-5912-3346d6fca75b@kernel.dk> (raw)
In-Reply-To: <2f1d5972-3257-22e0-efd7-0038f979f438@lightnvm.io>
On 8/5/18 2:29 AM, Matias Bjørling wrote:
> On 8/3/18 2:07 PM, Javier Gonzalez wrote:
>>> On 3 Aug 2018, at 11.02, Matias Bjørling <mb@lightnvm.io> wrote:
>>>
>>> A minor version number increase should not break backwards
>>> compatibility.
>>>
>>> Fixes: 3cb98f84d368b ("lightnvm: add minor version to generic geometry")
>>> Signed-off-by: Matias Bjørling <mb@lightnvm.io>
>>> ---
>>> drivers/nvme/host/lightnvm.c | 6 ------
>>> 1 file changed, 6 deletions(-)
>>>
>>> diff --git a/drivers/nvme/host/lightnvm.c b/drivers/nvme/host/lightnvm.c
>>> index d9e4cccd5b66..a156fe3ca7d3 100644
>>> --- a/drivers/nvme/host/lightnvm.c
>>> +++ b/drivers/nvme/host/lightnvm.c
>>> @@ -414,12 +414,6 @@ static int nvme_nvm_setup_20(struct nvme_nvm_id20 *id,
>>> /* Set compacted version for upper layers */
>>> geo->version = NVM_OCSSD_SPEC_20;
>>>
>>> - if (!(geo->major_ver_id == 2 && geo->minor_ver_id == 0)) {
>>> - pr_err("nvm: OCSSD version not supported (v%d.%d)\n",
>>> - geo->major_ver_id, geo->minor_ver_id);
>>> - return -EINVAL;
>>> - }
>>> -
>>> geo->num_ch = le16_to_cpu(id->num_grp);
>>> geo->num_lun = le16_to_cpu(id->num_pu);
>>> geo->all_luns = geo->num_ch * geo->num_lun;
>>> --
>>> 2.11.0
>>
>> Looks good to me.
>>
>> Reviewed-by: Javier González <javier@cnexlabs.com>
>>
>
> Hi Jens,
>
> Would it be possible to pick this one up for 4.19?
Done.
--
Jens Axboe
prev parent reply other threads:[~2018-08-05 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 9:02 Matias Bjørling
2018-08-03 12:07 ` Javier Gonzalez
2018-08-05 8:29 ` Matias Bjørling
2018-08-05 14:26 ` 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=e2436194-0de5-df6a-5912-3346d6fca75b@kernel.dk \
--to=axboe@kernel.dk \
--cc=hans.holmberg@cnexlabs.com \
--cc=hlitz@ucsc.edu \
--cc=igor.j.konopko@intel.com \
--cc=javier@cnexlabs.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.dziegielewski@intel.com \
--cc=mb@lightnvm.io \
--cc=youngtack.jin@circuitblvd.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
all inboxes | Powered by JetHome®