From: Vasiliy Kulikov <segooon@gmail.com>
To: Chris Metcalf <cmetcalf@tilera.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Paul Mundt <lethal@linux-sh.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] char: hvc: check for error case
Date: Mon, 13 Sep 2010 17:32:08 +0400 [thread overview]
Message-ID: <20100913133208.GA11032@albatros> (raw)
In-Reply-To: <4C8E2355.60807@tilera.com>
On Mon, Sep 13, 2010 at 09:12 -0400, Chris Metcalf wrote:
> Thanks, accepted into my tree (for the next merge window). In practice all
> this means is in debug mode we'll get a warning from do_one_initcall()
> rather than silence, but you're right, it's technically better. :-)
Anyway it's better, if user sees warning in the dmesg, he/she might
response to this situation.
Best,
--
Vasiliy
prev parent reply other threads:[~2010-09-13 13:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-12 18:57 [PATCH] char: hvc: check for error case Vasiliy Kulikov
2010-09-13 13:12 ` Chris Metcalf
2010-09-13 13:32 ` Vasiliy Kulikov [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=20100913133208.GA11032@albatros \
--to=segooon@gmail.com \
--cc=arnd@arndb.de \
--cc=cmetcalf@tilera.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=kernel-janitors@vger.kernel.org \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).