linux-next: build warning after merge of Linus' tree

linux-next: build warning after merge of Linus' tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 361 bytes --]

Hi all,

While building Linus' tree, today's linux-next build (htmldocs)
produced this warning:

include/media/v4l2-subdev.h:1130: warning: Function parameter or member 'client_caps' not described in 'v4l2_subdev_fh'

Introduced by commit

  f57fa2959244 ("media: v4l2-subdev: Add new ioctl for client capabilities")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: build warning after merge of Linus' tree

[Sakari Ailus]

Hi Stephen,

On Mon, May 08, 2023 at 02:44:26PM +1000, Stephen Rothwell wrote:
>   f57fa2959244 ("media: v4l2-subdev: Add new ioctl for client capabilities")

There's a fix for this but it hasn't been merged yet, will be soon.

<URL:https://lore.kernel.org/linux-media/20230418105924.126608-1-tomi.valkeinen@ideasonboard.com/>

-- 
Sakari Ailus

linux-next: build warning after merge of Linus' tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 347 bytes --]

Hi all,

After merging Linus' tree, today's linux-next build (htmldocs)
produced this warning:

block/blk-settings.c:281: warning: expecting prototype for queue_limits_commit_set(). Prototype was for queue_limits_set() instead

Introduced by commit

  bff4b74625fe ("Revert "dm: use queue_limits_set"")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

linux-next: build warning after merge of Linus' tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 362 bytes --]

Hi all,

Building Linus' tree, today's linux-next build (htmldocs) produced
this warning:

drivers/gpu/drm/amd/include/amd_shared.h:103: warning: Enum value 'AMD_IP_BLOCK_TYPE_NUM' not described in enum 'amd_ip_block_type'

Introduced by commit

  6ee27ee27ba8 ("drm/amd/pm: avoid duplicate powergate/ungate setting")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: build warning after merge of Linus' tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 500 bytes --]

Hi all,

On Tue, 23 Nov 2021 16:29:38 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> Building Linus' tree, today's linux-next build (htmldocs) produced
> this warning:
> 
> drivers/gpu/drm/amd/include/amd_shared.h:103: warning: Enum value 'AMD_IP_BLOCK_TYPE_NUM' not described in enum 'amd_ip_block_type'
> 
> Introduced by commit
> 
>   6ee27ee27ba8 ("drm/amd/pm: avoid duplicate powergate/ungate setting")

I am still seeing this warning.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

linux-next: build warning after merge of Linus' tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 344 bytes --]

Hi all,

In Linus' tree, today's linux-next build (htmldocs) produced this warning:

Documentation/filesystems/index.rst:18: WARNING: toctree contains reference to nonexisting document 'filesystems/mandatory-locking'

Introduced by commit

  f7e33bdbd6d1 ("fs: remove mandatory file locking support")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: build warning after merge of Linus' tree

[Jeff Layton]

On Tue, 2021-10-05 at 20:18 +1100, Stephen Rothwell wrote:
> Hi all,
> 
> In Linus' tree, today's linux-next build (htmldocs) produced this warning:
> 
> Documentation/filesystems/index.rst:18: WARNING: toctree contains reference to nonexisting document 'filesystems/mandatory-locking'
> 
> Introduced by commit
> 
>   f7e33bdbd6d1 ("fs: remove mandatory file locking support")
> 

Thanks Stephen.

I rolled up a patch to remove that line and put it in my locks-next
branch. It should end up in linux-next soon. I'll plan to send that on
to Linus for v5.16, unless anyone thinks it needs to go in sooner.
-- 
Jeff Layton <jlayton@kernel.org>

linux-next: build warning after merge of Linus' tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 338 bytes --]

Hi all,

Building Linus' tree, today's linux-next build (htmldocs) produced
this warning:

include/net/sock.h:533: warning: Function parameter or member 'sk_peer_lock' not described in 'sock'

Introduced by commit

  35306eb23814 ("af_unix: fix races in sk_peer_pid and sk_peer_cred accesses")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: build warning after merge of Linus' tree

[Eric Dumazet]

On Fri, Oct 1, 2021 at 12:18 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> Building Linus' tree, today's linux-next build (htmldocs) produced
> this warning:
>
> include/net/sock.h:533: warning: Function parameter or member 'sk_peer_lock' not described in 'sock'
>
> Introduced by commit
>
>   35306eb23814 ("af_unix: fix races in sk_peer_pid and sk_peer_cred accesses")


OK, I will fix this, thank you.

linux-next: build warning after merge of Linus' tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 657 bytes --]

Hi all,

After merging the origin tree, today's linux-next build (powerpc
allyesconfig) produced this warning:

sound/aoa/codecs/onyx.c: In function 'onyx_snd_single_bit_get':
sound/aoa/codecs/onyx.c:377:37: warning: 'c' may be used uninitialized in this function [-Wmaybe-uninitialized]
  ucontrol->value.integer.value[0] = !!(c & mask) ^ polarity;
                                     ^~~~~~~~~~~~

Introduced by commit

  f3d9478b2ce4 ("[ALSA] snd-aoa: add snd-aoa")

This warning has been around for a long time.  It could possibly be
suppressed by checking for errors returned by onyx_read_register().

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: build warning after merge of Linus' tree

[Takashi Iwai]

On Mon, 29 Jul 2019 06:04:04 +0200,
Stephen Rothwell wrote:
> 
> Hi all,
> 
> After merging the origin tree, today's linux-next build (powerpc
> allyesconfig) produced this warning:
> 
> sound/aoa/codecs/onyx.c: In function 'onyx_snd_single_bit_get':
> sound/aoa/codecs/onyx.c:377:37: warning: 'c' may be used uninitialized in this function [-Wmaybe-uninitialized]
>   ucontrol->value.integer.value[0] = !!(c & mask) ^ polarity;
>                                      ^~~~~~~~~~~~
> 
> Introduced by commit
> 
>   f3d9478b2ce4 ("[ALSA] snd-aoa: add snd-aoa")
> 
> This warning has been around for a long time.  It could possibly be
> suppressed by checking for errors returned by onyx_read_register().

Yes, or simply zero-ing the variable in onyx_read_register().  The
current code ignores the read error and it's been OK over a decade :)


thanks,

Takashi

Re: linux-next: build warning after merge of Linus' tree

[Johannes Berg]

On Mon, 2019-07-29 at 08:58 +0200, Takashi Iwai wrote:
> On Mon, 29 Jul 2019 06:04:04 +0200,
> Stephen Rothwell wrote:
> > Hi all,
> > 
> > After merging the origin tree, today's linux-next build (powerpc
> > allyesconfig) produced this warning:
> > 
> > sound/aoa/codecs/onyx.c: In function 'onyx_snd_single_bit_get':
> > sound/aoa/codecs/onyx.c:377:37: warning: 'c' may be used uninitialized in this function [-Wmaybe-uninitialized]
> >   ucontrol->value.integer.value[0] = !!(c & mask) ^ polarity;
> >                                      ^~~~~~~~~~~~
> > 
> > Introduced by commit
> > 
> >   f3d9478b2ce4 ("[ALSA] snd-aoa: add snd-aoa")
> > 
> > This warning has been around for a long time.  It could possibly be
> > suppressed by checking for errors returned by onyx_read_register().
> 
> Yes, or simply zero-ing the variable in onyx_read_register().  The
> current code ignores the read error and it's been OK over a decade :)

Yeah, it's pretty weird that it never showed up before. I was wondering
for a minute why I was CC'ed on a sound merge issue :-)

Do you want me to send a patch or just commit something to suppress
this?

johannes

Re: linux-next: build warning after merge of Linus' tree

[Takashi Iwai]

On Mon, 29 Jul 2019 09:03:14 +0200,
Johannes Berg wrote:
> 
> On Mon, 2019-07-29 at 08:58 +0200, Takashi Iwai wrote:
> > On Mon, 29 Jul 2019 06:04:04 +0200,
> > Stephen Rothwell wrote:
> > > Hi all,
> > > 
> > > After merging the origin tree, today's linux-next build (powerpc
> > > allyesconfig) produced this warning:
> > > 
> > > sound/aoa/codecs/onyx.c: In function 'onyx_snd_single_bit_get':
> > > sound/aoa/codecs/onyx.c:377:37: warning: 'c' may be used uninitialized in this function [-Wmaybe-uninitialized]
> > >   ucontrol->value.integer.value[0] = !!(c & mask) ^ polarity;
> > >                                      ^~~~~~~~~~~~
> > > 
> > > Introduced by commit
> > > 
> > >   f3d9478b2ce4 ("[ALSA] snd-aoa: add snd-aoa")
> > > 
> > > This warning has been around for a long time.  It could possibly be
> > > suppressed by checking for errors returned by onyx_read_register().
> > 
> > Yes, or simply zero-ing the variable in onyx_read_register().  The
> > current code ignores the read error and it's been OK over a decade :)
> 
> Yeah, it's pretty weird that it never showed up before. I was wondering
> for a minute why I was CC'ed on a sound merge issue :-)

Maybe switched to a new gcc version?

> Do you want me to send a patch or just commit something to suppress
> this?

Yes, that'd be appreciated.


Thanks!

Takashi

Re: linux-next: build warning after merge of Linus' tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 869 bytes --]

Hi all,

On Mon, 29 Jul 2019 09:07:10 +0200 Takashi Iwai <tiwai@suse.de> wrote:
>
> On Mon, 29 Jul 2019 09:03:14 +0200,
> Johannes Berg wrote:
> > 
> > On Mon, 2019-07-29 at 08:58 +0200, Takashi Iwai wrote:  
> > > > This warning has been around for a long time.  It could possibly be
> > > > suppressed by checking for errors returned by onyx_read_register().  
> > > 
> > > Yes, or simply zero-ing the variable in onyx_read_register().  The
> > > current code ignores the read error and it's been OK over a decade :)  
> > 
> > Yeah, it's pretty weird that it never showed up before. I was wondering
> > for a minute why I was CC'ed on a sound merge issue :-)  
> 
> Maybe switched to a new gcc version?

Or the number of warnings in a powerpc allyesconfig build got low
enough for me to finally take notice :-)

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]