lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20241201133854.2e87400c@jic23-huawei>
Date: Sun, 1 Dec 2024 13:38:54 +0000
From: Jonathan Cameron <jic23@...nel.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: David Laight <David.Laight@...LAB.COM>, 'Jakob Hauser'
 <jahau@...ketmail.com>, Lars-Peter Clausen <lars@...afoo.de>, Linus Walleij
 <linus.walleij@...aro.org>, "linux-iio@...r.kernel.org"
 <linux-iio@...r.kernel.org>, "linux-kernel@...r.kernel.org"
 <linux-kernel@...r.kernel.org>, kernel test robot <lkp@...el.com>
Subject: Re: [PATCH v2] iio: magnetometer: yas530: Use signed integer type
 for clamp limits

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

> On Sat, 30 Nov 2024 20:59:22 +0000 David Laight <David.Laight@...LAB.COM> wrote:
> 
> > From: Jonathan Cameron  
> > > Sent: 30 November 2024 14:35
> > > 
> > > On Sat, 30 Nov 2024 11:40:45 +0000
> > > David Laight <David.Laight@...LAB.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@...wei.com>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ