From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: patrick.rudolph@9elements.com
Cc: linux-kernel@vger.kernel.org, coreboot@coreboot.org,
Arthur Heymans <arthur@aheymans.xyz>,
Allison Randal <allison@lohutok.net>,
Thomas Gleixner <tglx@linutronix.de>,
Alexios Zavras <alexios.zavras@intel.com>
Subject: Re: [PATCH 2/3] firmware: google: Unregister driver_info on failure and exit in gsmi
Date: Sat, 16 Nov 2019 14:39:28 +0100 [thread overview]
Message-ID: <20191116133928.GD454551@kroah.com> (raw)
In-Reply-To: <20191115134842.17013-3-patrick.rudolph@9elements.com>
On Fri, Nov 15, 2019 at 02:48:38PM +0100, patrick.rudolph@9elements.com wrote:
> From: Arthur Heymans <arthur@aheymans.xyz>
>
> Fix a bug where the kernel module couldn't be loaded after unloading,
> as the platform driver wasn't released on exit.
>
> Signed-off-by: Arthur Heymans <arthur@aheymans.xyz>
> ---
When sending a patch from someone else, you too have to add your s-o-b
so that we can accept it as that shows the progression of the patch (and
you are accepting responsibility for it being correct.)
Please fix up when you resend.
thanks,
greg k-h
next prev parent reply other threads:[~2019-11-16 13:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 13:48 [PATCH 0/3] firmware: google: Fix minor bugs patrick.rudolph
2019-11-15 13:48 ` [PATCH 1/3] firmware: google: Release devices before unregistering the bus patrick.rudolph
2019-11-15 20:28 ` kbuild test robot
2019-11-16 13:38 ` Greg Kroah-Hartman
2019-11-18 8:12 ` patrick.rudolph
2019-11-15 13:48 ` [PATCH 2/3] firmware: google: Unregister driver_info on failure and exit in gsmi patrick.rudolph
2019-11-16 13:39 ` Greg Kroah-Hartman [this message]
2019-11-16 13:40 ` Greg Kroah-Hartman
2019-11-18 7:59 ` patrick.rudolph
2019-11-18 8:13 ` Greg Kroah-Hartman
2019-11-15 13:48 ` [PATCH 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=20191116133928.GD454551@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexios.zavras@intel.com \
--cc=allison@lohutok.net \
--cc=arthur@aheymans.xyz \
--cc=coreboot@coreboot.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick.rudolph@9elements.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox