From: Joe Perches <joe@perches.com>
To: Jitendra Bhivare <jitendra.bhivare@broadcom.com>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Jayamohan Kallickal <jayamohan.kallickal@avagotech.com>,
Ketan Mukadam <ketan.mukadam@avagotech.com>
Cc: Bart Van Assche <Bart.VanAssche@sandisk.com>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] be2iscsi: Use a more current logging style
Date: Tue, 16 Aug 2016 20:59:24 -0700 [thread overview]
Message-ID: <1471406364.4075.200.camel@perches.com> (raw)
In-Reply-To: <6716f28ca4aa8580e87f6ca68ba5199e@mail.gmail.com>
On Wed, 2016-08-17 at 09:20 +0530, Jitendra Bhivare wrote:
> >
> > -----Original Message-----
> > From: Joe Perches [mailto:joe@perches.com]
> > Sent: Tuesday, August 16, 2016 3:57 PM
> > To: Jitendra Bhivare; Christophe JAILLET; Jayamohan Kallickal; Ketan
> Mukadam
> >
> > Cc: Bart Van Assche; James E.J. Bottomley; Martin K. Petersen; linux-
> > scsi@vger.kernel.org; linux-kernel@vger.kernel.org
> > Subject: Re: [PATCH] be2iscsi: Use a more current logging style
> >
> > On Tue, 2016-08-16 at 11:32 +0530, Jitendra Bhivare wrote:
> > >
> > > Thanks Joe for taking this up. It has been pending for long time from
> > > our side.
> > Thanks, not a problem, it took ~10 minutes.
> >
> > There was a bit of an issue about your reply though.
> >
> > First there was ~50 k of quoted stuff without any content
> >
> > >
> > > [ hundreds and hundreds of quoted lines ]
> > and then this happened:
> >
> > >
> > > >
> > > > diff --git a/drivers/scsi/be2iscsi/be_main.h
> > > b/drivers/scsi/be2iscsi/be_main.h
> > > >
> > > >
> > > > index aa9c682..7cce6e3 100644
> > > > --- a/drivers/scsi/be2iscsi/be_main.h
> > > > +++ b/drivers/scsi/be2iscsi/be_main.h
> > > > @@ -1081,15 +1081,19 @@ struct hwi_context_memory {
> > > > #define BEISCSI_LOG_CONFIG 0x0020 /* CONFIG Code Path */
> > > > #define BEISCSI_LOG_ISCSI 0x0040 /* SCSI/iSCSI Protocol
> related
> >
> > >
> > > Logs */
> > > >
> > > >
> > > >
> > > > -#define __beiscsi_log(phba, level, fmt, ...)
> \
> >
> > >
> > > >
> > > > - shost_printk(level, phba->shost, fmt, ##__VA_ARGS__)
> > > > -
> > > > -#define beiscsi_log(phba, level, mask, prefix, fmt, ...) \
> > > > +#define beiscsi_printk(level, phba, mask, fmt, ...)
> \
> >
> > >
> > > >
> > > > do {
> > \
> > >
> > > >
> > > > - uint32_t log_value = phba->attr_log_enable; \
> > > > - if (((mask) & log_value) || (level[1] <= '3')) \
> > > > - __beiscsi_log(phba, level, prefix "_%d: " fmt, \
> > > > - __LINE__, ##__VA_ARGS__); \
> > > > + if ((mask) & (phba)->attr_log_enable) \
> > > > + shost_printk(level, phba->shost, \
> > > [JB] PCI dev_printk would be more useful with SCSI host_no included by
> > > default in the message.
> > This is a good note that seems simple enough, but I almost missed this.
> >
> > Given the reply at the top and the _very_ long uncommented quoted block,
> I just
> >
> > about assumed it was a useless block quote that you didn't bother to
> trim.
> >
> >
> > Please make it easier to find your replies and notes by deleting
> irrelevant quoted
> >
> > stuff.
> >
> > Also, I think I misread the code.
> >
> > The original code is <= '3' i.e.: show all KERN_ERR.
> > That is not correct in the new code.
> >
> > I don't know the code well and don't have a test bed with the hardware.
> >
> > Is it possible for a beiscsi_ message to be called before
> phba->pcidev is
> >
> > set to a valid value in beiscsi_hba_alloc? It appears the code is
> careful to only
> >
> > use dev_ logging calls before probe.
> [JB] KERN_ERR messages need to be logged irrespective of the masks.
> I understand, that in some places, mask is unnecessarily passed.
> I had made sure to call __beiscsi_log in some places.
I did as well.
> Can we please keep it that way? So beiscsi_err calls dev_err directly or
> is replaced with dev_err.
No worries, I'll respin the series after Christophe's
patches are applied.
> It's safe to assume pcidev will be valid for all beiscsi_log calls.
> Will test your change on my setup before ack'ing.
Don't bother until you get another patchset.
I suggest you fix your email client when sending
replies to me and to lkml.
What I received is very difficult to read due to
the odd line wrapping.
prev parent reply other threads:[~2016-08-17 3:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 10:02 [PATCH 2/2] be2iscsi: Fix some error messages Christophe JAILLET
2016-08-12 10:30 ` Julia Lawall
2016-08-12 20:30 ` Christophe JAILLET
2016-08-13 7:08 ` [PATCH 2/2 v2] " Christophe JAILLET
2016-08-13 7:14 ` Julia Lawall
2016-08-13 7:20 ` [PATCH 2/2 v3] " Christophe JAILLET
2016-08-13 11:35 ` Joe Perches
2016-08-13 12:31 ` Christophe JAILLET
2016-08-13 16:41 ` Joe Perches
2016-08-13 17:03 ` Joe Perches
2016-08-13 20:42 ` [PATCH 0/2] be2iscsi: Logging neatening Joe Perches
2016-08-13 20:42 ` [PATCH 1/2] be2iscsi: Coalesce split strings and formats Joe Perches
2016-08-13 20:42 ` [PATCH 2/2] be2iscsi: Use a standard logging style Joe Perches
2016-08-14 14:34 ` [PATCH 0/2] be2iscsi: Logging neatening Bart Van Assche
2016-08-14 16:24 ` Joe Perches
2016-08-14 17:09 ` Bart Van Assche
2016-08-14 17:29 ` Joe Perches
2016-08-17 1:19 ` Bart Van Assche
2016-08-17 3:39 ` Joe Perches
2016-08-14 18:55 ` [PATCH] be2iscsi: Use a more current logging style Joe Perches
2016-08-16 6:02 ` Jitendra Bhivare
2016-08-16 10:27 ` Joe Perches
2016-08-17 3:50 ` Jitendra Bhivare
2016-08-17 3:59 ` Joe Perches [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=1471406364.4075.200.camel@perches.com \
--to=joe@perches.com \
--cc=Bart.VanAssche@sandisk.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=jayamohan.kallickal@avagotech.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=jitendra.bhivare@broadcom.com \
--cc=ketan.mukadam@avagotech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--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