From: "Michał Pecio" <michal.pecio-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: <Mario_Limonciello-DYMqY+WieiM@public.gmane.org>
Cc: <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>,
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
<netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
<linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
<anthony.wong-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
Subject: Re: [PATCH v6 RESEND] r8152: Add support for setting pass through MAC address on RTL8153-AD
Date: Wed, 13 Jul 2016 08:23:58 +0200 [thread overview]
Message-ID: <20160713082358.487082a4@sauron> (raw)
In-Reply-To: <5a304b784fe747aea4de6b69fb12a767-uCoIPMzyhkttLtSlb8FIwwVY21JRvFwKV6yJEvX+wlw@public.gmane.org>
> So in order to hit this hypothetical corner case today you would
> need to be using a real world type-C device something such as a
> Dell WD15 on another OEM's machine that has type-C and the exact
> same ACPI object name that does $BADSTUFF other than return a
> buffer.
Exactly what I meant.
> If that situation arises please alert me and I'll send a follow up
> patch that whitelists this to match DMI vendor of only Dell
> systems.
I'm not sure if it's the most responsible way to approach this problem.
There were cases of laptops bricking (as in - they would never power on
ever again) just because Linux made some bad BIOS/ACPI calls. Also, see
the famous Samsung UEFI NVRAM fiasco or the recent pains with EFIVARS.
Regards,
MP
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-07-13 6:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 0:58 [PATCH v6 RESEND] r8152: Add support for setting pass through MAC address on RTL8153-AD Mario Limonciello
2016-07-12 2:42 ` David Miller
2016-07-12 7:02 ` Michał Pecio
2016-07-12 15:04 ` Mario_Limonciello
[not found] ` <5a304b784fe747aea4de6b69fb12a767-uCoIPMzyhkttLtSlb8FIwwVY21JRvFwKV6yJEvX+wlw@public.gmane.org>
2016-07-13 6:23 ` Michał Pecio [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=20160713082358.487082a4@sauron \
--to=michal.pecio-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=Mario_Limonciello-DYMqY+WieiM@public.gmane.org \
--cc=anthony.wong-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).