From: Corey Minyard <minyard@acm.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Titus Rwantare <titusr@google.com>, Hao Wu <wuhaotsh@google.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Joel Stanley <joel@jms.id.au>
Subject: Re: [GIT PULL] I2C/IPMI bug fixes for QEMU 6.1
Date: Tue, 6 Jul 2021 16:45:35 -0500 [thread overview]
Message-ID: <20210706214535.GU2921206@minyard.net> (raw)
In-Reply-To: <CAFEAcA-dvSPpKoJ-+ATYcBs6UuLJY1ZKwx-9WYvPyJ+0MYU4ew@mail.gmail.com>
Hmm, it compiled for me, I wonder if there are some compiler
differences, but I don't see how.
Anyway, copying the original patch source so they know.
Thanks for checking.
-corey
On Tue, Jul 06, 2021 at 10:16:36PM +0100, Peter Maydell wrote:
> On Tue, 6 Jul 2021 at 21:06, Corey Minyard <minyard@acm.org> wrote:
> >
> > The following changes since commit 38848ce565849e5b867a5e08022b3c755039c11a:
> >
> > Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20210616' into staging (2021-06-16 17:02:30 +0100)
> >
> > are available in the Git repository at:
> >
> > https://github.com/cminyard/qemu.git tags/for-qemu-6.1-1
> >
> > for you to fetch changes up to 7051d605e6b03259e0185dd574f760b93d15fa10:
> >
> > ipmi/sim: fix watchdog_expired data type error in IPMIBmcSim struct (2021-06-25 08:54:57 -0500)
> >
> > ----------------------------------------------------------------
> > Some qemu updates for IPMI and I2C
> >
> > Move some ADC file to where they belong and move some sensors to a
> > sensor directory, since with new BMCs coming in lots of different
> > sensors should be coming in. Keep from cluttering things up.
> >
> > Add support for I2C PMBus devices.
> >
> > Replace the confusing and error-prone i2c_send_recv and i2c_transfer with
> > specific send and receive functions. Several errors have already been
> > made with these, avoid any new errors.
> >
> > Fix the watchdog_expired field in the IPMI watchdog, it's not a bool,
> > it's a u8. After a vmstate transfer, the new value could be wrong.
> >
>
> Hi; this fails to compile on 32-bit hosts:
>
> ../../hw/sensor/max34451.c: In function 'max34451_init':
> /home/peter.maydell/qemu/include/qemu/bitops.h:22:38: error: left
> shift count >= width of type [-Werror=shift-count-overflow]
> #define BIT(nr) (1UL << (nr))
> ^
> /home/peter.maydell/qemu/include/hw/i2c/pmbus_device.h:253:36: note:
> in expansion of macro 'BIT'
> #define PB_HAS_TEMPERATURE BIT(40)
> ^~~
> ../../hw/sensor/max34451.c:725:37: note: in expansion of macro
> 'PB_HAS_TEMPERATURE'
> pmbus_page_config(pmdev, i, PB_HAS_TEMPERATURE | PB_HAS_VOUT_MODE);
> ^~~~~~~~~~~~~~~~~~
> cc1: all warnings being treated as errors
>
> You probably wanted to define PB_HAS_TEMPERATURE using BIT_ULL().
>
> Sample gitlab CI job failure with this error:
> https://gitlab.com/qemu-project/qemu/-/jobs/1403927147
>
> thanks
> -- PMM
>
next prev parent reply other threads:[~2021-07-06 21:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 20:05 [GIT PULL] I2C/IPMI bug fixes for QEMU 6.1 Corey Minyard
2021-07-06 21:16 ` Peter Maydell
2021-07-06 21:45 ` Corey Minyard [this message]
2021-07-06 21:59 ` Peter Maydell
2021-07-08 17:23 ` Titus Rwantare
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=20210706214535.GU2921206@minyard.net \
--to=minyard@acm.org \
--cc=joel@jms.id.au \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=titusr@google.com \
--cc=wuhaotsh@google.com \
/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).