From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: "Bryant G. Ly" <bryantly@linux.vnet.ibm.com>
Cc: nab@linux-iscsi.org, martin.petersen@oracle.com,
linux-scsi@vger.kernel.org, target-devel@vger.kernel.org,
Brad Warrum <bwarrum@us.ibm.com>
Subject: Re: [PATCH] ibmvscsis: add DRC indices to debug statements
Date: Mon, 04 Dec 2017 22:32:37 -0500 [thread overview]
Message-ID: <yq14lp54zoq.fsf@oracle.com> (raw)
In-Reply-To: <20171204220728.94613-1-bryantly@linux.vnet.ibm.com> (Bryant G. Ly's message of "Mon, 4 Dec 2017 16:07:28 -0600")
Bryant,
> Where applicable, changes pr_debug, pr_info, pr_err, etc. calls
> to the dev_* versions. This adds the DRC index of the device to the
> corresponding trace statement.
Applied to 4.16/scsi-queue, thank you!
--
Martin K. Petersen Oracle Linux Engineering
WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: "Bryant G. Ly" <bryantly@linux.vnet.ibm.com>
Cc: nab@linux-iscsi.org, martin.petersen@oracle.com,
linux-scsi@vger.kernel.org, target-devel@vger.kernel.org,
Brad Warrum <bwarrum@us.ibm.com>
Subject: Re: [PATCH] ibmvscsis: add DRC indices to debug statements
Date: Tue, 05 Dec 2017 03:32:37 +0000 [thread overview]
Message-ID: <yq14lp54zoq.fsf@oracle.com> (raw)
In-Reply-To: <20171204220728.94613-1-bryantly@linux.vnet.ibm.com> (Bryant G. Ly's message of "Mon, 4 Dec 2017 16:07:28 -0600")
Bryant,
> Where applicable, changes pr_debug, pr_info, pr_err, etc. calls
> to the dev_* versions. This adds the DRC index of the device to the
> corresponding trace statement.
Applied to 4.16/scsi-queue, thank you!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2017-12-05 3:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 22:07 [PATCH] ibmvscsis: add DRC indices to debug statements Bryant G. Ly
2017-12-04 22:07 ` Bryant G. Ly
2017-12-05 3:32 ` Martin K. Petersen [this message]
2017-12-05 3:32 ` Martin K. Petersen
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=yq14lp54zoq.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=bryantly@linux.vnet.ibm.com \
--cc=bwarrum@us.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=target-devel@vger.kernel.org \
/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.