qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Corey Minyard <minyard@acm.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, armbru@redhat.com
Subject: Re: [PATCH] pm_smbus: rename variable to avoid shadowing
Date: Tue, 26 Sep 2023 07:46:34 -0500	[thread overview]
Message-ID: <ZRLSqhgqlGVAk2/C@mail.minyard.net> (raw)
In-Reply-To: <20230925144744.527958-2-pbonzini@redhat.com>

On Mon, Sep 25, 2023 at 04:47:39PM +0200, Paolo Bonzini wrote:
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
>  hw/i2c/pm_smbus.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

This looks ok to me.

Acked-by: Corey Minyard <cminyard@mvista.com>

> 
> diff --git a/hw/i2c/pm_smbus.c b/hw/i2c/pm_smbus.c
> index 9ad6a47739b..4e1b8a5182d 100644
> --- a/hw/i2c/pm_smbus.c
> +++ b/hw/i2c/pm_smbus.c
> @@ -279,7 +279,7 @@ static void smb_ioport_writeb(void *opaque, hwaddr addr, uint64_t val,
>              if (!read && s->smb_index == s->smb_data0) {
>                  uint8_t prot = (s->smb_ctl >> 2) & 0x07;
>                  uint8_t cmd = s->smb_cmd;
> -                uint8_t addr = s->smb_addr >> 1;
> +                uint8_t smb_addr = s->smb_addr >> 1;
>                  int ret;
>  
>                  if (prot == PROT_I2C_BLOCK_READ) {
> @@ -287,7 +287,7 @@ static void smb_ioport_writeb(void *opaque, hwaddr addr, uint64_t val,
>                      goto out;
>                  }
>  
> -                ret = smbus_write_block(s->smbus, addr, cmd, s->smb_data,
> +                ret = smbus_write_block(s->smbus, smb_addr, cmd, s->smb_data,
>                                          s->smb_data0, !s->i2c_enable);
>                  if (ret < 0) {
>                      s->smb_stat |= STS_DEV_ERR;
> -- 
> 2.41.0
> 
> 


      reply	other threads:[~2023-09-26 12:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-25 14:47 [PATCH] pm_smbus: rename variable to avoid shadowing Paolo Bonzini
2023-09-26 12:46 ` 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=ZRLSqhgqlGVAk2/C@mail.minyard.net \
    --to=minyard@acm.org \
    --cc=armbru@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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).