From: Arjan van de Ven <arjan@linux.intel.com>
To: Julian Brost <julian.brost@fau.de>,
Andy Lutomirski <luto@kernel.org>,
Jean Delvare <jdelvare@suse.de>,
x86@kernel.org
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Andy Lutomirski <luto@amacapital.net>,
Borislav Petkov <bp@alien8.de>, Brian Gerst <brgerst@gmail.com>,
Denys Vlasenko <dvlasenk@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
"Luis R. Rodriguez" <mcgrof@suse.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Toshi Kani <toshi.kani@hp.com>, Ingo Molnar <mingo@kernel.org>,
problems@cip.cs.fau.de
Subject: Re: [PATCH] x86/dmi: Switch dmi_remap to ioremap_cache
Date: Thu, 9 Mar 2017 09:51:04 -0800 [thread overview]
Message-ID: <382c62c4-5384-4d18-a979-3161f6e2d3a5@linux.intel.com> (raw)
In-Reply-To: <1303553d-2975-daeb-1a3d-303228966c96@fau.de>
On 3/9/2017 9:48 AM, Julian Brost wrote:
> I'm note entirely sure whether it's actually the kernel or HP to blame,
> but for now, hp-health is completely broken on 4.9 (probably on
> everything starting from 4.6), so this patch should be reviewed again.
it looks like another kernel driver is doing a conflicting mapping.
do these HP tools come with their own kernel drivers or are those in the
upstream kernel nowadays?
next prev parent reply other threads:[~2017-03-09 17:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 7:06 Andy Lutomirski
2016-02-09 16:08 ` [tip:x86/mm] x86/dmi: Switch dmi_remap() from ioremap() [uncached ] to ioremap_cache() tip-bot for Andy Lutomirski
2017-03-09 17:48 ` [PATCH] x86/dmi: Switch dmi_remap to ioremap_cache Julian Brost
2017-03-09 17:51 ` Arjan van de Ven [this message]
2017-03-09 18:03 ` Julian Brost
2017-03-09 18:14 ` Andy Lutomirski
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=382c62c4-5384-4d18-a979-3161f6e2d3a5@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=hpa@zytor.com \
--cc=jdelvare@suse.de \
--cc=julian.brost@fau.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=mcgrof@suse.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=problems@cip.cs.fau.de \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=toshi.kani@hp.com \
--cc=x86@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
Powered by JetHome