From: "David E. Box" <david.e.box@linux.intel.com>
To: hdegoede@redhat.com, mgross@linux.intel.com
Cc: lee.jones@linaro.org, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] platform/x86: intel_pmt_class: Initial resource to 0
Date: Tue, 23 Mar 2021 10:29:59 -0700 [thread overview]
Message-ID: <425422a30006a869f8cbefce3ee6be8764b2b03c.camel@linux.intel.com> (raw)
In-Reply-To: <20210317024455.3071477-1-david.e.box@linux.intel.com>
On Tue, 2021-03-16 at 19:44 -0700, David E. Box wrote:
> Initialize the struct resource in intel_pmt_dev_register to zero to
> avoid a
> fault should the char *name field be non-zero.
Hi Hans. Can these 2 patches be pulled as fixes for 5.12? Thanks.
David
>
> Signed-off-by: David E. Box <david.e.box@linux.intel.com>
> ---
>
> Base commit is v5.12-rc3.
>
> drivers/platform/x86/intel_pmt_class.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/platform/x86/intel_pmt_class.c
> b/drivers/platform/x86/intel_pmt_class.c
> index c8939fba4509..ee2b3bbeb83d 100644
> --- a/drivers/platform/x86/intel_pmt_class.c
> +++ b/drivers/platform/x86/intel_pmt_class.c
> @@ -173,7 +173,7 @@ static int intel_pmt_dev_register(struct
> intel_pmt_entry *entry,
> struct intel_pmt_namespace *ns,
> struct device *parent)
> {
> - struct resource res;
> + struct resource res = {0};
> struct device *dev;
> int ret;
>
>
> base-commit: 1e28eed17697bcf343c6743f0028cc3b5dd88bf0
next prev parent reply other threads:[~2021-03-23 17:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 2:44 [PATCH 1/2] platform/x86: intel_pmt_class: Initial resource to 0 David E. Box
2021-03-17 2:44 ` [PATCH 2/2] platform_x86: intel_pmt_crashlog: Fix incorrect macros David E. Box
2021-03-23 17:29 ` David E. Box [this message]
2021-03-23 20:15 ` [PATCH 1/2] platform/x86: intel_pmt_class: Initial resource to 0 Hans de Goede
2021-03-23 20:10 ` Hans de Goede
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=425422a30006a869f8cbefce3ee6be8764b2b03c.camel@linux.intel.com \
--to=david.e.box@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgross@linux.intel.com \
--cc=platform-driver-x86@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