All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: "Martin K. Petersen" <martin.petersen@oracle.com>,
	jbottomley@parallels.com
Cc: Maurizio Lombardi <mlombard@redhat.com>,
	Kai.Makisara@kolumbus.fi, linux-scsi@vger.kernel.org,
	kay@vrfy.org
Subject: Re: [PATCH] st: use dev_printk() to avoid linebreaks in kernel messages.
Date: Fri, 21 Feb 2014 07:46:41 +0100	[thread overview]
Message-ID: <5306F651.6050607@suse.de> (raw)
In-Reply-To: <yq1ob21k2ng.fsf@sermon.lab.mkp.net>

On 02/20/2014 08:25 PM, Martin K. Petersen wrote:
>>>>>> "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?
> 

I'm all for removing it, and move over to SCSI tracing.
But not without general (read: the maintainers) consent.

James?

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2014-02-21  6:46 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
2014-02-21  6:46         ` Hannes Reinecke [this message]
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=5306F651.6050607@suse.de \
    --to=hare@suse.de \
    --cc=Kai.Makisara@kolumbus.fi \
    --cc=jbottomley@parallels.com \
    --cc=kay@vrfy.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --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 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.