From: "Javier González" <jg@lightnvm.io>
To: Rakesh Pandit <rakesh@tuxera.com>
Cc: "Matias Bjørling" <mb@lightnvm.io>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/6] lightnvm: pblk: fix message if L2P MAP is in device
Date: Fri, 22 Sep 2017 12:03:14 +0200 [thread overview]
Message-ID: <3E24DF8F-A2D4-493C-AA9F-DC3EFC2E6364@lightnvm.io> (raw)
In-Reply-To: <20170922094417.GB31904@dhcp-216.srv.tuxera.com>
[-- Attachment #1: Type: text/plain, Size: 1677 bytes --]
Sure.
Matias: Can you fix this when picking it up?
Javier
> On 22 Sep 2017, at 11.44, Rakesh Pandit <rakesh@tuxera.com> wrote:
>
> On Fri, Sep 22, 2017 at 10:52:19AM +0200, Javier González wrote:
>>> On 21 Sep 2017, at 13.26, Rakesh Pandit <rakesh@tuxera.com> wrote:
>>>
>>> This usually happens if we are developing with qemu and ll2pmode has
>>> default value. Even in that case message seems wrong.
>>>
>>> Signed-off-by: Rakesh Pandit <rakesh@tuxera.com>
>>> ---
>>> drivers/lightnvm/pblk-init.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/lightnvm/pblk-init.c b/drivers/lightnvm/pblk-init.c
>>> index 470ef04..c5c1337 100644
>>> --- a/drivers/lightnvm/pblk-init.c
>>> +++ b/drivers/lightnvm/pblk-init.c
>>> @@ -913,7 +913,7 @@ static void *pblk_init(struct nvm_tgt_dev *dev, struct gendisk *tdisk,
>>> int ret;
>>>
>>> if (dev->identity.dom & NVM_RSP_L2P) {
>>> - pr_err("pblk: device-side L2P table not supported. (%x)\n",
>>> + pr_err("pblk: device-side L2P table supported. (%x)\n",
>>> dev->identity.dom);
>>> return ERR_PTR(-EINVAL);
>>> }
>>> --
>>> 2.5.0
>>
>> You're right. This is inherited from rrpc.
>>
>> Can we instead write "pblk: full host-side L2P table not supported"?
>> People will not know about the hybrid device/host L2P as time goes by
>> and it will just be confusing. I'm not even sure this will be part of
>> the 2.0 spec, so it will probably go away with time...
>
> Sure. I was confused the first time. This is better.
>
> It would be great if this is done while picking up. I can repost as
> well if need be.
>
> Thanks,
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2017-09-22 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 11:26 [PATCH 3/6] lightnvm: pblk: fix message if L2P MAP is in device Rakesh Pandit
2017-09-22 8:52 ` Javier González
2017-09-22 9:44 ` Rakesh Pandit
2017-09-22 10:03 ` Javier González [this message]
2017-09-25 10:15 ` Matias Bjørling
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=3E24DF8F-A2D4-493C-AA9F-DC3EFC2E6364@lightnvm.io \
--to=jg@lightnvm.io \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@lightnvm.io \
--cc=rakesh@tuxera.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).