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] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZL410jAw2ksuBx56@smile.fi.intel.com>
Date:   Mon, 24 Jul 2023 11:26:58 +0300
From:   Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Mark Brown <broonie@...nel.org>,
        Liam Girdwood <lgirdwood@...il.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Randy Dunlap <rdunlap@...radead.org>
Subject: Re: linux-next: build warning after merge of the sound-asoc tree

On Mon, Jul 24, 2023 at 01:58:58PM +1000, Stephen Rothwell wrote:
> On Fri, 14 Jul 2023 12:18:55 +0300 Andy Shevchenko <andriy.shevchenko@...ux.intel.com> wrote:
> > On Thu, Jul 13, 2023 at 03:41:09PM +0300, Andy Shevchenko wrote:
> > > On Thu, Jul 13, 2023 at 03:19:04PM +0300, Andy Shevchenko wrote:  
> > > > On Thu, Jul 13, 2023 at 12:16:27PM +1000, Stephen Rothwell wrote:  
> > > > > 
> > > > > After merging the sound-asoc tree, today's linux-next build (htmldocs)
> > > > > produced this warning:
> > > > > 
> > > > > include/linux/int_log.h:1: warning: no structured comments found
> > > > > 
> > > > > Introduced by commit
> > > > > 
> > > > >   f97fa3dcb2db ("lib/math: Move dvb_math.c into lib/math/int_log.c")  
> > > > 
> > > > Can you elaborate a bit, please?
> > > > 
> > > > Seems to me to be a false positive, or unveils a bug somewhere else.  
> > > 
> > > Ah, now I understand. There is a header file that has descriptions but
> > > EXPORT_SYMBOL. We have to drop keyword export from the index.
> > > 
> > > Thank you for the report, I'll cook the patch ASAP.  
> > 
> > The 20230713165320.14199-1-andriy.shevchenko@...ux.intel.com had been sent.
> 
> But not yet applied by anyone :-(

Since the culprit went via ASoC tree, I think that tree is the best for the fix.
Mark, can you apply that, please?

-- 
With Best Regards,
Andy Shevchenko


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ