From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>,
vagabon.xyz@gmail.com, linux-mips@linux-mips.org
Subject: Re: [PATCH][MIPS] merge a few printk in check_wait()
Date: Thu, 19 Oct 2006 18:48:41 +0100 [thread overview]
Message-ID: <20061019174840.GA5195@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.64N.0610191753180.5982@blysk.ds.pg.gda.pl>
On Thu, Oct 19, 2006 at 05:54:19PM +0100, Maciej W. Rozycki wrote:
>
> > > Or more radical, just getting rid of the printk entirely? It doesn't
> > > provide very useful information.
> [...]
> > I agree with you.
> > I updated my patch.
>
> You might consider removing "Checking for..." in that case as well.
I acutally already have such a patch on the queue tree.
Ralf
next prev parent reply other threads:[~2006-10-19 17:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 15:27 [PATCH][MIPS] merge a few printk in check_wait() Yoichi Yuasa
2006-10-18 16:00 ` Franck Bui-Huu
2006-10-18 16:15 ` Ralf Baechle
2006-10-19 8:07 ` Yoichi Yuasa
2006-10-19 16:54 ` Maciej W. Rozycki
2006-10-19 17:48 ` Ralf Baechle [this message]
2006-10-19 22:10 ` Yoichi Yuasa
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=20061019174840.GA5195@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=vagabon.xyz@gmail.com \
--cc=yoichi_yuasa@tripeaks.co.jp \
/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