On Fri, Sep 19, 2014 at 08:26:29AM +0200, Hannes Reinecke wrote:
I would rather use 'scmd-tag', as this should be a straight copy
of scmd-request-tag, but we wouldn't need to reference the request
when doing so.
Yes, for now scmd-tag is correct as drivers might not be using the
block level
On 09/19/2014 01:35 PM, Christoph Hellwig wrote:
On Fri, Sep 19, 2014 at 08:26:29AM +0200, Hannes Reinecke wrote:
I would rather use 'scmd-tag', as this should be a straight copy
of scmd-request-tag, but we wouldn't need to reference the request
when doing so.
Yes, for now scmd-tag is correct
-Original Message-
From: Christoph Hellwig [mailto:h...@infradead.org]
...
scmd ties the messages together so you can tell which command
has gotten to which state. grep works.
Can we just print the tag instead, that would be a much more human
readable number normally.
I made
On Mon, Sep 01, 2014 at 01:00:26AM +, Elliott, Robert (Server Storage)
wrote:
-Original Message-
From: linux-scsi-ow...@vger.kernel.org [mailto:linux-scsi-
ow...@vger.kernel.org] On Behalf Of Christoph Hellwig
Sent: Sunday, 31 August, 2014 5:26 PM
...
On Thu, Aug 28, 2014
On Thu, Aug 28, 2014 at 07:33:34PM +0200, Hannes Reinecke wrote:
Always use 'scmd 0x%p' when logging a command pointer.
Is there any good reason to print the address of a command pointer?
--
To unsubscribe from this list: send the line unsubscribe linux-scsi in
the body of a message to
-Original Message-
From: linux-scsi-ow...@vger.kernel.org [mailto:linux-scsi-
ow...@vger.kernel.org] On Behalf Of Christoph Hellwig
Sent: Sunday, 31 August, 2014 5:26 PM
...
On Thu, Aug 28, 2014 at 07:33:34PM +0200, Hannes Reinecke wrote:
Always use 'scmd 0x%p' when logging a
Always use 'scmd 0x%p' when logging a command pointer.
Suggested-by: Robert Elliot ell...@hp.com
Signed-off-by: Hannes Reinecke h...@suse.de
---
drivers/scsi/scsi.c | 7 +++---
drivers/scsi/scsi_error.c | 58 +++
drivers/scsi/scsi_lib.c | 2
7 matches
Mail list logo
