All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Maurizio Lombardi <mlombard@redhat.com>, Kai.Makisara@kolumbus.fi
Cc: 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: Wed, 19 Feb 2014 10:09:38 +0100	[thread overview]
Message-ID: <530474D2.4050504@suse.de> (raw)
In-Reply-To: <1392800681-5290-1-git-send-email-mlombard@redhat.com>

On 02/19/2014 10:04 AM, Maurizio Lombardi wrote:
> This patch converts the st driver to use dev_printk() instead of printk(),
> every st device has a reference to the underlying scsi device.
> 
> Signed-off-by: Maurizio Lombardi <mlombard@redhat.com>
Thanks for doing this.

I've actually a full patchset queued, converting all the stray
'printk' invocations in the SCSI stack to dev_printk() and friends.
And moving to a per-device scsi_log_level :-)

So far I haven't posted them as I'm still waiting for feedback
from my EVPD patchset.

But I can rebase them on top of that if you want to have a look at them.

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-19  9:09 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 [this message]
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
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=530474D2.4050504@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=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.