Re: [PATCH 6.6 027/222] cleanup: Adjust scoped_guard() macros to avoid potential warning

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jan 07, 2025 at 11:01:23AM +0100, Przemek Kitszel wrote:
> On 1/6/25 16:13, Greg Kroah-Hartman wrote:
> > 6.6-stable review patch.  If anyone has any objections, please let me know.
> > 
> > ------------------
> > 
> > From: Przemek Kitszel <przemyslaw.kitszel@xxxxxxxxx>
> > 
> > [ Upstream commit fcc22ac5baf06dd17193de44b60dbceea6461983 ]
> > 
> > Change scoped_guard() and scoped_cond_guard() macros to make reasoning
> > about them easier for static analysis tools (smatch, compiler
> > diagnostics), especially to enable them to tell if the given usage of
> > scoped_guard() is with a conditional lock class (interruptible-locks,
> > try-locks) or not (like simple mutex_lock()).
> > 
> 
> please also consider cherry pick of the commit 9a884bdb6e95 ("iio:
> magnetometer: fix if () scoped_guard() formatting") when picking
> the one in the subject

Did you try to apply that commit to the 6.6.y tree?  If you have it
working, please send us the correct backport because as-is, it does not
apply at all.

thanks,

greg k-h




[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux