From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Nick Warne <nick@ukfsn.org>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] Fixup KERN_INFO in tmscsim.c
Date: Fri, 15 Aug 2008 22:17:57 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0808152202440.7852@axis700.grange> (raw)
In-Reply-To: <20080815121045.48ca37e4@sauron.linicks.net>
On Fri, 15 Aug 2008, Nick Warne wrote:
> Setting up my new AMD64 I noticed a curious one liner in syslogs:
Wow, are you sure you need the tmscsim driver on your new amd64 system?:-)
> ^Iwith "disable_clustering=1" and report to maintainers
The message priority is indeed missing in the second line, but it has
nothing to do with the "^I" in your log. I do not know why your syslogd /
klogd converts a TAB to "^I". But if it is a problem, I think, the correct
fix would be something like
- printk(KERN_INFO "DC390: clustering now enabled by default. If you get problems load\n"
- "\twith \"disable_clustering=1\" and report to maintainers\n");
+ printk(KERN_INFO "DC390: clustering now enabled by default. If you get problems load\n");
+ printk(KERN_INFO " with \"disable_clustering=1\" and report to maintainers\n");
Or maybe just remove that printk altogether - it has been there for almost
2 years now, and I haven't heard a single complaint, but on the other
hand, maybe you are the first, who at least loaded this driver since 2
years:-)
Ok, taking into account that this driver is hardly used, I would keep this
warning in case someone does get a problem.
So, please, redo as above, create with "-p1" format, fix your Sob line
> Signed off by: "Nick Warne" <nick@ukfsn.org>
which has to be
Signed-off-by: Nick Warne <nick@ukfsn.org>
and send the patch inline,
Thanks
Guennadi
---
Guennadi Liakhovetski
next prev parent reply other threads:[~2008-08-15 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 11:10 Nick Warne
2008-08-15 20:17 ` Guennadi Liakhovetski [this message]
2008-08-16 8:06 ` Nick Warne
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=Pine.LNX.4.64.0808152202440.7852@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nick@ukfsn.org \
/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
all inboxes | Powered by JetHome®