From: kbuild test robot <fengguang.wu@intel.com>
To: Ilia Mirkin <imirkin@alum.mit.edu>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Ben Skeggs <bskeggs@redhat.com>, David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Thierry Reding <treding@nvidia.com>,
Jani Nikula <jani.nikula@intel.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
dri-devel@lists.freedesktop.org
Subject: drivers/gpu/drm/nouveau/nouveau_connector.c:60:5: sparse: symbol 'nouveau_hdmimhz' was not declared. Should it be static?
Date: Sat, 19 Mar 2016 22:17:14 +0800 [thread overview]
Message-ID: <201603192240.bx0vLALq%fengguang.wu@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 6b5f04b6cf8ebab9a65d9c0026c650bb2538fd0f
commit: 1a0c96c075bb4517d4ce4fb6750ee0a3cf38714c drm/nouveau/kms: allow 225/297MHz pixel clocks for HDMI on Fermi/Kepler
date: 10 weeks ago
reproduce:
# apt-get install sparse
git checkout 1a0c96c075bb4517d4ce4fb6750ee0a3cf38714c
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/nouveau/nouveau_connector.c:60:5: sparse: symbol 'nouveau_hdmimhz' was not declared. Should it be static?
drivers/gpu/drm/nouveau/nouveau_connector.c:1081:29: sparse: cast to restricted __le16
drivers/gpu/drm/nouveau/nouveau_connector.c:1083:39: sparse: cast to restricted __le16
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next reply other threads:[~2016-03-19 14:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-19 14:17 kbuild test robot [this message]
2016-03-19 14:17 ` [RFC PATCH linus] drm/nouveau/kms: nouveau_hdmimhz can be static kbuild test robot
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=201603192240.bx0vLALq%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=airlied@linux.ie \
--cc=bskeggs@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=imirkin@alum.mit.edu \
--cc=jani.nikula@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=treding@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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
all inboxes | Powered by JetHome®