From: Greg KH <gregkh@linuxfoundation.org>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: stable@vger.kernel.org, openipmi-developer@lists.sourceforge.net,
LKML <linux-kernel@vger.kernel.org>,
it+lkml@molgen.mpg.de
Subject: Re: [PATCH v2] ipmi:pci: Blacklist a Realtek "IPMI" device
Date: Thu, 24 Jan 2019 18:53:31 +0100 [thread overview]
Message-ID: <20190124175331.GC7484@kroah.com> (raw)
In-Reply-To: <cc8b4831-73bf-5f18-ebaa-e0fa6c3d5366@molgen.mpg.de>
On Wed, Jan 23, 2019 at 05:44:57PM +0100, Paul Menzel wrote:
> From: Corey Minyard <cminyard@mvista.com>
> Date: Thu, 15 Feb 2018 16:58:26 -0600
>
> [ upstream commit bc48fa1b9d3b04106055b27078da824cd209865a ]
>
> Realtek has some sort of "Virtual" IPMI device on the PCI bus as a
> KCS controller, but whatever it is, it's not one. Ignore it if seen.
>
> Reported-by: Chris Chiu <chiu@endlessm.com>
> Signed-off-by: Corey Minyard <cminyard@mvista.com>
> Tested-by: Daniel Drake <drake@endlessm.com>
>
> [ Commit 13d0b35c (ipmi_si: Move PCI setup to another file) from Linux
> 4.15-rc1 has not been back ported, so the PCI code is still in
> `drivers/char/ipmi/ipmi_si_intf.c`, requiring to apply the commit
> manually.
>
> This fixes a 100 s boot delay on the HP EliteDesk 705 G4 MT with Linux
> 4.14.94. ]
>
> Signed-off-by: Paul Menzel <pmenzel@molgen.mpg.de>
> ---
>
> v2: Use tabs. Sorry for messing that up.
That worked, thanks.
greg k-h
prev parent reply other threads:[~2019-01-24 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 16:17 ipmi_si: 90 s delay in system start with 4.14.94, but not 4.18.6 Paul Menzel
2019-01-22 20:58 ` Corey Minyard
2019-01-23 16:25 ` Paul Menzel
2019-01-23 16:27 ` [PATCH] ipmi:pci: Blacklist a Realtek "IPMI" device Paul Menzel
2019-01-23 16:32 ` Greg KH
2019-01-23 16:44 ` [PATCH v2] " Paul Menzel
2019-01-24 17:53 ` Greg KH [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=20190124175331.GC7484@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=it+lkml@molgen.mpg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=pmenzel@molgen.mpg.de \
--cc=stable@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
Powered by JetHome