Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: David Laight <David.Laight@ACULAB.COM>,
	'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: Sun, 1 Dec 2024 13:38:54 +0000	[thread overview]
Message-ID: <20241201133854.2e87400c@jic23-huawei> (raw)
In-Reply-To: <20241130183222.ecf271abffcff61b93bbae22@linux-foundation.org>

On Sat, 30 Nov 2024 18:32:22 -0800
Andrew Morton <akpm@linux-foundation.org> wrote:

> 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!

Thanks for the info - I'm fine with this going through mm.

Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>

      parent reply	other threads:[~2024-12-01 13:39 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
2024-12-01 11:04         ` David Laight
2024-12-01 13:38         ` Jonathan Cameron [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=20241201133854.2e87400c@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=David.Laight@ACULAB.COM \
    --cc=akpm@linux-foundation.org \
    --cc=jahau@rocketmail.com \
    --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