From: Alan Cox <alan@linux.intel.com>
To: jet.chen@intel.com
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Fengguang Wu <fengguang.wu@intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Fwd: Re: [goldfish] genirq: Flags mismatch irq 4. 00000000 (serial) vs. 00000080 (goldfish_pdev_bus)]
Date: Mon, 19 May 2014 14:58:47 +0100 [thread overview]
Message-ID: <1400507927.5510.4.camel@acox1-desk.ger.corp.intel.com> (raw)
In-Reply-To: <1400506648.5510.0.camel@acox1-desk.ger.corp.intel.com>
> > > 0day kernel testing robot got the below dmesg and the first bad commit is
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git staging-next
> > > commit 9b17aeec232a5f0a61ce3952c2e728a0eeddda8b
I don't believe this one is actually a bug. Or rather it's an annoyance
that was already present on the 32bit Goldfish and I don't see a way of
avoiding it.
Goldfish is an Android emulator not a PC, if you build a Goldfish kernel
it won't run on a PC and mixing the setup gives nonsense results.
I don't know of any way to reliably detect we are running on Goldfish.
Given that it's easy enough to fix up a bit so I'll see if I can find
any documented way to detect Goldfish.
Alan
parent reply other threads:[~2014-05-19 13:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1400506648.5510.0.camel@acox1-desk.ger.corp.intel.com>]
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=1400507927.5510.4.camel@acox1-desk.ger.corp.intel.com \
--to=alan@linux.intel.com \
--cc=fengguang.wu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jet.chen@intel.com \
--cc=linux-kernel@vger.kernel.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®