From: Joe Perches <joe@perches.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
jayamohan.kallickal@avagotech.com, jejb@linux.vnet.ibm.com,
ketan.mukadam@avagotech.com, sony.john@avagotech.com,
martin.petersen@oracle.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 2/2 v3] be2iscsi: Fix some error messages
Date: Sat, 13 Aug 2016 16:41:38 +0000 [thread overview]
Message-ID: <1471106498.3467.19.camel@perches.com> (raw)
In-Reply-To: <fdffed8e-d269-6519-437e-6f731dbb9c05@wanadoo.fr>
On Sat, 2016-08-13 at 14:31 +0200, Christophe JAILLET wrote:
> Le 13/08/2016 à 13:35, Joe Perches a écrit :
> > > @@ -268,7 +268,7 @@ static int beiscsi_eh_abort(struct scsi_cmnd *sc)
> > > &nonemb_cmd.dma);
> > > if (nonemb_cmd.va = NULL) {
> > > beiscsi_log(phba, KERN_ERR, BEISCSI_LOG_EH,
> > > - "BM_%d : Failed to allocate memory for"
> > > + "BM_%d : Failed to allocate memory for "
> > > "mgmt_invalidate_icds\n");
> > doesn't match commit log as no coalescing/concatenation
> > is done.
> >
> > There are many of these.
> >
> I have *only* fixed the one reported by checkpatch and left the others
> unchanged.
>
> My initial proposal was to fix incorrect strings, without modifying too
> much the code. So I decided to do the minimum of changes.
>
> Should I resubmitted with:
> - all strings *in the patch* concatenated?
> - all strings *in the file*" concatenated?
Hello Christophe
You don't _have_ to do anything.
I think the commit message is misleading.
You could submit another patch that does
the equivalent of:
$ ./scripts/checkpatch.pl --types=SPLIT_STRING --fix-inplace drivers/scsi/be2iscsi/be_main.c
with the appropriate commit message
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
jayamohan.kallickal@avagotech.com, jejb@linux.vnet.ibm.com,
ketan.mukadam@avagotech.com, sony.john@avagotech.com,
martin.petersen@oracle.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 2/2 v3] be2iscsi: Fix some error messages
Date: Sat, 13 Aug 2016 09:41:38 -0700 [thread overview]
Message-ID: <1471106498.3467.19.camel@perches.com> (raw)
In-Reply-To: <fdffed8e-d269-6519-437e-6f731dbb9c05@wanadoo.fr>
On Sat, 2016-08-13 at 14:31 +0200, Christophe JAILLET wrote:
> Le 13/08/2016 à 13:35, Joe Perches a écrit :
> > > @@ -268,7 +268,7 @@ static int beiscsi_eh_abort(struct scsi_cmnd *sc)
> > > &nonemb_cmd.dma);
> > > if (nonemb_cmd.va == NULL) {
> > > beiscsi_log(phba, KERN_ERR, BEISCSI_LOG_EH,
> > > - "BM_%d : Failed to allocate memory for"
> > > + "BM_%d : Failed to allocate memory for "
> > > "mgmt_invalidate_icds\n");
> > doesn't match commit log as no coalescing/concatenation
> > is done.
> >
> > There are many of these.
> >
> I have *only* fixed the one reported by checkpatch and left the others
> unchanged.
>
> My initial proposal was to fix incorrect strings, without modifying too
> much the code. So I decided to do the minimum of changes.
>
> Should I resubmitted with:
> - all strings *in the patch* concatenated?
> - all strings *in the file*" concatenated?
Hello Christophe
You don't _have_ to do anything.
I think the commit message is misleading.
You could submit another patch that does
the equivalent of:
$ ./scripts/checkpatch.pl --types=SPLIT_STRING --fix-inplace drivers/scsi/be2iscsi/be_main.c
with the appropriate commit message
next prev parent reply other threads:[~2016-08-13 16:41 UTC|newest]
Thread overview: 34+ 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:02 ` Christophe JAILLET
2016-08-12 10:30 ` Julia Lawall
2016-08-12 10:30 ` Julia Lawall
2016-08-12 20:30 ` Christophe JAILLET
2016-08-12 20:30 ` Christophe JAILLET
2016-08-13 7:08 ` [PATCH 2/2 v2] " Christophe JAILLET
2016-08-13 7:08 ` Christophe JAILLET
2016-08-13 7:14 ` Julia Lawall
2016-08-13 7:14 ` Julia Lawall
2016-08-13 7:20 ` [PATCH 2/2 v3] " Christophe JAILLET
2016-08-13 7:20 ` Christophe JAILLET
2016-08-13 11:35 ` Joe Perches
2016-08-13 11:35 ` Joe Perches
2016-08-13 12:31 ` Christophe JAILLET
2016-08-13 12:31 ` Christophe JAILLET
2016-08-13 16:41 ` Joe Perches [this message]
2016-08-13 16:41 ` Joe Perches
2016-08-13 17:03 ` 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
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=1471106498.3467.19.camel@perches.com \
--to=joe@perches.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=jayamohan.kallickal@avagotech.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=ketan.mukadam@avagotech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sony.john@avagotech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.