From: patrick.rudolph@9elements.com
To: linux-kernel@vger.kernel.org
Cc: coreboot@coreboot.org,
Patrick Rudolph <patrick.rudolph@9elements.com>,
Allison Randal <allison@lohutok.net>,
Thomas Gleixner <tglx@linutronix.de>,
Alexios Zavras <alexios.zavras@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arthur Heymans <arthur@aheymans.xyz>
Subject: [PATCH v3 0/3] firmware: google: Fix minor bugs
Date: Mon, 18 Nov 2019 11:19:28 +0100 [thread overview]
Message-ID: <20191118101934.22526-1-patrick.rudolph@9elements.com> (raw)
From: Patrick Rudolph <patrick.rudolph@9elements.com>
This patch series fixes 3 independent bugs in the google firmware
drivers.
Patch 1-2 do proper cleanup at kernel module unloading.
Patch 3 adds a check if the optional GSMI SMM handler is actually
present in the firmware and responses to the driver.
Changes in v2:
- Add missing return statement
- Add s-o-b on GSMI patches
- Add define for reserved GSMI command
Changes in v3:
- Cosmetic changes only
Arthur Heymans (2):
firmware: google: Unregister driver_info on failure and exit in gsmi
firmware: google: Probe for a GSMI handler in firmware
Patrick Rudolph (1):
firmware: google: Release devices before unregistering the bus
drivers/firmware/google/coreboot_table.c | 7 +++++++
drivers/firmware/google/gsmi.c | 25 ++++++++++++++++++++++++
2 files changed, 32 insertions(+)
--
2.21.0
next reply other threads:[~2019-11-18 10:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 10:19 patrick.rudolph [this message]
2019-11-18 10:19 ` [PATCH v3 1/3] firmware: google: Release devices before unregistering the bus patrick.rudolph
2019-11-18 10:19 ` [PATCH v3 2/3] firmware: google: Unregister driver_info on failure and exit in gsmi patrick.rudolph
2019-11-18 10:19 ` [PATCH v3 3/3] firmware: google: Probe for a GSMI handler in firmware patrick.rudolph
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=20191118101934.22526-1-patrick.rudolph@9elements.com \
--to=patrick.rudolph@9elements.com \
--cc=alexios.zavras@intel.com \
--cc=allison@lohutok.net \
--cc=arthur@aheymans.xyz \
--cc=coreboot@coreboot.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.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.