linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Thumshirn <jthumshirn@suse.de>
To: James Smart <jsmart2021@gmail.com>
Cc: linux-nvme@lists.infradead.org, sagi@grimberg.me,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH 03/17] lpfc: NVME Initiator: Base modifications Part B
Date: Wed, 18 Jan 2017 11:11:12 +0100	[thread overview]
Message-ID: <20170118101112.GC3514@linux-x5ow.site> (raw)
In-Reply-To: <587ec2ee.01djIfQsSlhQj6k1%jsmart2021@gmail.com>

On Tue, Jan 17, 2017 at 05:20:46PM -0800, James Smart wrote:
> 
> NVME Initiator: Base modifications
> 
> This is part B of parts A..F.
> 
> Part B is limited to lpfc_attr.c: lpfc attribute modifications
> 
> *********
> 
> Refer to Part A for a description of base modifications
> 
> Signed-off-by: Dick Kennedy <dick.kennedy@broadcom.com>
> Signed-off-by: James Smart <james.smart@broadcom.com>
> ---

[...]

> +	len += snprintf(buf + len, PAGE_SIZE - len,
> +			"%s%d WWPN x%llx WWNN x%llx DID x%06x %s\n",
> +			"NVME LPORT lpfc",

Is it the lack of coffee or should it be 
			"NVME LPORT lpfc%d WWPN x%llx WWNN x%llx DID x%06x %s\n"

I think you're doing it to not hit the 80 chars limit, but then there are
way more offenders than that one, so...


> +			phba->brd_no,
> +			wwn_to_u64(vport->fc_portname.u.wwn),
> +			wwn_to_u64(vport->fc_nodename.u.wwn),
> +			localport->port_id, statep);

[...]

> +int
> +lpfc_emptyq_wait(struct lpfc_hba *phba, struct list_head *q, spinlock_t *lock)
> +{
> +	int cnt = 0;
> +
> +	spin_lock_irq(lock);
> +	while (!list_empty(q)) {
> +		spin_unlock_irq(lock);
> +		msleep(20);
> +		if (cnt++ > 250) {  /* 5 secs */
> +			lpfc_printf_log(phba, KERN_WARNING, LOG_INIT,
> +					"0466 %s %s\n",
> +					"Outstanding IO when ",
> +					"bringing Adapter offline\n");
> +				return 0;
> +		}
> +		spin_lock_irq(lock);
> +	}
> +	spin_unlock_irq(lock);
> +	return 1;
> +}
> +

Aren't you using lpc_emptyq_wait() in patches prior to that already? This
breaks git bisect. Pleas test-build (ideally + checkpatch and sparse/smatch)
each patch in the series individually.

[...]

Thanks,
	Johannes
-- 
Johannes Thumshirn                                          Storage
jthumshirn@suse.de                                +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850

  parent reply	other threads:[~2017-01-18 10:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-18  1:20 [PATCH 03/17] lpfc: NVME Initiator: Base modifications Part B James Smart
2017-01-18  7:08 ` Hannes Reinecke
2017-01-18 10:11 ` Johannes Thumshirn [this message]
2017-01-19  2:45   ` James Smart
2017-01-19  8:08     ` Johannes Thumshirn

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=20170118101112.GC3514@linux-x5ow.site \
    --to=jthumshirn@suse.de \
    --cc=jsmart2021@gmail.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sagi@grimberg.me \
    /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).