Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1650109 > unrolled thread

Re: linux-next: build warnings after merge of the drm tree

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: linux-next: build warnings after merge of the drm tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-05-25 03:50 +0200
    Re: linux-next: build warnings after merge of the drm tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-06-02 06:00 +0200
      Re: linux-next: build warnings after merge of the drm tree Eric Anholt <eric@anholt.net> - 2017-06-02 23:10 +0200
        Re: linux-next: build warnings after merge of the drm tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-06-03 01:50 +0200
          Re: linux-next: build warnings after merge of the drm tree Eric Anholt <eric@anholt.net> - 2017-06-03 02:50 +0200
            Re: linux-next: build warnings after merge of the drm tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-06-03 03:30 +0200

#1650109 — Re: linux-next: build warnings after merge of the drm tree

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

[toc] | [next] | [standalone]

#1655883

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

[toc] | [prev] | [next] | [standalone]

#1656550

[Multipart message — attachments visible in raw view] — view raw

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.

[toc] | [prev] | [next] | [standalone]

#1656632

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

[toc] | [prev] | [next] | [standalone]

#1656650

[Multipart message — attachments visible in raw view] — view raw

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.

[toc] | [prev] | [next] | [standalone]

#1656656

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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web