linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Douglas Gilbert <dgilbert@interlog.com>
To: Hannes Reinecke <hare@suse.de>,
	James Bottomley <jbottomley@parallels.com>
Cc: Christoph Hellwig <hch@infradead.org>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 2/6] scsi: Implement sg_printk()
Date: Tue, 03 Jun 2014 09:32:20 -0400	[thread overview]
Message-ID: <538DCE64.3020604@interlog.com> (raw)
In-Reply-To: <1401794577-102277-3-git-send-email-hare@suse.de>

On 14-06-03 07:22 AM, Hannes Reinecke wrote:
> Update the sg driver to use dev_printk() variants instead of
> plain printk(); this will prefix logging messages with the
> appropriate device.
>
> Signed-off-by: Hannes Reinecke <hare@suse.de>
> Cc: Doug Gilbert <dgilbert@interlog.com>

Acked-by: Douglas Gilbert <dgilbert@interlog.com>


  reply	other threads:[~2014-06-03 13:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-03 11:22 [PATCH 0/6] First batch of logging cleanups Hannes Reinecke
2014-06-03 11:22 ` [PATCH 1/6] scsi: Implement sr_printk() Hannes Reinecke
2014-06-03 11:22 ` [PATCH 2/6] scsi: Implement sg_printk() Hannes Reinecke
2014-06-03 13:32   ` Douglas Gilbert [this message]
2014-06-03 11:22 ` [PATCH 3/6] scsi: Implement ch_printk() Hannes Reinecke
2014-06-03 11:22 ` [PATCH 4/6] scsi: Implement st_printk() Hannes Reinecke
2014-06-03 11:22 ` [PATCH 5/6] scsi: use dev_printk() variants for ioctl Hannes Reinecke
2014-06-03 11:22 ` [PATCH 6/6] scsi: use dev_printk variants where possible Hannes Reinecke
2014-10-22 22:29   ` Elliott, Robert (Server Storage)
2014-06-03 22:12 ` [PATCH 0/6] First batch of logging cleanups Martin K. Petersen
2014-06-04  5:50   ` Hannes Reinecke
2014-06-11 12:08 ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2014-06-25 14:39 [PATCHv2 0/6] First batch of logging cleanup Hannes Reinecke
2014-06-25 14:39 ` [PATCH 2/6] scsi: Implement sg_printk() Hannes Reinecke
2014-06-25 20:21   ` Douglas Gilbert
2014-06-26  7:41     ` Christoph Hellwig

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=538DCE64.3020604@interlog.com \
    --to=dgilbert@interlog.com \
    --cc=hare@suse.de \
    --cc=hch@infradead.org \
    --cc=jbottomley@parallels.com \
    --cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).