From: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Max Staudt <max@enpas.org>
Subject: Re: [mkp-scsi:for-next 15/20] drivers/ata/pata_buddha.c:255:63: warning: missing braces around initializer
Date: Tue, 14 Jul 2026 07:05:46 +0200 [thread overview]
Message-ID: <alXCV8g17CBxcg5P@monoceros> (raw)
In-Reply-To: <202607140557.mhC5z0xE-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 3943 bytes --]
Hello,
On Tue, Jul 14, 2026 at 06:00:00AM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git for-next
> head: 4afcc9ed6a57b1b87e55366f9ff10c1c43b6d6e8
> commit: e73ba3d6ed03bf2afeecdfffc045b1ac98aeb1fc [15/20] scsi: zorro: Simplify storing pointers in device id struct
> config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20260714/202607140557.mhC5z0xE-lkp@intel.com/config)
> compiler: m68k-linux-gcc (GCC) 16.1.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260714/202607140557.mhC5z0xE-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/202607140557.mhC5z0xE-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> In file included from include/linux/bvec.h:10,
> from include/linux/blk_types.h:10,
> from include/linux/blkdev.h:9,
> from drivers/ata/pata_buddha.c:15:
> include/linux/highmem.h: In function 'clear_user_pages':
> include/linux/highmem.h:234:63: warning: parameter 'vaddr' set but not used [-Wunused-but-set-parameter=]
> 234 | static inline void clear_user_pages(void *addr, unsigned long vaddr,
> | ~~~~~~~~~~~~~~^~~~~
> drivers/ata/pata_buddha.c: At top level:
> >> drivers/ata/pata_buddha.c:255:63: warning: missing braces around initializer [-Wmissing-braces]
> 255 | static const struct zorro_device_id pata_buddha_zorro_tbl[] = {
> | ^
> 256 | { ZORRO_PROD_INDIVIDUAL_COMPUTERS_BUDDHA, BOARD_BUDDHA},
> | { }
> >> drivers/ata/pata_buddha.c:255:63: warning: missing braces around initializer [-Wmissing-braces]
> 255 | static const struct zorro_device_id pata_buddha_zorro_tbl[] = {
> | ^
> 256 | { ZORRO_PROD_INDIVIDUAL_COMPUTERS_BUDDHA, BOARD_BUDDHA},
> | { }
> 257 | { ZORRO_PROD_INDIVIDUAL_COMPUTERS_CATWEASEL, BOARD_CATWEASEL},
> | { }
> >> drivers/ata/pata_buddha.c:255:63: warning: missing braces around initializer [-Wmissing-braces]
> 255 | static const struct zorro_device_id pata_buddha_zorro_tbl[] = {
> | ^
> 256 | { ZORRO_PROD_INDIVIDUAL_COMPUTERS_BUDDHA, BOARD_BUDDHA},
> | { }
> 257 | { ZORRO_PROD_INDIVIDUAL_COMPUTERS_CATWEASEL, BOARD_CATWEASEL},
> | { }
> drivers/ata/pata_buddha.c: In function 'pata_buddha_late_init':
> drivers/ata/pata_buddha.c:284:59: warning: missing braces around initializer [-Wmissing-braces]
> 284 | static struct zorro_device_id xsurf_ent = {
> | ^
> 285 | ZORRO_PROD_INDIVIDUAL_COMPUTERS_X_SURF, BOARD_XSURF
> | {
> 286 | };
> | }
The problem here is that patch #6 of
https://lore.kernel.org/all/cover.1779803053.git.u.kleine-koenig@baylibre.com/
was picked up, but patch #1 wasn't, maybe due to my confusion when
describing the merge plan.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-07-14 5:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 22:00 [mkp-scsi:for-next 15/20] drivers/ata/pata_buddha.c:255:63: warning: missing braces around initializer kernel test robot
2026-07-14 5:05 ` Uwe Kleine-König (The Capable Hub) [this message]
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=alXCV8g17CBxcg5P@monoceros \
--to=u.kleine-koenig@baylibre.com \
--cc=geert@linux-m68k.org \
--cc=lkp@intel.com \
--cc=martin.petersen@oracle.com \
--cc=max@enpas.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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.