From: Corey Minyard <minyard@acm.org>
To: Emilio Perez <emiliopeju@gmail.com>
Cc: "moderated list:IPMI SUBSYSTEM"
<openipmi-developer@lists.sourceforge.net>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ipmi: Use regspacings passed as a module parameter
Date: Wed, 22 Nov 2023 14:49:01 -0600 [thread overview]
Message-ID: <ZV5pPW9RsGsazy4i@mail.minyard.net> (raw)
In-Reply-To: <20231122203433.443098-1-emiliopeju@gmail.com>
On Wed, Nov 22, 2023 at 08:34:28PM +0000, Emilio Perez wrote:
> regspacings parameter is currently ignored and the platform data uses a
> default value of 0, this has been fixed by setting the appropriate field
> in the platform data.
Yep, queued for next release. Thank you.
-corey
>
> Fixes: 3cd83bac481d ("ipmi: Consolidate the adding of platform devices")
> Signed-off-by: Emilio Perez <emiliopeju@gmail.com>
> ---
> drivers/char/ipmi/ipmi_si_hardcode.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/char/ipmi/ipmi_si_hardcode.c b/drivers/char/ipmi/ipmi_si_hardcode.c
> index ed5e91b1e040..0c92fa3eee88 100644
> --- a/drivers/char/ipmi/ipmi_si_hardcode.c
> +++ b/drivers/char/ipmi/ipmi_si_hardcode.c
> @@ -80,10 +80,10 @@ static void __init ipmi_hardcode_init_one(const char *si_type_str,
> }
>
> p.regsize = regsizes[i];
> + p.regspacing = regspacings[i];
> p.slave_addr = slave_addrs[i];
> p.addr_source = SI_HARDCODED;
> p.regshift = regshifts[i];
> - p.regsize = regsizes[i];
> p.addr = addr;
> p.space = addr_space;
>
> --
> 2.39.3
>
prev parent reply other threads:[~2023-11-22 20:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 20:34 [PATCH] ipmi: Use regspacings passed as a module parameter Emilio Perez
2023-11-22 20:49 ` Corey Minyard [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=ZV5pPW9RsGsazy4i@mail.minyard.net \
--to=minyard@acm.org \
--cc=emiliopeju@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
/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