From: Jean Delvare <jdelvare@suse.de>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Wolfram Sang <wsa@the-dreams.de>,
linux-i2c@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] i2c: i801: Fix Failed to allocate irq -2147483648 error
Date: Tue, 28 Nov 2017 14:37:07 +0100 [thread overview]
Message-ID: <20171128143707.257a2fa1@endymion> (raw)
In-Reply-To: <a733c418-9a88-fd40-96b7-40690c757db0@redhat.com>
On Mon, 27 Nov 2017 16:38:50 +0100, Hans de Goede wrote:
> On 27-11-17 11:04, Jean Delvare wrote:
> > Turning a cryptic error message into a meaningful error message isn't
> > necessarily a bad thing.
>
> Given all the effort distros have done with splash-screens to give
> users a nice clean boot experience, we really want dmesg --level=err
> to not print anything unless there is a real problem with either the
> hardware or the kernel,
I completely agree with that, same goal here.
> printing an error message on all Apollo Lake
> systems is really not helpful IMHO.
It wouldn't have to be an error message, it could be a mere notice.
What I'm afraid of is that the missing IRQ is an overlook from the
standard BIOS provided by Intel to integrators, and the error will keep
spreading until BIOS developers are aware of the problem.
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2017-11-28 13:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 11:28 [PATCH] i2c: i801: Fix Failed to allocate irq -2147483648 error Hans de Goede
2017-11-24 13:49 ` Jean Delvare
2017-11-25 13:43 ` Hans de Goede
2017-11-27 10:04 ` Jean Delvare
2017-11-27 15:38 ` Hans de Goede
2017-11-28 13:37 ` Jean Delvare [this message]
2017-11-28 13:42 ` Hans de Goede
2017-11-27 18:11 ` Wolfram Sang
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=20171128143707.257a2fa1@endymion \
--to=jdelvare@suse.de \
--cc=hdegoede@redhat.com \
--cc=linux-i2c@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.