From: Joe Perches <joe@perches.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, QLogic-Storage-Upstream@cavium.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] scsi: qedf: Fix defective logging format and argument mismatches
Date: Mon, 06 Mar 2017 10:33:49 -0800 [thread overview]
Message-ID: <1488825229.2210.12.camel@perches.com> (raw)
In-Reply-To: <1488824248.2210.11.camel@perches.com>
On Mon, 2017-03-06 at 10:17 -0800, Joe Perches wrote:
> On Tue, 2017-03-07 at 02:03 +0800, kbuild test robot wrote:
> > Hi Joe,
>
> Hi again Fengguang's robot.
Rehi. OK, it is a new message. Patch sent.
next prev parent reply other threads:[~2017-03-06 18:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-04 8:07 [PATCH] scsi: qedf: Fix defective logging format and argument mismatches Joe Perches
2017-03-06 17:52 ` kbuild test robot
2017-03-06 18:03 ` kbuild test robot
2017-03-06 18:17 ` Joe Perches
2017-03-06 18:33 ` Joe Perches [this message]
2017-03-06 19:33 ` Chad Dupuis
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=1488825229.2210.12.camel@perches.com \
--to=joe@perches.com \
--cc=QLogic-Storage-Upstream@cavium.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lkp@intel.com \
--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