From: Michael Tokarev <mjt@tls.msk.ru>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: spurious dots in dmesg when reconstructing arrays
Date: Thu, 17 Aug 2006 16:15:13 +0400 [thread overview]
Message-ID: <44E45DD1.4080608@tls.msk.ru> (raw)
In-Reply-To: <17636.22183.827402.227427@cse.unsw.edu.au>
Neil Brown wrote:
> On Thursday August 17, mjt@tls.msk.ru wrote:
>> A long time ago I noticied pretty bad formatting of
>> dmesg text in md array reconstruction output, but
>> never bothered to ask. So here it goes.
>
> What kernel version?
> My patch logs suggest that I fixed that about 1 year ago...
> which means it is still in SLES9 at least :-)
Okay, er, me bad. I was looking at the 2.6.17 source trying
to find that dot, but the kernel from which the messages are
is 2.6.11-based, which is indeed more than a year old. Sure
I can't find where that dot is coming from in 2.6.17! ;)
Oh well.
Thank you, and sorry for the noise.
/mjt
prev parent reply other threads:[~2006-08-17 12:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-17 10:41 spurious dots in dmesg when reconstructing arrays Michael Tokarev
2006-08-17 11:44 ` Neil Brown
2006-08-17 12:15 ` Michael Tokarev [this message]
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=44E45DD1.4080608@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).