From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Daniel Vetter <daniel.vetter@ffwll•ch>,
intel-gfx@lists•freedesktop.org, dri-devel@lists•freedesktop.org
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: linux-next: build warnings after merge of the drm-misc tree
Date: Tue, 14 Jul 2015 13:05:03 +1000 [thread overview]
Message-ID: <20150714130503.0d1ef33a@canb.auug.org.au> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 4389 bytes --]
Hi all,
After merging the drm-misc tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:
drivers/gpu/drm/bochs/bochs_fbdev.c: In function 'bochsfb_create':
drivers/gpu/drm/bochs/bochs_fbdev.c:63:17: warning: unused variable 'device' [-Wunused-variable]
struct device *device = &dev->pdev->dev;
^
Caused by commit
394111a2b303 ("drm/boschs: Use new drm_fb_helper functions")
drivers/gpu/drm/cirrus/cirrus_fbdev.c: In function 'cirrusfb_create':
drivers/gpu/drm/cirrus/cirrus_fbdev.c:247:1: warning: label 'out_iounmap' defined but not used [-Wunused-label]
out_iounmap:
^
Caused by commit
fd6ab591ce15 ("drm/cirrus: Use new drm_fb_helper functions")
drivers/gpu/drm/ast/ast_fb.c: In function 'astfb_create':
drivers/gpu/drm/ast/ast_fb.c:196:17: warning: unused variable 'device' [-Wunused-variable]
struct device *device = &dev->pdev->dev;
^
Caused by commit
6f4900cd28c9 ("drm/ast: Use new drm_fb_helper functions")
drivers/gpu/drm/gma500/framebuffer.c: In function 'psbfb_create':
drivers/gpu/drm/gma500/framebuffer.c:346:17: warning: unused variable 'device' [-Wunused-variable]
struct device *device = &dev->pdev->dev;
^
Caused by commit
3b9a13e85365 ("drm/gma500: Use new drm_fb_helper functions")
drivers/gpu/drm/mgag200/mgag200_fb.c: In function 'mgag200fb_create':
drivers/gpu/drm/mgag200/mgag200_fb.c:232:1: warning: label 'out' defined but not used [-Wunused-label]
out:
^
drivers/gpu/drm/mgag200/mgag200_fb.c:169:17: warning: unused variable 'device' [-Wunused-variable]
struct device *device = &dev->pdev->dev;
^
Caused by commit
53ebb642ccba ("drm/mgag200: Use new drm_fb_helper functions")
drivers/gpu/drm/amd/amdgpu/amdgpu_fb.c: In function 'amdgpufb_create':
drivers/gpu/drm/amd/amdgpu/amdgpu_fb.c:206:9: warning: passing argument 1 of 'PTR_ERR' makes pointer from integer without a cast
ret = PTR_ERR(ret);
^
In file included from arch/x86/include/asm/processor.h:31:0,
from arch/x86/include/asm/thread_info.h:49,
from include/linux/thread_info.h:54,
from arch/x86/include/asm/preempt.h:6,
from include/linux/preempt.h:64,
from include/linux/spinlock.h:50,
from include/linux/seqlock.h:35,
from include/linux/time.h:5,
from include/linux/stat.h:18,
from include/linux/module.h:10,
from drivers/gpu/drm/amd/amdgpu/amdgpu_fb.c:26:
include/linux/err.h:28:33: note: expected 'const void *' but argument is of type 'int'
static inline long __must_check PTR_ERR(__force const void *ptr)
^
drivers/gpu/drm/amd/amdgpu/amdgpu_fb.c:182:17: warning: unused variable 'device' [-Wunused-variable]
struct device *device = &adev->pdev->dev;
^
drivers/gpu/drm/amd/amdgpu/amdgpu_fb.c: In function 'amdgpu_fbdev_destroy':
drivers/gpu/drm/amd/amdgpu/amdgpu_fb.c:283:18: warning: unused variable 'info' [-Wunused-variable]
struct fb_info *info;
^
Caused by commit
9d70561ba3b1 ("drm/amdgpu: Use new drm_fb_helper functions")
drivers/gpu/drm/udl/udl_fb.c: In function 'udlfb_create':
drivers/gpu/drm/udl/udl_fb.c:479:17: warning: unused variable 'device' [-Wunused-variable]
struct device *device = dev->dev;
^
Caused by commit
457959f2ed5f ("drm/udl: Use new drm_fb_helper functions")
drivers/gpu/drm/radeon/radeon_fb.c: In function 'radeonfb_create':
drivers/gpu/drm/radeon/radeon_fb.c:230:17: warning: unused variable 'device' [-Wunused-variable]
struct device *device = &rdev->pdev->dev;
^
Caused by commit
4bc29bb98bae ("drm/radeon: Use new drm_fb_helper functions")
drivers/gpu/drm/nouveau/nouveau_fbcon.c: In function 'nouveau_fbcon_create':
drivers/gpu/drm/nouveau/nouveau_fbcon.c:322:18: warning: unused variable 'pdev' [-Wunused-variable]
struct pci_dev *pdev = dev->pdev;
^
Caused by commit
237fc6452ca5 ("drm/nouveau: Use new drm_fb_helper functions")
I think "COMPILE TESTED ONLY" should at least include eliminating such
warnings ...
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists•freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-07-14 3:05 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 3:05 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-08-14 5:35 linux-next: build warnings after merge of the drm-misc tree Stephen Rothwell
2015-08-14 12:51 ` Thierry Reding
2021-01-15 1:23 Stephen Rothwell
2021-01-15 15:03 ` Nirmoy
2022-04-06 5:44 Stephen Rothwell
2022-04-06 5:51 ` Stephen Rothwell
2022-04-13 0:07 ` Stephen Rothwell
2022-06-11 8:21 Stephen Rothwell
2022-06-11 16:57 ` Doug Anderson
2023-03-14 3:15 Stephen Rothwell
2023-12-04 4:53 Stephen Rothwell
2024-03-26 5:12 Stephen Rothwell
2024-04-16 7:31 Stephen Rothwell
2024-04-16 8:25 ` Jocelyn Falempe
2024-08-01 6:03 Stephen Rothwell
2024-10-10 5:04 Stephen Rothwell
2024-10-10 5:09 Stephen Rothwell
2024-10-10 8:35 ` Thomas Hellström
2024-12-20 4:42 Stephen Rothwell
2025-01-14 5:41 ` Stephen Rothwell
2025-01-16 10:34 ` Tomi Valkeinen
2025-01-16 11:50 ` Maxime Ripard
2025-01-06 6:46 Stephen Rothwell
2025-01-14 5:43 ` Stephen Rothwell
2025-01-14 11:40 ` Dmitry Baryshkov
2025-01-14 12:06 ` Stephen Rothwell
2025-06-11 4:09 Stephen Rothwell
2025-08-01 4:34 ` Stephen Rothwell
2025-08-01 11:04 ` Dmitry Baryshkov
2025-06-18 5:13 Stephen Rothwell
2025-11-05 5:18 Stephen Rothwell
2025-11-10 2:24 Stephen Rothwell
2025-11-10 2:50 Stephen Rothwell
2025-12-16 0:56 Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150714130503.0d1ef33a@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=daniel.vetter@ffwll$(echo .)ch \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=intel-gfx@lists$(echo .)freedesktop.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox