Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
* linux-next: build warnings after merge of the drm tree
@ 2021-04-01  7:32 Stephen Rothwell
  2021-04-21  6:30 ` Stephen Rothwell
  0 siblings, 1 reply; 25+ messages in thread
From: Stephen Rothwell @ 2021-04-01  7:32 UTC (permalink / raw)
  To: Dave Airlie, DRI
  Cc: Daniel Vetter, Maarten Lankhorst, Linux Kernel Mailing List,
	Linux Next Mailing List


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

Hi all,

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

drivers/gpu/drm/i915/i915_cmd_parser.c:1420: warning: Excess function parameter 'trampoline' description in 'intel_engine_cmd_parser'
drivers/gpu/drm/i915/i915_cmd_parser.c:1420: warning: Function parameter or member 'jump_whitelist' not described in 'intel_engine_cmd_parser'
drivers/gpu/drm/i915/i915_cmd_parser.c:1420: warning: Function parameter or member 'shadow_map' not described in 'intel_engine_cmd_parser'
drivers/gpu/drm/i915/i915_cmd_parser.c:1420: warning: Function parameter or member 'batch_map' not described in 'intel_engine_cmd_parser'
drivers/gpu/drm/i915/i915_cmd_parser.c:1420: warning: Excess function parameter 'trampoline' description in 'intel_engine_cmd_parser'


Introduced by commit

  0edbb9ba1bfe ("drm/i915: Move cmd parser pinning to execbuffer")

-- 
Cheers,
Stephen Rothwell

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

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

* Re: linux-next: build warnings after merge of the drm tree
  2021-04-01  7:32 linux-next: build warnings after merge of the drm tree Stephen Rothwell
@ 2021-04-21  6:30 ` Stephen Rothwell
  0 siblings, 0 replies; 25+ messages in thread
From: Stephen Rothwell @ 2021-04-21  6:30 UTC (permalink / raw)
  To: Dave Airlie, DRI
  Cc: Daniel Vetter, Maarten Lankhorst, Linux Kernel Mailing List,
	Linux Next Mailing List


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

Hi all,

On Thu, 1 Apr 2021 18:32:34 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> After merging the drm tree, today's linux-next build (htmldocs) produced
> these warnings:
> 
> drivers/gpu/drm/i915/i915_cmd_parser.c:1420: warning: Excess function parameter 'trampoline' description in 'intel_engine_cmd_parser'
> drivers/gpu/drm/i915/i915_cmd_parser.c:1420: warning: Function parameter or member 'jump_whitelist' not described in 'intel_engine_cmd_parser'
> drivers/gpu/drm/i915/i915_cmd_parser.c:1420: warning: Function parameter or member 'shadow_map' not described in 'intel_engine_cmd_parser'
> drivers/gpu/drm/i915/i915_cmd_parser.c:1420: warning: Function parameter or member 'batch_map' not described in 'intel_engine_cmd_parser'
> drivers/gpu/drm/i915/i915_cmd_parser.c:1420: warning: Excess function parameter 'trampoline' description in 'intel_engine_cmd_parser'
> 
> Introduced by commit
> 
>   0edbb9ba1bfe ("drm/i915: Move cmd parser pinning to execbuffer")

I am still seeing these warnings (as of next-20210420).

-- 
Cheers,
Stephen Rothwell

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

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

* Re: linux-next: build warnings after merge of the drm tree
  2020-12-15  2:47     ` Stephen Rothwell
@ 2020-12-15  9:42       ` Daniel Vetter
  0 siblings, 0 replies; 25+ messages in thread
From: Daniel Vetter @ 2020-12-15  9:42 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Dave Airlie, DRI, Linux Next Mailing List,
	Linux Kernel Mailing List, Thomas Zimmermann

On Tue, Dec 15, 2020 at 3:47 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> On Tue, 15 Dec 2020 06:50:45 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > On Mon, 16 Nov 2020 10:44:44 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > >
> > > On Thu, 5 Nov 2020 17:50:31 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > > >
> > > > After merging the drm tree, today's linux-next build (htmldocs) produced
> > > > these warnings:
> > > >
> > > > include/linux/dma-buf-map.h:106: warning: Excess function parameter 'vaddr' description in 'DMA_BUF_MAP_INIT_VADDR'
> > > > include/linux/dma-buf-map.h:106: warning: Function parameter or member 'vaddr_' not described in 'DMA_BUF_MAP_INIT_VADDR'
> > > > include/linux/dma-buf-map.h:106: warning: Excess function parameter 'vaddr' description in 'DMA_BUF_MAP_INIT_VADDR'
> > > >
> > > > Introduced by commit
> > > >
> > > >   20e76f1a7059 ("dma-buf: Use struct dma_buf_map in dma_buf_vunmap() interfaces")
> > >
> > > I am still getting these warnings.
> >
> > I am still getting these warnings.
>
> These warnings are now from Linus' tree.

We had a stuck pull request which should have been included in the
main merge pull. This should be fixed now in drm-next. Well in a few
minutes when the compile testing is done.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

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

* Re: linux-next: build warnings after merge of the drm tree
  2020-12-14 19:50   ` Stephen Rothwell
@ 2020-12-15  2:47     ` Stephen Rothwell
  2020-12-15  9:42       ` Daniel Vetter
  0 siblings, 1 reply; 25+ messages in thread
From: Stephen Rothwell @ 2020-12-15  2:47 UTC (permalink / raw)
  To: Dave Airlie, DRI
  Cc: Thomas Zimmermann, Linux Kernel Mailing List, Linux Next Mailing List


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

Hi all,

On Tue, 15 Dec 2020 06:50:45 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> On Mon, 16 Nov 2020 10:44:44 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > On Thu, 5 Nov 2020 17:50:31 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:  
> > >
> > > After merging the drm tree, today's linux-next build (htmldocs) produced
> > > these warnings:
> > > 
> > > include/linux/dma-buf-map.h:106: warning: Excess function parameter 'vaddr' description in 'DMA_BUF_MAP_INIT_VADDR'
> > > include/linux/dma-buf-map.h:106: warning: Function parameter or member 'vaddr_' not described in 'DMA_BUF_MAP_INIT_VADDR'
> > > include/linux/dma-buf-map.h:106: warning: Excess function parameter 'vaddr' description in 'DMA_BUF_MAP_INIT_VADDR'
> > > 
> > > Introduced by commit
> > > 
> > >   20e76f1a7059 ("dma-buf: Use struct dma_buf_map in dma_buf_vunmap() interfaces")    
> > 
> > I am still getting these warnings.  
> 
> I am still getting these warnings.

These warnings are now from Linus' tree.

-- 
Cheers,
Stephen Rothwell

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

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

* Re: linux-next: build warnings after merge of the drm tree
  2020-11-15 23:44 ` Stephen Rothwell
@ 2020-12-14 19:50   ` Stephen Rothwell
  2020-12-15  2:47     ` Stephen Rothwell
  0 siblings, 1 reply; 25+ messages in thread
From: Stephen Rothwell @ 2020-12-14 19:50 UTC (permalink / raw)
  To: Dave Airlie, DRI
  Cc: Thomas Zimmermann, Linux Kernel Mailing List, Linux Next Mailing List


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

Hi all,

On Mon, 16 Nov 2020 10:44:44 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> On Thu, 5 Nov 2020 17:50:31 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > After merging the drm tree, today's linux-next build (htmldocs) produced
> > these warnings:
> > 
> > include/linux/dma-buf-map.h:106: warning: Excess function parameter 'vaddr' description in 'DMA_BUF_MAP_INIT_VADDR'
> > include/linux/dma-buf-map.h:106: warning: Function parameter or member 'vaddr_' not described in 'DMA_BUF_MAP_INIT_VADDR'
> > include/linux/dma-buf-map.h:106: warning: Excess function parameter 'vaddr' description in 'DMA_BUF_MAP_INIT_VADDR'
> > 
> > Introduced by commit
> > 
> >   20e76f1a7059 ("dma-buf: Use struct dma_buf_map in dma_buf_vunmap() interfaces")  
> 
> I am still getting these warnings.

I am still getting these warnings.

-- 
Cheers,
Stephen Rothwell

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

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

* Re: linux-next: build warnings after merge of the drm tree
  2020-11-05  6:50 Stephen Rothwell
@ 2020-11-15 23:44 ` Stephen Rothwell
  2020-12-14 19:50   ` Stephen Rothwell
  0 siblings, 1 reply; 25+ messages in thread
From: Stephen Rothwell @ 2020-11-15 23:44 UTC (permalink / raw)
  To: Dave Airlie, DRI
  Cc: Thomas Zimmermann, Linux Kernel Mailing List, Linux Next Mailing List


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

Hi all,

On Thu, 5 Nov 2020 17:50:31 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
> 
> After merging the drm tree, today's linux-next build (htmldocs) produced
> these warnings:
> 
> include/linux/dma-buf-map.h:106: warning: Excess function parameter 'vaddr' description in 'DMA_BUF_MAP_INIT_VADDR'
> include/linux/dma-buf-map.h:106: warning: Function parameter or member 'vaddr_' not described in 'DMA_BUF_MAP_INIT_VADDR'
> include/linux/dma-buf-map.h:106: warning: Excess function parameter 'vaddr' description in 'DMA_BUF_MAP_INIT_VADDR'
> 
> Introduced by commit
> 
>   20e76f1a7059 ("dma-buf: Use struct dma_buf_map in dma_buf_vunmap() interfaces")

I am still getting these warnings.

-- 
Cheers,
Stephen Rothwell

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

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

* linux-next: build warnings after merge of the drm tree
@ 2020-11-05  6:50 Stephen Rothwell
  2020-11-15 23:44 ` Stephen Rothwell
  0 siblings, 1 reply; 25+ messages in thread
From: Stephen Rothwell @ 2020-11-05  6:50 UTC (permalink / raw)
  To: Dave Airlie, DRI
  Cc: Thomas Zimmermann, Linux Kernel Mailing List, Linux Next Mailing List


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

Hi all,

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

include/linux/dma-buf-map.h:106: warning: Excess function parameter 'vaddr' description in 'DMA_BUF_MAP_INIT_VADDR'
include/linux/dma-buf-map.h:106: warning: Function parameter or member 'vaddr_' not described in 'DMA_BUF_MAP_INIT_VADDR'
include/linux/dma-buf-map.h:106: warning: Excess function parameter 'vaddr' description in 'DMA_BUF_MAP_INIT_VADDR'

Introduced by commit

  20e76f1a7059 ("dma-buf: Use struct dma_buf_map in dma_buf_vunmap() interfaces")

-- 
Cheers,
Stephen Rothwell

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

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

* Re: linux-next: build warnings after merge of the drm tree
  2017-11-01  3:16 Stephen Rothwell
@ 2017-11-01  9:58 ` Boris Brezillon
  0 siblings, 0 replies; 25+ messages in thread
From: Boris Brezillon @ 2017-11-01  9:58 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Dave Airlie, Linux-Next Mailing List, Linux Kernel Mailing List,
	Eric Anholt

Hi Stephen,

On Wed, 1 Nov 2017 14:16:40 +1100
Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi Dave,
> 
> After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
> produced these warnings:
> 
> drivers/gpu/drm/vc4/vc4_bo.c: In function 'vc4_bo_stats_debugfs':
> drivers/gpu/drm/vc4/vc4_bo.c:91:17: warning: format '%d' expects argument of type 'int', but argument 4 has type 'size_t {aka long unsigned int}' [-Wformat=]
>    seq_printf(m, "%30s: %6dkb BOs (%d)\n", "userspace BO cache",
>                  ^
> drivers/gpu/drm/vc4/vc4_bo.c:95:17: warning: format '%d' expects argument of type 'int', but argument 4 has type 'size_t {aka long unsigned int}' [-Wformat=]
>    seq_printf(m, "%30s: %6dkb BOs (%d)\n", "total purged BO",
>                  ^
> 
> Introduced by commit
> 
>   b9f19259b84d ("drm/vc4: Add the DRM_IOCTL_VC4_GEM_MADVISE ioctl")
> 

Just sent a patch fixing the problem.

Thanks for the report.

Boris

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

* linux-next: build warnings after merge of the drm tree
@ 2017-11-01  3:16 Stephen Rothwell
  2017-11-01  9:58 ` Boris Brezillon
  0 siblings, 1 reply; 25+ messages in thread
From: Stephen Rothwell @ 2017-11-01  3:16 UTC (permalink / raw)
  To: Dave Airlie
  Cc: Linux-Next Mailing List, Linux Kernel Mailing List,
	Boris Brezillon, Eric Anholt

Hi Dave,

After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
produced these warnings:

drivers/gpu/drm/vc4/vc4_bo.c: In function 'vc4_bo_stats_debugfs':
drivers/gpu/drm/vc4/vc4_bo.c:91:17: warning: format '%d' expects argument of type 'int', but argument 4 has type 'size_t {aka long unsigned int}' [-Wformat=]
   seq_printf(m, "%30s: %6dkb BOs (%d)\n", "userspace BO cache",
                 ^
drivers/gpu/drm/vc4/vc4_bo.c:95:17: warning: format '%d' expects argument of type 'int', but argument 4 has type 'size_t {aka long unsigned int}' [-Wformat=]
   seq_printf(m, "%30s: %6dkb BOs (%d)\n", "total purged BO",
                 ^

Introduced by commit

  b9f19259b84d ("drm/vc4: Add the DRM_IOCTL_VC4_GEM_MADVISE ioctl")

-- 
Cheers,
Stephen Rothwell

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

* Re: linux-next: build warnings after merge of the drm tree
  2017-06-03  0:45           ` Eric Anholt
@ 2017-06-03  1:26             ` Stephen Rothwell
  0 siblings, 0 replies; 25+ messages in thread
From: Stephen Rothwell @ 2017-06-03  1:26 UTC (permalink / raw)
  To: Eric Anholt
  Cc: Dave Airlie, Linux-Next Mailing List, Linux Kernel Mailing List,
	Tom Cooksey, Daniel Vetter, Linus Walleij, Arnd Bergmann,
	Caesar Wang, Mark Yao

Hi Eric,

On Fri, 02 Jun 2017 17:45:10 -0700 Eric Anholt <eric@anholt.net> wrote:
>
> Stephen Rothwell <sfr@canb.auug.org.au> writes:
> 
> > On Fri, 02 Jun 2017 14:05:14 -0700 Eric Anholt <eric@anholt.net> wrote:  
> >>
> >> Not sure what's going on.  I see your "yesterday" list present, and not
> >> your "today" commit.  
> >
> > I just refetched the drm-misc tree and received no changes.  It is
> > still as I said in the previous email.  This tree is fetched from the
> > drm-misc-next branch of git://anongit.freedesktop.org/drm/drm-misc
> >
> > The single commit currently in that branch was authored by "Caesar Wang
> > <wxt@rock-chips.com>" and committed by "Mark Yao
> > <mark.yao@rock-chips.com>" (both now cc'd).  
> 
> I see that commit in drm-misc-next-fixes, but not drm-misc-next.

I see it in the drm-misc-fixes tree (branch for-linux-next-fixes) as
well (along with another commit).

I made a mistake above, the drm-misc tree is branch for-linux-next.
-- 
Cheers,
Stephen Rothwell

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

* Re: linux-next: build warnings after merge of the drm tree
  2017-06-02 23:40         ` Stephen Rothwell
@ 2017-06-03  0:45           ` Eric Anholt
  2017-06-03  1:26             ` Stephen Rothwell
  0 siblings, 1 reply; 25+ messages in thread
From: Eric Anholt @ 2017-06-03  0:45 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Dave Airlie, Linux-Next Mailing List, Linux Kernel Mailing List,
	Tom Cooksey, Daniel Vetter, Linus Walleij, Arnd Bergmann,
	Caesar Wang, Mark Yao


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

Stephen Rothwell <sfr@canb.auug.org.au> writes:

> Hi Eric,
>
> On Fri, 02 Jun 2017 14:05:14 -0700 Eric Anholt <eric@anholt.net> wrote:
>>
>> Not sure what's going on.  I see your "yesterday" list present, and not
>> your "today" commit.
>
> I just refetched the drm-misc tree and received no changes.  It is
> still as I said in the previous email.  This tree is fetched from the
> drm-misc-next branch of git://anongit.freedesktop.org/drm/drm-misc
>
> The single commit currently in that branch was authored by "Caesar Wang
> <wxt@rock-chips.com>" and committed by "Mark Yao
> <mark.yao@rock-chips.com>" (both now cc'd).

I see that commit in drm-misc-next-fixes, but not drm-misc-next.

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

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

* Re: linux-next: build warnings after merge of the drm tree
  2017-06-02 21:05       ` Eric Anholt
@ 2017-06-02 23:40         ` Stephen Rothwell
  2017-06-03  0:45           ` Eric Anholt
  0 siblings, 1 reply; 25+ messages in thread
From: Stephen Rothwell @ 2017-06-02 23:40 UTC (permalink / raw)
  To: Eric Anholt
  Cc: Dave Airlie, Linux-Next Mailing List, Linux Kernel Mailing List,
	Tom Cooksey, Daniel Vetter, Linus Walleij, Arnd Bergmann,
	Caesar Wang, Mark Yao

Hi Eric,

On Fri, 02 Jun 2017 14:05:14 -0700 Eric Anholt <eric@anholt.net> wrote:
>
> Not sure what's going on.  I see your "yesterday" list present, and not
> your "today" commit.

I just refetched the drm-misc tree and received no changes.  It is
still as I said in the previous email.  This tree is fetched from the
drm-misc-next branch of git://anongit.freedesktop.org/drm/drm-misc

The single commit currently in that branch was authored by "Caesar Wang
<wxt@rock-chips.com>" and committed by "Mark Yao
<mark.yao@rock-chips.com>" (both now cc'd).

-- 
Cheers,
Stephen Rothwell

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

* Re: linux-next: build warnings after merge of the drm tree
  2017-06-02  3:59     ` Stephen Rothwell
@ 2017-06-02 21:05       ` Eric Anholt
  2017-06-02 23:40         ` Stephen Rothwell
  0 siblings, 1 reply; 25+ messages in thread
From: Eric Anholt @ 2017-06-02 21:05 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Dave Airlie, Linux-Next Mailing List, Linux Kernel Mailing List,
	Tom Cooksey, Daniel Vetter, Linus Walleij, Arnd Bergmann


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

Stephen Rothwell <sfr@canb.auug.org.au> writes:

> Hi all,
>
> On Thu, 25 May 2017 11:49:42 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>> On Fri, 19 May 2017 10:49:06 -0700 Eric Anholt <eric@anholt.net> wrote:
>> >
>> > Stephen Rothwell <sfr@canb.auug.org.au> writes:
>> >   
>> > > After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
>> > > produced these warnings:
>> > >
>> > > drivers/gpu/drm/pl111/pl111_drv.c:81:12: warning: 'pl111_modeset_init' defined but not used [-Wunused-function]
>> > >  static int pl111_modeset_init(struct drm_device *dev)
>> > >             ^
>> > > drivers/gpu/drm/pl111/pl111_drv.c:149:26: warning: 'pl111_drm_driver' defined but not used [-Wunused-variable]
>> > >  static struct drm_driver pl111_drm_driver = {
>> > >                           ^    
>> > 
>> > Sorry about that -- I thought that kbuild test robot would give me
>> > notification of new warnings.
>> > 
>> > Patch incoming.  
>> 
>> I saw the patch, but it doesn't seem to have been applied anywhere yet.
>
> So these warnings went away yesterday, but are back today after quite a
> few patches were dropped from the drm-misc tree.
>
> Yesterday it contained theses (relative to the drm tree):
>
> 9a8d5e4a53dc drm/vc4: Fix comment in vc4_drv.h
> 66d6dd45eee2 drm/pl111: fix warnings without CONFIG_ARM_AMBA
> 91110a4b64fe drm/atomic: Consitfy mode parameter to drm_atomic_set_mode_for_crtc()
> fb51cbfd4b2e drm/arcgpu: Drop drm_vblank_cleanup
> e3ec0e1e38a5 drm/atmel: Drop drm_vblank_cleanup
> 85769cf7cd7f drm/imx: Drop drm_vblank_cleanup
> a360b39b5137 drm/meson: Drop drm_vblank_cleanup
> 25b905fe4323 drm/stm: Drop drm_vblank_cleanup
> d79373bd4d7e drm/sun4i: Drop drm_vblank_cleanup
> 8938d13585bc drm: better document how to send out the crtc disable event
> 46466b0dac3f drm: Use vsnprintf extension %ph
> 99cdb35e787b drm/doc: move printf helpers out of drmP.h
> e7cc23de3e4e drm/pl111: select DRM_PANEL
> 7dbcbce9f551 drm/bridge: analogix-anx78xx: Use bridge->mode_valid() callback
> faf94a0883ce drm: Use mode_valid() in atomic modeset
> 97f973d65260 drm: Use new mode_valid() helpers in connector probe helper
> b1240f81a186 drm: Introduce drm_bridge_mode_valid()
> da251bf8f935 drm: Add drm_{crtc/encoder/connector}_mode_valid()
> 18e51064c42c drm: Remove drm_device->virtdev
> a301b1118615 drm: todo: remove task about switch to drm_connector_list_iter
> eb53a46be597 drm: remove unsafe drm_for_each_connector()
> 4894bf711d19 drm/vc4: use drm_for_each_connector_iter()
> 875dd62697fe drm/nouveau: use drm_for_each_connector_iter()
> c8bf8b968adb drm/mediatek: use drm_for_each_connector_iter()
> 2fd96b4116bf drm/i915: use drm_for_each_connector_iter()
> 2cbeb64f6c70 drm/rockchip: use drm_for_each_connector_iter()
> 48a92916729b drm/exynos: use drm_for_each_connector_iter()
>
> Today it only has:
>
> 2d7b56378d32 drm/rockchip: gem: add the lacks lock and trivial changes

Not sure what's going on.  I see your "yesterday" list present, and not
your "today" commit.

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

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

* Re: linux-next: build warnings after merge of the drm tree
  2017-05-25  1:49   ` Stephen Rothwell
@ 2017-06-02  3:59     ` Stephen Rothwell
  2017-06-02 21:05       ` Eric Anholt
  0 siblings, 1 reply; 25+ messages in thread
From: Stephen Rothwell @ 2017-06-02  3:59 UTC (permalink / raw)
  To: Eric Anholt
  Cc: Dave Airlie, Linux-Next Mailing List, Linux Kernel Mailing List,
	Tom Cooksey, Daniel Vetter, Linus Walleij, Arnd Bergmann

Hi all,

On Thu, 25 May 2017 11:49:42 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> On Fri, 19 May 2017 10:49:06 -0700 Eric Anholt <eric@anholt.net> wrote:
> >
> > Stephen Rothwell <sfr@canb.auug.org.au> writes:
> >   
> > > After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
> > > produced these warnings:
> > >
> > > drivers/gpu/drm/pl111/pl111_drv.c:81:12: warning: 'pl111_modeset_init' defined but not used [-Wunused-function]
> > >  static int pl111_modeset_init(struct drm_device *dev)
> > >             ^
> > > drivers/gpu/drm/pl111/pl111_drv.c:149:26: warning: 'pl111_drm_driver' defined but not used [-Wunused-variable]
> > >  static struct drm_driver pl111_drm_driver = {
> > >                           ^    
> > 
> > Sorry about that -- I thought that kbuild test robot would give me
> > notification of new warnings.
> > 
> > Patch incoming.  
> 
> I saw the patch, but it doesn't seem to have been applied anywhere yet.

So these warnings went away yesterday, but are back today after quite a
few patches were dropped from the drm-misc tree.

Yesterday it contained theses (relative to the drm tree):

9a8d5e4a53dc drm/vc4: Fix comment in vc4_drv.h
66d6dd45eee2 drm/pl111: fix warnings without CONFIG_ARM_AMBA
91110a4b64fe drm/atomic: Consitfy mode parameter to drm_atomic_set_mode_for_crtc()
fb51cbfd4b2e drm/arcgpu: Drop drm_vblank_cleanup
e3ec0e1e38a5 drm/atmel: Drop drm_vblank_cleanup
85769cf7cd7f drm/imx: Drop drm_vblank_cleanup
a360b39b5137 drm/meson: Drop drm_vblank_cleanup
25b905fe4323 drm/stm: Drop drm_vblank_cleanup
d79373bd4d7e drm/sun4i: Drop drm_vblank_cleanup
8938d13585bc drm: better document how to send out the crtc disable event
46466b0dac3f drm: Use vsnprintf extension %ph
99cdb35e787b drm/doc: move printf helpers out of drmP.h
e7cc23de3e4e drm/pl111: select DRM_PANEL
7dbcbce9f551 drm/bridge: analogix-anx78xx: Use bridge->mode_valid() callback
faf94a0883ce drm: Use mode_valid() in atomic modeset
97f973d65260 drm: Use new mode_valid() helpers in connector probe helper
b1240f81a186 drm: Introduce drm_bridge_mode_valid()
da251bf8f935 drm: Add drm_{crtc/encoder/connector}_mode_valid()
18e51064c42c drm: Remove drm_device->virtdev
a301b1118615 drm: todo: remove task about switch to drm_connector_list_iter
eb53a46be597 drm: remove unsafe drm_for_each_connector()
4894bf711d19 drm/vc4: use drm_for_each_connector_iter()
875dd62697fe drm/nouveau: use drm_for_each_connector_iter()
c8bf8b968adb drm/mediatek: use drm_for_each_connector_iter()
2fd96b4116bf drm/i915: use drm_for_each_connector_iter()
2cbeb64f6c70 drm/rockchip: use drm_for_each_connector_iter()
48a92916729b drm/exynos: use drm_for_each_connector_iter()

Today it only has:

2d7b56378d32 drm/rockchip: gem: add the lacks lock and trivial changes

-- 
Cheers,
Stephen Rothwell

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

* Re: linux-next: build warnings after merge of the drm tree
  2017-05-19 17:49 ` Eric Anholt
@ 2017-05-25  1:49   ` Stephen Rothwell
  2017-06-02  3:59     ` Stephen Rothwell
  0 siblings, 1 reply; 25+ messages in thread
From: Stephen Rothwell @ 2017-05-25  1:49 UTC (permalink / raw)
  To: Eric Anholt
  Cc: Dave Airlie, Linux-Next Mailing List, Linux Kernel Mailing List,
	Tom Cooksey, Daniel Vetter, Linus Walleij

Hi Eric,

On Fri, 19 May 2017 10:49:06 -0700 Eric Anholt <eric@anholt.net> wrote:
>
> Stephen Rothwell <sfr@canb.auug.org.au> writes:
> 
> > After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
> > produced these warnings:
> >
> > drivers/gpu/drm/pl111/pl111_drv.c:81:12: warning: 'pl111_modeset_init' defined but not used [-Wunused-function]
> >  static int pl111_modeset_init(struct drm_device *dev)
> >             ^
> > drivers/gpu/drm/pl111/pl111_drv.c:149:26: warning: 'pl111_drm_driver' defined but not used [-Wunused-variable]
> >  static struct drm_driver pl111_drm_driver = {
> >                           ^  
> 
> Sorry about that -- I thought that kbuild test robot would give me
> notification of new warnings.
> 
> Patch incoming.

I saw the patch, but it doesn't seem to have been applied anywhere yet.

-- 
Cheers,
Stephen Rothwell

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

* Re: linux-next: build warnings after merge of the drm tree
  2017-05-19  2:07 Stephen Rothwell
@ 2017-05-19 17:49 ` Eric Anholt
  2017-05-25  1:49   ` Stephen Rothwell
  0 siblings, 1 reply; 25+ messages in thread
From: Eric Anholt @ 2017-05-19 17:49 UTC (permalink / raw)
  To: Stephen Rothwell, Dave Airlie
  Cc: Linux-Next Mailing List, Linux Kernel Mailing List, Tom Cooksey,
	Daniel Vetter, Linus Walleij


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

Stephen Rothwell <sfr@canb.auug.org.au> writes:

> Hi Dave,
>
> After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
> produced these warnings:
>
> drivers/gpu/drm/pl111/pl111_drv.c:81:12: warning: 'pl111_modeset_init' defined but not used [-Wunused-function]
>  static int pl111_modeset_init(struct drm_device *dev)
>             ^
> drivers/gpu/drm/pl111/pl111_drv.c:149:26: warning: 'pl111_drm_driver' defined but not used [-Wunused-variable]
>  static struct drm_driver pl111_drm_driver = {
>                           ^

Sorry about that -- I thought that kbuild test robot would give me
notification of new warnings.

Patch incoming.

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

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

* linux-next: build warnings after merge of the drm tree
@ 2017-05-19  2:07 Stephen Rothwell
  2017-05-19 17:49 ` Eric Anholt
  0 siblings, 1 reply; 25+ messages in thread
From: Stephen Rothwell @ 2017-05-19  2:07 UTC (permalink / raw)
  To: Dave Airlie
  Cc: Linux-Next Mailing List, Linux Kernel Mailing List, Tom Cooksey,
	Eric Anholt, Daniel Vetter, Linus Walleij

Hi Dave,

After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
produced these warnings:

drivers/gpu/drm/pl111/pl111_drv.c:81:12: warning: 'pl111_modeset_init' defined but not used [-Wunused-function]
 static int pl111_modeset_init(struct drm_device *dev)
            ^
drivers/gpu/drm/pl111/pl111_drv.c:149:26: warning: 'pl111_drm_driver' defined but not used [-Wunused-variable]
 static struct drm_driver pl111_drm_driver = {
                          ^

Introduced by commit

  bed41005e617 ("drm/pl111: Initial drm/kms driver for pl111")

-- 
Cheers,
Stephen Rothwell

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

* linux-next: build warnings after merge of the drm tree
@ 2017-02-23 23:27 Stephen Rothwell
  0 siblings, 0 replies; 25+ messages in thread
From: Stephen Rothwell @ 2017-02-23 23:27 UTC (permalink / raw)
  To: Dave Airlie; +Cc: linux-next, linux-kernel, Noralf Trønnes

Hi Dave,

After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
produced these warnings:

/next/include/drm/drm_gem_cma_helper.h:4:0,
                 from include/drm/tinydrm/tinydrm.h:13,
                 from include/drm/tinydrm/mipi-dbi.h:15,
                 from drivers/gpu/drm/tinydrm/mipi-dbi.c:12:
drivers/gpu/drm/tinydrm/mipi-dbi.c: In function 'mipi_dbi_typec1_command':
drivers/gpu/drm/tinydrm/mipi-dbi.c:65:20: warning: field width specifier '*' expects argument of type 'int', but argument 5 has type 'size_t {aka long unsigned int}' [-Wformat=]
   DRM_DEBUG_DRIVER("cmd=%02x, par=%*ph\n", cmd, len, data); \
                    ^
include/drm/drmP.h:228:40: note: in definition of macro 'DRM_DEBUG_DRIVER'
  drm_printk(KERN_DEBUG, DRM_UT_DRIVER, fmt, ##__VA_ARGS__)
                                        ^
drivers/gpu/drm/tinydrm/mipi-dbi.c:671:2: note: in expansion of macro 'MIPI_DBI_DEBUG_COMMAND'
  MIPI_DBI_DEBUG_COMMAND(cmd, parameters, num);
  ^
drivers/gpu/drm/tinydrm/mipi-dbi.c: In function 'mipi_dbi_typec3_command_read':
drivers/gpu/drm/tinydrm/mipi-dbi.c:65:20: warning: field width specifier '*' expects argument of type 'int', but argument 5 has type 'size_t {aka long unsigned int}' [-Wformat=]
   DRM_DEBUG_DRIVER("cmd=%02x, par=%*ph\n", cmd, len, data); \
                    ^
include/drm/drmP.h:228:40: note: in definition of macro 'DRM_DEBUG_DRIVER'
  drm_printk(KERN_DEBUG, DRM_UT_DRIVER, fmt, ##__VA_ARGS__)
                                        ^
drivers/gpu/drm/tinydrm/mipi-dbi.c:740:2: note: in expansion of macro 'MIPI_DBI_DEBUG_COMMAND'
  MIPI_DBI_DEBUG_COMMAND(cmd, data, len);
  ^
drivers/gpu/drm/tinydrm/mipi-dbi.c: In function 'mipi_dbi_typec3_command':
drivers/gpu/drm/tinydrm/mipi-dbi.c:65:20: warning: field width specifier '*' expects argument of type 'int', but argument 5 has type 'size_t {aka long unsigned int}' [-Wformat=]
   DRM_DEBUG_DRIVER("cmd=%02x, par=%*ph\n", cmd, len, data); \
                    ^
include/drm/drmP.h:228:40: note: in definition of macro 'DRM_DEBUG_DRIVER'
  drm_printk(KERN_DEBUG, DRM_UT_DRIVER, fmt, ##__VA_ARGS__)
                                        ^
drivers/gpu/drm/tinydrm/mipi-dbi.c:759:2: note: in expansion of macro 'MIPI_DBI_DEBUG_COMMAND'
  MIPI_DBI_DEBUG_COMMAND(cmd, par, num);
  ^
drivers/gpu/drm/tinydrm/mipi-dbi.c: In function 'mipi_dbi_debugfs_command_write':
drivers/gpu/drm/tinydrm/mipi-dbi.c:905:8: warning: 'cmd' may be used uninitialized in this function [-Wmaybe-uninitialized]
  ret = mipi_dbi_command_buf(mipi, cmd, parameters, i);
        ^
Introduced by commit

  02dd95fe3169 ("drm/tinydrm: Add MIPI DBI support")

-- 
Cheers,
Stephen Rothwell

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

* linux-next: build warnings after merge of the drm tree
@ 2017-02-19 23:48 Stephen Rothwell
  0 siblings, 0 replies; 25+ messages in thread
From: Stephen Rothwell @ 2017-02-19 23:48 UTC (permalink / raw)
  To: Dave Airlie; +Cc: linux-next, linux-kernel, Vincent Abriou, Fabien Dessenne

Hi Dave,

After merging the drm tree, today's linux-next build (arm
multi_v7_defconfig) produced these warnings:

drivers/gpu/drm/sti/sti_vtg.c: In function 'vtg_probe':
drivers/gpu/drm/sti/sti_vtg.c:392:22: warning: unused variable 'np' [-Wunused-variable]
  struct device_node *np;
                      ^

Introduced by commit

  0c7ff84f7f9d ("drm/sti: remove deprecated legacy vtg slave")

drivers/gpu/drm/sti/sti_drv.c:120:13: warning: 'sti_drm_dbg_cleanup' defined but not used [-Wunused-function]
 static void sti_drm_dbg_cleanup(struct drm_minor *minor)
             ^

Introduced by commit

  5e60f595d6ca ("drm/sti: use atomic_helper for commit")

[BTW, this latter commit has no Signed-off-by from its committer :-(]

-- 
Cheers,
Stephen Rothwell

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

* linux-next: build warnings after merge of the drm tree
@ 2012-10-04  2:21 Stephen Rothwell
  0 siblings, 0 replies; 25+ messages in thread
From: Stephen Rothwell @ 2012-10-04  2:21 UTC (permalink / raw)
  To: Dave Airlie; +Cc: linux-next, linux-kernel


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

Hi Dave,

After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
produced these warnings:

drivers/gpu/drm/gma500/backlight.c:29:13: warning: 'do_gma_backlight_set' defined but not used [-Wunused-function]
drivers/gpu/drm/nouveau/core/subdev/gpio/base.c: In function 'nouveau_gpio_isr_del':
drivers/gpu/drm/nouveau/core/subdev/gpio/base.c:219:4: warning: 'flush_work_sync' is deprecated (declared at include/linux/workqueue.h:448) [-Wdeprecated-declarations]
drivers/gpu/drm/nouveau/nouveau_drm.c: In function 'nouveau_drm_open':
drivers/gpu/drm/nouveau/nouveau_drm.c:503:2: warning: format '%d' expects argument of type 'int', but argument 4 has type 'struct pid *' [-Wformat]

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

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

* Re: linux-next: build warnings after merge of the drm tree
  2012-09-04  8:22   ` Dave Airlie
@ 2012-09-04  8:58     ` Sedat Dilek
  0 siblings, 0 replies; 25+ messages in thread
From: Sedat Dilek @ 2012-09-04  8:58 UTC (permalink / raw)
  To: Dave Airlie
  Cc: Stephen Rothwell, linux-next, linux-kernel, Sachin Kamat,
	Guenter Roeck, Greg Kroah-Hartman

On Tue, Sep 4, 2012 at 10:22 AM, Dave Airlie <airlied@linux.ie> wrote:
>> > After merging the drm tree, today's linux-next build (powerpc
>> > ppc64_defconfig) produced these warnings:
>> >
>> > drivers/gpu/drm/udl/Kconfig:1:error: recursive dependency detected!
>> > drivers/gpu/drm/udl/Kconfig:1:  symbol DRM_UDL depends on USB_ARCH_HAS_HCD
>> > drivers/usb/Kconfig:76: symbol USB_ARCH_HAS_HCD depends on USB_SUPPORT
>> > drivers/usb/Kconfig:58: symbol USB_SUPPORT is selected by DRM_USB
>> > drivers/gpu/drm/Kconfig:22:     symbol DRM_USB is selected by DRM_UDL
>> > warning: (PPC_PS3) selects USB_OHCI_LITTLE_ENDIAN which has unmet direct dependencies (USB_SUPPORT && USB_OHCI_HCD)
>> > warning: (PPC_PS3 && PPC_CELLEB) selects USB_OHCI_BIG_ENDIAN_MMIO which has unmet direct dependencies (USB_SUPPORT && USB_OHCI_HCD)
>> > warning: (PPC_PS3 && PPC_CELLEB && USB_EHCI_HCD_PMC_MSP && XPS_USB_HCD_XILINX && USB_OCTEON_EHCI) selects USB_EHCI_BIG_ENDIAN_MMIO which has unmet direct dependencies (USB_SUPPORT && USB_EHCI_HCD && (PPC_CELLEB || PPC_PS3 || 440EPX || ARCH_IXP4XX || XPS_USB_HCD_XILINX || PPC_MPC512x || CPU_CAVIUM_OCTEON || PMC_MSP || SPARC_LEON || MIPS_SEAD3))
>> >
>> > The x86_64 allmodconfig produces these:
>> >
>> > drivers/gpu/drm/udl/Kconfig:1:error: recursive dependency detected!
>> > drivers/gpu/drm/udl/Kconfig:1:  symbol DRM_UDL depends on USB_ARCH_HAS_HCD
>> > drivers/usb/Kconfig:76: symbol USB_ARCH_HAS_HCD depends on USB_SUPPORT
>> > drivers/usb/Kconfig:58: symbol USB_SUPPORT is selected by DRM_USB
>> > drivers/gpu/drm/Kconfig:22:     symbol DRM_USB is selected by DRM_UDL
>> > warning: (MOUSE_APPLETOUCH && MOUSE_BCM5974 && MOUSE_SYNAPTICS_USB && JOYSTICK_XPAD && TABLET_USB_ACECAD && TABLET_USB_AIPTEK && TABLET_USB_HANWANG && TABLET_USB_KBTAB && TABLET_USB_WACOM && TOUCHSCREEN_USB_COMPOSITE && INPUT_ATI_REMOTE2 && INPUT_KEYSPAN_REMOTE && INPUT_POWERMATE && INPUT_YEALINK && INPUT_CM109 && RC_ATI_REMOTE && IR_IMON && IR_MCEUSB && IR_REDRAT3 && IR_STREAMZAP && IR_IGUANA && IR_TTUSBIR && DRM_USB) selects USB which has unmet direct dependencies (USB_SUPPORT && USB_ARCH_HAS_HCD)
>> >
>> > Maybe introduced by commit df0b34430072 ("drm/usb: select USB_SUPPORT in
>> > Kconfig"), maybe interacting with a commit 8f057d7bca54 ("gpu/mfd/usb:
>> > Fix USB randconfig problems") from Linus' tree (that added "depends on
>> > USB_ARCH_HAS_HCD" to "config DRM_USB" and "config DRM_UDL").
>> >
>> > I have left this mess for now, but it needs addressing.
>>
>> I have sent a fix ("drm/udl: usb: Fix recursive Kconfig dependency")
>> for this mess and pinged airlied on IRC.
>> NOTE: I saw this when I merged drm(-intel){-fixes,next} into next-20120824.
>
> I[ve pushed it to drm-next now hopefully it will resolve the mess.
>

Great and thanks!

Can't say if the label of my patch should be changed to "drm/usb: ..."
as the culprit commit df0b34430072 (drm/usb: select USB_SUPPORT in
Kconfig) has it and the fix is done in drm/usb Kconfig definition.
( Thinking loud of people searching within (git-)logs. )

For me the current status of drm-next is OK (next time I do better).

- Sedat -

[1] http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commitdiff;h=df0b344300724e00db9fff7eb6406eb91f450b91

> thanks,
> Dave.

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

* Re: linux-next: build warnings after merge of the drm tree
  2012-09-04  6:40 ` Sedat Dilek
@ 2012-09-04  8:22   ` Dave Airlie
  2012-09-04  8:58     ` Sedat Dilek
  0 siblings, 1 reply; 25+ messages in thread
From: Dave Airlie @ 2012-09-04  8:22 UTC (permalink / raw)
  To: Sedat Dilek
  Cc: Stephen Rothwell, linux-next, linux-kernel, Sachin Kamat,
	Guenter Roeck, Greg Kroah-Hartman

> > After merging the drm tree, today's linux-next build (powerpc
> > ppc64_defconfig) produced these warnings:
> >
> > drivers/gpu/drm/udl/Kconfig:1:error: recursive dependency detected!
> > drivers/gpu/drm/udl/Kconfig:1:  symbol DRM_UDL depends on USB_ARCH_HAS_HCD
> > drivers/usb/Kconfig:76: symbol USB_ARCH_HAS_HCD depends on USB_SUPPORT
> > drivers/usb/Kconfig:58: symbol USB_SUPPORT is selected by DRM_USB
> > drivers/gpu/drm/Kconfig:22:     symbol DRM_USB is selected by DRM_UDL
> > warning: (PPC_PS3) selects USB_OHCI_LITTLE_ENDIAN which has unmet direct dependencies (USB_SUPPORT && USB_OHCI_HCD)
> > warning: (PPC_PS3 && PPC_CELLEB) selects USB_OHCI_BIG_ENDIAN_MMIO which has unmet direct dependencies (USB_SUPPORT && USB_OHCI_HCD)
> > warning: (PPC_PS3 && PPC_CELLEB && USB_EHCI_HCD_PMC_MSP && XPS_USB_HCD_XILINX && USB_OCTEON_EHCI) selects USB_EHCI_BIG_ENDIAN_MMIO which has unmet direct dependencies (USB_SUPPORT && USB_EHCI_HCD && (PPC_CELLEB || PPC_PS3 || 440EPX || ARCH_IXP4XX || XPS_USB_HCD_XILINX || PPC_MPC512x || CPU_CAVIUM_OCTEON || PMC_MSP || SPARC_LEON || MIPS_SEAD3))
> >
> > The x86_64 allmodconfig produces these:
> >
> > drivers/gpu/drm/udl/Kconfig:1:error: recursive dependency detected!
> > drivers/gpu/drm/udl/Kconfig:1:  symbol DRM_UDL depends on USB_ARCH_HAS_HCD
> > drivers/usb/Kconfig:76: symbol USB_ARCH_HAS_HCD depends on USB_SUPPORT
> > drivers/usb/Kconfig:58: symbol USB_SUPPORT is selected by DRM_USB
> > drivers/gpu/drm/Kconfig:22:     symbol DRM_USB is selected by DRM_UDL
> > warning: (MOUSE_APPLETOUCH && MOUSE_BCM5974 && MOUSE_SYNAPTICS_USB && JOYSTICK_XPAD && TABLET_USB_ACECAD && TABLET_USB_AIPTEK && TABLET_USB_HANWANG && TABLET_USB_KBTAB && TABLET_USB_WACOM && TOUCHSCREEN_USB_COMPOSITE && INPUT_ATI_REMOTE2 && INPUT_KEYSPAN_REMOTE && INPUT_POWERMATE && INPUT_YEALINK && INPUT_CM109 && RC_ATI_REMOTE && IR_IMON && IR_MCEUSB && IR_REDRAT3 && IR_STREAMZAP && IR_IGUANA && IR_TTUSBIR && DRM_USB) selects USB which has unmet direct dependencies (USB_SUPPORT && USB_ARCH_HAS_HCD)
> >
> > Maybe introduced by commit df0b34430072 ("drm/usb: select USB_SUPPORT in
> > Kconfig"), maybe interacting with a commit 8f057d7bca54 ("gpu/mfd/usb:
> > Fix USB randconfig problems") from Linus' tree (that added "depends on
> > USB_ARCH_HAS_HCD" to "config DRM_USB" and "config DRM_UDL").
> >
> > I have left this mess for now, but it needs addressing.
> 
> I have sent a fix ("drm/udl: usb: Fix recursive Kconfig dependency")
> for this mess and pinged airlied on IRC.
> NOTE: I saw this when I merged drm(-intel){-fixes,next} into next-20120824.

I[ve pushed it to drm-next now hopefully it will resolve the mess.

thanks,
Dave.

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

* Re: linux-next: build warnings after merge of the drm tree
  2012-09-04  3:58 Stephen Rothwell
  2012-09-04  5:31 ` Guenter Roeck
@ 2012-09-04  6:40 ` Sedat Dilek
  2012-09-04  8:22   ` Dave Airlie
  1 sibling, 1 reply; 25+ messages in thread
From: Sedat Dilek @ 2012-09-04  6:40 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Dave Airlie, linux-next, linux-kernel, Sachin Kamat,
	Guenter Roeck, Greg Kroah-Hartman

On Tue, Sep 4, 2012 at 5:58 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Dave,
>
> After merging the drm tree, today's linux-next build (powerpc
> ppc64_defconfig) produced these warnings:
>
> drivers/gpu/drm/udl/Kconfig:1:error: recursive dependency detected!
> drivers/gpu/drm/udl/Kconfig:1:  symbol DRM_UDL depends on USB_ARCH_HAS_HCD
> drivers/usb/Kconfig:76: symbol USB_ARCH_HAS_HCD depends on USB_SUPPORT
> drivers/usb/Kconfig:58: symbol USB_SUPPORT is selected by DRM_USB
> drivers/gpu/drm/Kconfig:22:     symbol DRM_USB is selected by DRM_UDL
> warning: (PPC_PS3) selects USB_OHCI_LITTLE_ENDIAN which has unmet direct dependencies (USB_SUPPORT && USB_OHCI_HCD)
> warning: (PPC_PS3 && PPC_CELLEB) selects USB_OHCI_BIG_ENDIAN_MMIO which has unmet direct dependencies (USB_SUPPORT && USB_OHCI_HCD)
> warning: (PPC_PS3 && PPC_CELLEB && USB_EHCI_HCD_PMC_MSP && XPS_USB_HCD_XILINX && USB_OCTEON_EHCI) selects USB_EHCI_BIG_ENDIAN_MMIO which has unmet direct dependencies (USB_SUPPORT && USB_EHCI_HCD && (PPC_CELLEB || PPC_PS3 || 440EPX || ARCH_IXP4XX || XPS_USB_HCD_XILINX || PPC_MPC512x || CPU_CAVIUM_OCTEON || PMC_MSP || SPARC_LEON || MIPS_SEAD3))
>
> The x86_64 allmodconfig produces these:
>
> drivers/gpu/drm/udl/Kconfig:1:error: recursive dependency detected!
> drivers/gpu/drm/udl/Kconfig:1:  symbol DRM_UDL depends on USB_ARCH_HAS_HCD
> drivers/usb/Kconfig:76: symbol USB_ARCH_HAS_HCD depends on USB_SUPPORT
> drivers/usb/Kconfig:58: symbol USB_SUPPORT is selected by DRM_USB
> drivers/gpu/drm/Kconfig:22:     symbol DRM_USB is selected by DRM_UDL
> warning: (MOUSE_APPLETOUCH && MOUSE_BCM5974 && MOUSE_SYNAPTICS_USB && JOYSTICK_XPAD && TABLET_USB_ACECAD && TABLET_USB_AIPTEK && TABLET_USB_HANWANG && TABLET_USB_KBTAB && TABLET_USB_WACOM && TOUCHSCREEN_USB_COMPOSITE && INPUT_ATI_REMOTE2 && INPUT_KEYSPAN_REMOTE && INPUT_POWERMATE && INPUT_YEALINK && INPUT_CM109 && RC_ATI_REMOTE && IR_IMON && IR_MCEUSB && IR_REDRAT3 && IR_STREAMZAP && IR_IGUANA && IR_TTUSBIR && DRM_USB) selects USB which has unmet direct dependencies (USB_SUPPORT && USB_ARCH_HAS_HCD)
>
> Maybe introduced by commit df0b34430072 ("drm/usb: select USB_SUPPORT in
> Kconfig"), maybe interacting with a commit 8f057d7bca54 ("gpu/mfd/usb:
> Fix USB randconfig problems") from Linus' tree (that added "depends on
> USB_ARCH_HAS_HCD" to "config DRM_USB" and "config DRM_UDL").
>
> I have left this mess for now, but it needs addressing.

I have sent a fix ("drm/udl: usb: Fix recursive Kconfig dependency")
for this mess and pinged airlied on IRC.
NOTE: I saw this when I merged drm(-intel){-fixes,next} into next-20120824.

- Sedat -

[1] https://patchwork.kernel.org/patch/1373391/

> --
> Cheers,
> Stephen Rothwell                    sfr@canb.auug.org.au

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

* Re: linux-next: build warnings after merge of the drm tree
  2012-09-04  3:58 Stephen Rothwell
@ 2012-09-04  5:31 ` Guenter Roeck
  2012-09-04  6:40 ` Sedat Dilek
  1 sibling, 0 replies; 25+ messages in thread
From: Guenter Roeck @ 2012-09-04  5:31 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Dave Airlie, linux-next, linux-kernel, Sachin Kamat, Greg Kroah-Hartman

On Tue, Sep 04, 2012 at 01:58:29PM +1000, Stephen Rothwell wrote:
> Hi Dave,
> 
> After merging the drm tree, today's linux-next build (powerpc
> ppc64_defconfig) produced these warnings:
> 
> drivers/gpu/drm/udl/Kconfig:1:error: recursive dependency detected!
> drivers/gpu/drm/udl/Kconfig:1:	symbol DRM_UDL depends on USB_ARCH_HAS_HCD
> drivers/usb/Kconfig:76:	symbol USB_ARCH_HAS_HCD depends on USB_SUPPORT
> drivers/usb/Kconfig:58:	symbol USB_SUPPORT is selected by DRM_USB
> drivers/gpu/drm/Kconfig:22:	symbol DRM_USB is selected by DRM_UDL
> warning: (PPC_PS3) selects USB_OHCI_LITTLE_ENDIAN which has unmet direct dependencies (USB_SUPPORT && USB_OHCI_HCD)
> warning: (PPC_PS3 && PPC_CELLEB) selects USB_OHCI_BIG_ENDIAN_MMIO which has unmet direct dependencies (USB_SUPPORT && USB_OHCI_HCD)
> warning: (PPC_PS3 && PPC_CELLEB && USB_EHCI_HCD_PMC_MSP && XPS_USB_HCD_XILINX && USB_OCTEON_EHCI) selects USB_EHCI_BIG_ENDIAN_MMIO which has unmet direct dependencies (USB_SUPPORT && USB_EHCI_HCD && (PPC_CELLEB || PPC_PS3 || 440EPX || ARCH_IXP4XX || XPS_USB_HCD_XILINX || PPC_MPC512x || CPU_CAVIUM_OCTEON || PMC_MSP || SPARC_LEON || MIPS_SEAD3))
> 
> The x86_64 allmodconfig produces these:
> 
> drivers/gpu/drm/udl/Kconfig:1:error: recursive dependency detected!
> drivers/gpu/drm/udl/Kconfig:1:	symbol DRM_UDL depends on USB_ARCH_HAS_HCD
> drivers/usb/Kconfig:76:	symbol USB_ARCH_HAS_HCD depends on USB_SUPPORT
> drivers/usb/Kconfig:58:	symbol USB_SUPPORT is selected by DRM_USB
> drivers/gpu/drm/Kconfig:22:	symbol DRM_USB is selected by DRM_UDL
> warning: (MOUSE_APPLETOUCH && MOUSE_BCM5974 && MOUSE_SYNAPTICS_USB && JOYSTICK_XPAD && TABLET_USB_ACECAD && TABLET_USB_AIPTEK && TABLET_USB_HANWANG && TABLET_USB_KBTAB && TABLET_USB_WACOM && TOUCHSCREEN_USB_COMPOSITE && INPUT_ATI_REMOTE2 && INPUT_KEYSPAN_REMOTE && INPUT_POWERMATE && INPUT_YEALINK && INPUT_CM109 && RC_ATI_REMOTE && IR_IMON && IR_MCEUSB && IR_REDRAT3 && IR_STREAMZAP && IR_IGUANA && IR_TTUSBIR && DRM_USB) selects USB which has unmet direct dependencies (USB_SUPPORT && USB_ARCH_HAS_HCD)
> 
> Maybe introduced by commit df0b34430072 ("drm/usb: select USB_SUPPORT in
> Kconfig"), maybe interacting with a commit 8f057d7bca54 ("gpu/mfd/usb:
> Fix USB randconfig problems") from Linus' tree (that added "depends on
> USB_ARCH_HAS_HCD" to "config DRM_USB" and "config DRM_UDL").
> 
Looks like it. I'll have a look once the tree is available.

Guenter

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

* linux-next: build warnings after merge of the drm tree
@ 2012-09-04  3:58 Stephen Rothwell
  2012-09-04  5:31 ` Guenter Roeck
  2012-09-04  6:40 ` Sedat Dilek
  0 siblings, 2 replies; 25+ messages in thread
From: Stephen Rothwell @ 2012-09-04  3:58 UTC (permalink / raw)
  To: Dave Airlie
  Cc: linux-next, linux-kernel, Sachin Kamat, Guenter Roeck,
	Greg Kroah-Hartman


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

Hi Dave,

After merging the drm tree, today's linux-next build (powerpc
ppc64_defconfig) produced these warnings:

drivers/gpu/drm/udl/Kconfig:1:error: recursive dependency detected!
drivers/gpu/drm/udl/Kconfig:1:	symbol DRM_UDL depends on USB_ARCH_HAS_HCD
drivers/usb/Kconfig:76:	symbol USB_ARCH_HAS_HCD depends on USB_SUPPORT
drivers/usb/Kconfig:58:	symbol USB_SUPPORT is selected by DRM_USB
drivers/gpu/drm/Kconfig:22:	symbol DRM_USB is selected by DRM_UDL
warning: (PPC_PS3) selects USB_OHCI_LITTLE_ENDIAN which has unmet direct dependencies (USB_SUPPORT && USB_OHCI_HCD)
warning: (PPC_PS3 && PPC_CELLEB) selects USB_OHCI_BIG_ENDIAN_MMIO which has unmet direct dependencies (USB_SUPPORT && USB_OHCI_HCD)
warning: (PPC_PS3 && PPC_CELLEB && USB_EHCI_HCD_PMC_MSP && XPS_USB_HCD_XILINX && USB_OCTEON_EHCI) selects USB_EHCI_BIG_ENDIAN_MMIO which has unmet direct dependencies (USB_SUPPORT && USB_EHCI_HCD && (PPC_CELLEB || PPC_PS3 || 440EPX || ARCH_IXP4XX || XPS_USB_HCD_XILINX || PPC_MPC512x || CPU_CAVIUM_OCTEON || PMC_MSP || SPARC_LEON || MIPS_SEAD3))

The x86_64 allmodconfig produces these:

drivers/gpu/drm/udl/Kconfig:1:error: recursive dependency detected!
drivers/gpu/drm/udl/Kconfig:1:	symbol DRM_UDL depends on USB_ARCH_HAS_HCD
drivers/usb/Kconfig:76:	symbol USB_ARCH_HAS_HCD depends on USB_SUPPORT
drivers/usb/Kconfig:58:	symbol USB_SUPPORT is selected by DRM_USB
drivers/gpu/drm/Kconfig:22:	symbol DRM_USB is selected by DRM_UDL
warning: (MOUSE_APPLETOUCH && MOUSE_BCM5974 && MOUSE_SYNAPTICS_USB && JOYSTICK_XPAD && TABLET_USB_ACECAD && TABLET_USB_AIPTEK && TABLET_USB_HANWANG && TABLET_USB_KBTAB && TABLET_USB_WACOM && TOUCHSCREEN_USB_COMPOSITE && INPUT_ATI_REMOTE2 && INPUT_KEYSPAN_REMOTE && INPUT_POWERMATE && INPUT_YEALINK && INPUT_CM109 && RC_ATI_REMOTE && IR_IMON && IR_MCEUSB && IR_REDRAT3 && IR_STREAMZAP && IR_IGUANA && IR_TTUSBIR && DRM_USB) selects USB which has unmet direct dependencies (USB_SUPPORT && USB_ARCH_HAS_HCD)

Maybe introduced by commit df0b34430072 ("drm/usb: select USB_SUPPORT in
Kconfig"), maybe interacting with a commit 8f057d7bca54 ("gpu/mfd/usb:
Fix USB randconfig problems") from Linus' tree (that added "depends on
USB_ARCH_HAS_HCD" to "config DRM_USB" and "config DRM_UDL").

I have left this mess for now, but it needs addressing.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

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

end of thread, back to index

Thread overview: 25+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-04-01  7:32 linux-next: build warnings after merge of the drm tree Stephen Rothwell
2021-04-21  6:30 ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2020-11-05  6:50 Stephen Rothwell
2020-11-15 23:44 ` Stephen Rothwell
2020-12-14 19:50   ` Stephen Rothwell
2020-12-15  2:47     ` Stephen Rothwell
2020-12-15  9:42       ` Daniel Vetter
2017-11-01  3:16 Stephen Rothwell
2017-11-01  9:58 ` Boris Brezillon
2017-05-19  2:07 Stephen Rothwell
2017-05-19 17:49 ` Eric Anholt
2017-05-25  1:49   ` Stephen Rothwell
2017-06-02  3:59     ` Stephen Rothwell
2017-06-02 21:05       ` Eric Anholt
2017-06-02 23:40         ` Stephen Rothwell
2017-06-03  0:45           ` Eric Anholt
2017-06-03  1:26             ` Stephen Rothwell
2017-02-23 23:27 Stephen Rothwell
2017-02-19 23:48 Stephen Rothwell
2012-10-04  2:21 Stephen Rothwell
2012-09-04  3:58 Stephen Rothwell
2012-09-04  5:31 ` Guenter Roeck
2012-09-04  6:40 ` Sedat Dilek
2012-09-04  8:22   ` Dave Airlie
2012-09-04  8:58     ` Sedat Dilek

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git