From: kernel test robot <lkp@intel.com>
To: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-bluetooth@vger.kernel.org
Subject: [bluetooth-next:master 138/152] drivers/bluetooth/btintel_pcie.h:569:2: warning: field within 'struct btintel_pcie_dump_range' is less aligned than 'union btintel_pcie_dump_range::(anonymous at drivers/bluetooth/btintel_pcie.h:569:2)' and is usually due to 'struct btintel_pcie_dump_ran...
Date: Sat, 24 Oct 2026 18:44:43 +0200 [thread overview]
Message-ID: <202610241822.0XYZitPj-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master
head: 47d4d9f67e92d56ef3965f2727f9c98a5a611368
commit: 20357497f44ee392117dd4a6eed8cd53d5abdbd7 [138/152] Bluetooth: btintel_pcie: Allow COMPILE_TEST without ACPI
config: arm-randconfig-r2111-20261024 (https://download.01.org/0day-ci/archive/20261024/202610241822.0XYZitPj-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project a808f8ea7fdc61ead417bfe55e8ef5f728776aeb)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261024/202610241822.0XYZitPj-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/202610241822.0XYZitPj-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from drivers/bluetooth/btintel_pcie.c:30:
>> drivers/bluetooth/btintel_pcie.h:569:2: warning: field within 'struct btintel_pcie_dump_range' is less aligned than 'union btintel_pcie_dump_range::(anonymous at drivers/bluetooth/btintel_pcie.h:569:2)' and is usually due to 'struct btintel_pcie_dump_range' being packed, which can lead to unaligned accesses [-Wunaligned-access]
569 | union {
| ^
1 warning generated.
vim +569 drivers/bluetooth/btintel_pcie.h
07e6bddb54b48e Kiran K 2025-03-03 563
9ea41cd5a63975 Chandrashekar Devegowda 2026-09-04 564 /* Per-fragment range descriptor for dump regions.
9ea41cd5a63975 Chandrashekar Devegowda 2026-09-04 565 * Binary-compatible with iwl_fw_ini_error_dump_range.
9ea41cd5a63975 Chandrashekar Devegowda 2026-09-04 566 */
9ea41cd5a63975 Chandrashekar Devegowda 2026-09-04 567 struct btintel_pcie_dump_range {
9ea41cd5a63975 Chandrashekar Devegowda 2026-09-04 568 __le32 range_data_size;
9ea41cd5a63975 Chandrashekar Devegowda 2026-09-04 @569 union {
9ea41cd5a63975 Chandrashekar Devegowda 2026-09-04 570 __le32 internal_base_addr;
9ea41cd5a63975 Chandrashekar Devegowda 2026-09-04 571 __le64 dram_base_addr;
9ea41cd5a63975 Chandrashekar Devegowda 2026-09-04 572 __le32 page_num;
9ea41cd5a63975 Chandrashekar Devegowda 2026-09-04 573 };
9ea41cd5a63975 Chandrashekar Devegowda 2026-09-04 574 __le32 data[];
9ea41cd5a63975 Chandrashekar Devegowda 2026-09-04 575 } __packed;
9ea41cd5a63975 Chandrashekar Devegowda 2026-09-04 576
:::::: The code at line 569 was first introduced by commit
:::::: 9ea41cd5a6397544620c185d52d23ec556e37d02 Bluetooth: btintel_pcie: unified decoder coredump format
:::::: TO: Chandrashekar Devegowda <chandrashekar.devegowda@intel.com>
:::::: CC: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-24 16:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202610241822.0XYZitPj-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.von.dentz@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox