linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avri Altman <Avri.Altman@wdc.com>
To: Marc Gonzalez <marc.w.gonzalez@free.fr>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Douglas Gilbert <dgilbert@interlog.com>
Cc: Alim Akhtar <alim.akhtar@samsung.com>,
	SCSI <linux-scsi@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: RE: correcting incorrect peripheral device type 0x0
Date: Thu, 4 Apr 2019 13:02:34 +0000	[thread overview]
Message-ID: <SN6PR04MB4925C4CBA85C47CF865C3732FC500@SN6PR04MB4925.namprd04.prod.outlook.com> (raw)
In-Reply-To: <69474538-b097-f672-a263-aefd5958dc90@free.fr>


> 
> > Marc wrote:
> >
> >> scsi 0:0:0:49488: scsi_add_lun: correcting incorrect peripheral device type
> 0x0 for W-LUN 0x            c150hN
> >
> >             ^^^^^ Where do these crazy LUN numbers come from? That
> >             looks like something which needs fixing...
> 
> 	sdev_printk(KERN_WARNING, sdev, "%s: correcting incorrect
> peripheral device type 0x%x for W-LUN 0x%16xhN\n",
> 			__func__, sdev->type, (unsigned int)sdev->lun);
> 
> What does the "hN" suffix stand for? It seems redundant with the "0x"
> prefix...
> (Looks like hN might be "hexadecimal Number")
> 
> 
> scsi 0:0:0:49488 -> 0xc150
> scsi 0:0:0:49476 -> 0xc144
> scsi 0:0:0:49456 -> 0xc130
Those are coming from ufshcd_scsi_add_wlus(), 
In which we call __scsi_add_device()  for each one of the 3 w-luns:
UFS Device - 0x50, Boot - 0x30, RPMB - 0x44.
Everything seems in order.

Thanks,
Avri

      reply	other threads:[~2019-04-04 13:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-02 15:05 correcting incorrect peripheral device type 0x0 Marc Gonzalez
2019-04-02 15:40 ` Avri Altman
2019-04-04  3:34 ` Martin K. Petersen
2019-04-04  4:04   ` Douglas Gilbert
2019-04-04 12:02   ` Marc Gonzalez
2019-04-04 13:02     ` Avri Altman [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=SN6PR04MB4925C4CBA85C47CF865C3732FC500@SN6PR04MB4925.namprd04.prod.outlook.com \
    --to=avri.altman@wdc.com \
    --cc=alim.akhtar@samsung.com \
    --cc=dgilbert@interlog.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=marc.w.gonzalez@free.fr \
    --cc=martin.petersen@oracle.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).