From: Jani Nikula <jani.nikula@intel.com>
To: kernel test robot <lkp@intel.com>, dri-devel@lists.freedesktop.org
Cc: oe-kbuild-all@lists.linux.dev, "David Airlie" <airlied@gmail.com>,
"Hamza Mahfooz" <hamza.mahfooz@amd.com>,
"Javier Martinez Canillas" <javierm@redhat.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Oleksandr Andrushchenko" <oleksandr_andrushchenko@epam.com>,
"Simon Ser" <contact@emersion.fr>,
"Simona Vetter" <simona@ffwll.ch>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
amd-gfx@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
nouveau@lists.freedesktop.org, xen-devel@lists.xenproject.org
Subject: Re: [PATCH 2/2] drm: remove driver date from struct drm_driver and all drivers
Date: Fri, 25 Oct 2024 12:47:35 +0300 [thread overview]
Message-ID: <878qucqzt4.fsf@intel.com> (raw)
In-Reply-To: <202410251351.r16zfufe-lkp@intel.com>
On Fri, 25 Oct 2024, kernel test robot <lkp@intel.com> wrote:
> Hi Jani,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on drm-misc/drm-misc-next]
> [also build test WARNING on next-20241024]
> [cannot apply to drm-exynos/exynos-drm-next shawnguo/for-next drm-xe/drm-xe-next linus/master v6.12-rc4]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Jani-Nikula/drm-remove-driver-date-from-struct-drm_driver-and-all-drivers/20241025-002344
> base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
> patch link: https://lore.kernel.org/r/20241024162240.2398664-2-jani.nikula%40intel.com
> patch subject: [PATCH 2/2] drm: remove driver date from struct drm_driver and all drivers
> config: i386-buildonly-randconfig-004-20241025 (https://download.01.org/0day-ci/archive/20241025/202410251351.r16zfufe-lkp@intel.com/config)
> compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241025/202410251351.r16zfufe-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202410251351.r16zfufe-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> drivers/accel/qaic/qaic_drv.c:211:10: error: 'const struct drm_driver' has no member named 'date'
> 211 | .date = "20190618",
> | ^~~~
>>> drivers/accel/qaic/qaic_drv.c:211:35: warning: initialization of 'unsigned int' from 'char *' makes integer from pointer without a cast [-Wint-conversion]
> 211 | .date = "20190618",
> | ^~~~~~~~~~
> drivers/accel/qaic/qaic_drv.c:211:35: note: (near initialization for 'qaic_accel_driver.driver_features')
> drivers/accel/qaic/qaic_drv.c:211:35: warning: initialized field overwritten [-Woverride-init]
> drivers/accel/qaic/qaic_drv.c:211:35: note: (near initialization for 'qaic_accel_driver.driver_features')
Hrmh, looks like I missed all of drivers/accel, I'll send an update
later.
BR,
Jani.
>
>
> vim +211 drivers/accel/qaic/qaic_drv.c
>
> c501ca23a6a306 Jeffrey Hugo 2023-03-27 205
> c501ca23a6a306 Jeffrey Hugo 2023-03-27 206 static const struct drm_driver qaic_accel_driver = {
> c501ca23a6a306 Jeffrey Hugo 2023-03-27 207 .driver_features = DRIVER_GEM | DRIVER_COMPUTE_ACCEL,
> c501ca23a6a306 Jeffrey Hugo 2023-03-27 208
> c501ca23a6a306 Jeffrey Hugo 2023-03-27 209 .name = QAIC_NAME,
> c501ca23a6a306 Jeffrey Hugo 2023-03-27 210 .desc = QAIC_DESC,
> c501ca23a6a306 Jeffrey Hugo 2023-03-27 @211 .date = "20190618",
> c501ca23a6a306 Jeffrey Hugo 2023-03-27 212
> c501ca23a6a306 Jeffrey Hugo 2023-03-27 213 .fops = &qaic_accel_fops,
> c501ca23a6a306 Jeffrey Hugo 2023-03-27 214 .open = qaic_open,
> c501ca23a6a306 Jeffrey Hugo 2023-03-27 215 .postclose = qaic_postclose,
> c501ca23a6a306 Jeffrey Hugo 2023-03-27 216
> c501ca23a6a306 Jeffrey Hugo 2023-03-27 217 .ioctls = qaic_drm_ioctls,
> c501ca23a6a306 Jeffrey Hugo 2023-03-27 218 .num_ioctls = ARRAY_SIZE(qaic_drm_ioctls),
> c501ca23a6a306 Jeffrey Hugo 2023-03-27 219 .gem_prime_import = qaic_gem_prime_import,
> c501ca23a6a306 Jeffrey Hugo 2023-03-27 220 };
> c501ca23a6a306 Jeffrey Hugo 2023-03-27 221
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-10-25 12:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 16:22 [PATCH 1/2] drm/xen: remove redundant initialization info print Jani Nikula
2024-10-24 16:22 ` [PATCH 2/2] drm: remove driver date from struct drm_driver and all drivers Jani Nikula
2024-10-24 16:29 ` Javier Martinez Canillas
2024-10-24 20:47 ` Alex Deucher
2024-10-24 21:34 ` Simon Ser
2024-10-25 5:44 ` kernel test robot
2024-10-25 9:47 ` Jani Nikula [this message]
2024-10-25 5:44 ` kernel test robot
2024-10-25 6:16 ` kernel 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=878qucqzt4.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=airlied@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=contact@emersion.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamza.mahfooz@amd.com \
--cc=javierm@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lkp@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oleksandr_andrushchenko@epam.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=ville.syrjala@linux.intel.com \
--cc=xen-devel@lists.xenproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.