From: "Bhanu Prakash Gollapudi" <bprakash@broadcom.com>
To: linux-scsi@vger.kernel.org, devel@open-fcoe.org
Cc: Nithin Nayak Sujir <nsujir@broadcom.com>,
Bhanu Prakash Gollapudi <bprakash@broadcom.com>
Subject: [PATCH 4/5] bnx2fc: Do not use HBA_DBG macro when lport is not available
Date: Mon, 25 Apr 2011 12:30:09 -0700 [thread overview]
Message-ID: <1303759810-22570-4-git-send-email-bprakash@broadcom.com> (raw)
In-Reply-To: <1303759810-22570-1-git-send-email-bprakash@broadcom.com>
From: Nithin Nayak Sujir <nsujir@broadcom.com>
Use MISC_DBG instead.
Signed-off-by: Nithin Nayak Sujir <nsujir@broadcom.com>
Signed-off-by: Bhanu Prakash Gollapudi <bprakash@broadcom.com>
---
drivers/scsi/bnx2fc/bnx2fc_fcoe.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/scsi/bnx2fc/bnx2fc_fcoe.c b/drivers/scsi/bnx2fc/bnx2fc_fcoe.c
index 734d8c1..8075d65 100644
--- a/drivers/scsi/bnx2fc/bnx2fc_fcoe.c
+++ b/drivers/scsi/bnx2fc/bnx2fc_fcoe.c
@@ -1131,7 +1131,7 @@ static void bnx2fc_interface_release(struct kref *kref)
struct net_device *phys_dev;
hba = container_of(kref, struct bnx2fc_hba, kref);
- BNX2FC_HBA_DBG(hba->ctlr.lp, "Interface is being released\n");
+ BNX2FC_MISC_DBG("Interface is being released\n");
netdev = hba->netdev;
phys_dev = hba->phys_dev;
--
1.7.0.6
next prev parent reply other threads:[~2011-04-25 19:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 19:30 [PATCH 1/5] scsi_transport_fc: Fix deadlock during fc_remove_host Bhanu Prakash Gollapudi
2011-04-25 19:30 ` [PATCH 2/5] bnx2fc: Release the reference to hba only after the interface is destroyed Bhanu Prakash Gollapudi
2011-04-25 22:49 ` Shyam_Iyer
2011-04-25 23:15 ` Bhanu Prakash Gollapudi
2011-04-26 4:09 ` Shyam_Iyer
2011-04-26 4:10 ` Shyam_Iyer
2011-04-25 19:30 ` [PATCH 3/5] bnx2fc: call scsi_done if session goes to not ready from ready Bhanu Prakash Gollapudi
2011-04-25 19:30 ` Bhanu Prakash Gollapudi [this message]
2011-04-25 19:30 ` [PATCH 5/5] bnx2fc: increase cleanup wait time Bhanu Prakash Gollapudi
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=1303759810-22570-4-git-send-email-bprakash@broadcom.com \
--to=bprakash@broadcom.com \
--cc=devel@open-fcoe.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nsujir@broadcom.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