public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
* linux-next: build warnings after merge of the i2c-host tree
@ 2024-07-12  6:55 Stephen Rothwell
  2024-07-12  7:02 ` Wolfram Sang
  0 siblings, 1 reply; 3+ messages in thread
From: Stephen Rothwell @ 2024-07-12  6:55 UTC (permalink / raw)
  To: Andi Shyti
  Cc: Wolfram Sang, Linux Kernel Mailing List, Linux Next Mailing List

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

Hi all,

After merging the i2c-host tree, today's linux-next build (htmldocs)
produced these warnings:

include/linux/i2c.h:583: warning: Function parameter or struct member 'xfer' not described in 'i2c_algorithm'
include/linux/i2c.h:583: warning: Function parameter or struct member 'xfer_atomic' not described in 'i2c_algorithm'
include/linux/i2c.h:583: warning: Function parameter or struct member 'reg_target' not described in 'i2c_algorithm'
include/linux/i2c.h:583: warning: Function parameter or struct member 'unreg_target' not described in 'i2c_algorithm'

Introduced by commit

  a93c2e5fe766 ("i2c: reword i2c_algorithm according to newest specification")

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: linux-next: build warnings after merge of the i2c-host tree
  2024-07-12  6:55 linux-next: build warnings after merge of the i2c-host tree Stephen Rothwell
@ 2024-07-12  7:02 ` Wolfram Sang
  2024-07-13  6:56   ` Andi Shyti
  0 siblings, 1 reply; 3+ messages in thread
From: Wolfram Sang @ 2024-07-12  7:02 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Andi Shyti, Linux Kernel Mailing List, Linux Next Mailing List

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


> include/linux/i2c.h:583: warning: Function parameter or struct member 'xfer' not described in 'i2c_algorithm'
> include/linux/i2c.h:583: warning: Function parameter or struct member 'xfer_atomic' not described in 'i2c_algorithm'
> include/linux/i2c.h:583: warning: Function parameter or struct member 'reg_target' not described in 'i2c_algorithm'
> include/linux/i2c.h:583: warning: Function parameter or struct member 'unreg_target' not described in 'i2c_algorithm'

Ouch, yes. I will fix this! Thanks. Seems like regular buildbot builds
do not build docs when they were changed?


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: linux-next: build warnings after merge of the i2c-host tree
  2024-07-12  7:02 ` Wolfram Sang
@ 2024-07-13  6:56   ` Andi Shyti
  0 siblings, 0 replies; 3+ messages in thread
From: Andi Shyti @ 2024-07-13  6:56 UTC (permalink / raw)
  To: Wolfram Sang, Stephen Rothwell, Linux Kernel Mailing List,
	Linux Next Mailing List

On Fri, Jul 12, 2024 at 09:02:24AM GMT, Wolfram Sang wrote:
> > include/linux/i2c.h:583: warning: Function parameter or struct member 'xfer' not described in 'i2c_algorithm'
> > include/linux/i2c.h:583: warning: Function parameter or struct member 'xfer_atomic' not described in 'i2c_algorithm'
> > include/linux/i2c.h:583: warning: Function parameter or struct member 'reg_target' not described in 'i2c_algorithm'
> > include/linux/i2c.h:583: warning: Function parameter or struct member 'unreg_target' not described in 'i2c_algorithm'
> 
> Ouch, yes. I will fix this! Thanks. Seems like regular buildbot builds
> do not build docs when they were changed?

apparently not, because I received only build success messages.

I will add the docs building in my test flow.

Thanks Stephen,
Andi

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2024-07-13  6:56 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-07-12  6:55 linux-next: build warnings after merge of the i2c-host tree Stephen Rothwell
2024-07-12  7:02 ` Wolfram Sang
2024-07-13  6:56   ` Andi Shyti

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox