From: Yoshihiro YUNOMAE <yoshihiro.yunomae.ez@hitachi.com>
To: hare@suse.de
Cc: mlombard@redhat.com, Kai.Makisara@kolumbus.fi,
linux-scsi@vger.kernel.org, jbottomley@parallels.com,
kay@vrfy.org, martin.petersen@oracle.com,
linux-kernel@vger.kernel.org, hidehiro.kawai.ez@hitachi.com,
yrl.pp-manager.tt@hitachi.com
Subject: Re: [PATCH] st: use dev_printk() to avoid linebreaks in kernel messages.
Date: Fri, 21 Feb 2014 11:48:59 +0900 [thread overview]
Message-ID: <5306BE9B.1010909@hitachi.com> (raw)
In-Reply-To: 53047DA0.4030100@suse.de
Hi Hannes,
We want to handle the error message in userland for HA clusters, so the
error messages should be output in single(atomic) line. However, current
upstream kernel outputs SCSI error messages in multiple lines, so
current implementation is inconvenient. Even if human reads the error
messages, the split messages are difficult to read. Therefore, the
split error messages should be fixed.
In order to solve this problem, recently I submitted the patch fixing
SCSI error message split[1] to LKML. However, when I read the
discussion of you and Maurizio, I noticed that you already have fixed
in your branch.
When will you send your branch to linux-kernel ML or linux-scsi ML?
[1] https://lkml.org/lkml/2014/1/15/926
[2] http://marc.info/?t=139280071900001&r=1&w=2
Thank you,
Yoshihiro YUNOMAE
--
Yoshihiro YUNOMAE
Software Platform Research Dept. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: yoshihiro.yunomae.ez@hitachi.com
next reply other threads:[~2014-02-21 2:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 2:48 Yoshihiro YUNOMAE [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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=5306BE9B.1010909@hitachi.com \
--to=yoshihiro.yunomae.ez@hitachi.com \
--cc=Kai.Makisara@kolumbus.fi \
--cc=hare@suse.de \
--cc=hidehiro.kawai.ez@hitachi.com \
--cc=jbottomley@parallels.com \
--cc=kay@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mlombard@redhat.com \
--cc=yrl.pp-manager.tt@hitachi.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.