From: Andrew Morton <akpm@linux-foundation.org>
To: David Laight <David.Laight@ACULAB.COM>
Cc: 'Jonathan Cameron' <jic23@kernel.org>,
'Jakob Hauser' <jahau@rocketmail.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Linus Walleij <linus.walleij@linaro.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v2] iio: magnetometer: yas530: Use signed integer type for clamp limits
Date: Sat, 30 Nov 2024 18:32:22 -0800 [thread overview]
Message-ID: <20241130183222.ecf271abffcff61b93bbae22@linux-foundation.org> (raw)
In-Reply-To: <6f2c9946a9fe4b40ac7dd5a66003c8c4@AcuMS.aculab.com>
On Sat, 30 Nov 2024 20:59:22 +0000 David Laight <David.Laight@ACULAB.COM> wrote:
> From: Jonathan Cameron
> > Sent: 30 November 2024 14:35
> >
> > On Sat, 30 Nov 2024 11:40:45 +0000
> > David Laight <David.Laight@ACULAB.COM> wrote:
> >
> > > From: Jakob Hauser
> > >
> > > Copying Andrew M - he might want to take this through his mm tree.
> >
> > I'm confused. Why?
> >
> > Looks like a local bug in an IIO driver. What am I missing?
>
> The build test bot picked it up because a change to minmax.h that Andrew
> committed to the mm tree showed up the bug.
> To avoid W=1 builds failing Andrew had applied a temporary 'fix'.
> So he needs to be in the loop at least.
> I don't know the actual procedure :-)
Jakob's minmax changes
(https://lkml.kernel.org/r/c50365d214e04f9ba256d417c8bebbc0@AcuMS.aculab.com)
are queued in mm.git for 6.14-rc1. They require a yas530 fix to build.
So as I need to carry this yas530 fix in mm.git I'd like to merge it as
a hotfix for 6.13-rcX, sometime in the next week or two. So please
send acks!
next prev parent reply other threads:[~2024-12-01 2:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 21:25 [PATCH v2] iio: magnetometer: yas530: Use signed integer type for clamp limits Jakob Hauser
2024-11-30 11:40 ` David Laight
2024-11-30 14:35 ` Jonathan Cameron
2024-11-30 20:59 ` David Laight
2024-12-01 2:32 ` Andrew Morton [this message]
2024-12-01 11:04 ` David Laight
2024-12-01 13:38 ` Jonathan Cameron
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=20241130183222.ecf271abffcff61b93bbae22@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=David.Laight@ACULAB.COM \
--cc=jahau@rocketmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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