public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Hannes Reinecke <hare@suse.de>
Cc: Maurizio Lombardi <mlombard@redhat.com>,
	Kai.Makisara@kolumbus.fi, linux-scsi@vger.kernel.org,
	jbottomley@parallels.com, kay@vrfy.org
Subject: Re: [PATCH] st: use dev_printk() to avoid linebreaks in kernel messages.
Date: Thu, 20 Feb 2014 14:25:07 -0500	[thread overview]
Message-ID: <yq1ob21k2ng.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <53047DA0.4030100@suse.de> (Hannes Reinecke's message of "Wed, 19 Feb 2014 10:47:12 +0100")

>>>>> "Hannes" == Hannes Reinecke <hare@suse.de> writes:

Hannes,

>> If you have a more complete and up-to-date patchset in your queue it
>> would be interesting to have a look at it.
>> 
Hannes> You can find the current development branch at

Hannes> git.kernel.org:/pub/scm/linux/kernel/git/hare/scsi-devel branch
Hannes> scsi-logging.v3

I like the printk cleanups and the more sensible sense printing. But why
perpetuate the crufty old SCSI logging stuff when we have SCSI tracing?

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2014-02-20 19:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19  9:04 [PATCH] st: use dev_printk() to avoid linebreaks in kernel messages Maurizio Lombardi
2014-02-19  9:09 ` Hannes Reinecke
2014-02-19  9:23   ` Maurizio Lombardi
2014-02-19  9:47     ` Hannes Reinecke
2014-02-20 19:25       ` Martin K. Petersen [this message]
2014-02-21  6:46         ` Hannes Reinecke
  -- strict thread matches above, loose matches on Subject: below --
2014-02-21  2:48 Yoshihiro YUNOMAE

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=yq1ob21k2ng.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=Kai.Makisara@kolumbus.fi \
    --cc=hare@suse.de \
    --cc=jbottomley@parallels.com \
    --cc=kay@vrfy.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mlombard@redhat.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