From: Greg KH <gregkh@linuxfoundation.org>
To: "Li, Zhenhua" <lizhenhuajiyang@163.com>
Cc: "jslaby@suse.com" <jslaby@suse.com>,
"mingo@kernel.org" <mingo@kernel.org>,
"andriy.shevchenko@linux.intel.com"
<andriy.shevchenko@linux.intel.com>,
"mail@maciej.szmigiero.name" <mail@maciej.szmigiero.name>,
"mgorman@suse.de" <mgorman@suse.de>,
"safinaskar@mail.ru" <safinaskar@mail.ru>,
"mhocko@suse.com" <mhocko@suse.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] drivers/tty: check for null pointer
Date: Wed, 6 Sep 2017 16:18:55 +0200 [thread overview]
Message-ID: <20170906141855.GA17134@kroah.com> (raw)
In-Reply-To: <151d3a06.73a0.15e577b217f.Coremail.lizhenhuajiyang@163.com>
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Wed, Sep 06, 2017 at 09:57:20PM +0800, Li, Zhenhua wrote:
> when I tried to boot linux on a system with virtual bios and vortual keyboard,
> it crashes.
What exact "virtual bios and keyboard" are you referring to here? QEMU?
Something else?
> The root cause is the bios does not initialize devices correctly.
How does the bios come into play here? It should not matter, it should
only be a kernel driver that can set this value.
> did not track what drivers called this function.
What was the full oops message? That should show the problem.
And by just rejecting the call here, you are probably just postponing
the real fix from happening, we should resolve that.
thanks,
greg k-h
next prev parent reply other threads:[~2017-09-06 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 13:38 [PATCH 1/1] drivers/tty: check for null pointer Zhenhua
2017-09-06 13:47 ` Greg KH
[not found] ` <151d3a06.73a0.15e577b217f.Coremail.lizhenhuajiyang@163.com>
2017-09-06 14:18 ` Greg KH [this message]
2017-10-04 8:20 ` Greg KH
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=20170906141855.GA17134@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhenhuajiyang@163.com \
--cc=mail@maciej.szmigiero.name \
--cc=mgorman@suse.de \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=safinaskar@mail.ru \
/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