From: Mark Brown <broonie@kernel.org>
To: kernel test robot <yujie.liu@intel.com>
Cc: Matti Vaittinen <mazziesaccount@gmail.com>,
Cristian Marussi <cristian.marussi@arm.com>,
clang-built-linux@googlegroups.com, kbuild-all@lists.01.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [kbuild] drivers/regulator/bd718x7-regulator.c:531:8: warning: Excessive padding in 'struct bd718xx_regulator_data' (8 padding bytes, where 0 is optimal).
Date: Thu, 19 Aug 2021 16:23:53 +0100 [thread overview]
Message-ID: <20210819152353.GN4177@sirena.org.uk> (raw)
In-Reply-To: <422ade1b-8e88-d6dc-ae4e-799e729932b7@intel.com>
[-- Attachment #1: Type: text/plain, Size: 466 bytes --]
On Thu, Aug 19, 2021 at 10:49:13PM +0800, kernel test robot wrote:
> Sorry for bothering, we'll ignore struct padding warnings next time.
I think the warnings are useful, it's just that they're not important
for all structs. If the struct was getting allocated a lot it could be
pointing out an issue that makes a real difference. I'm not sure it s
realistic for automation to figure it out for itself so it's better to
send them even if they get ignored a lot.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-08-19 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202108172206.9cbgvI53-lkp@intel.com>
2021-08-19 3:24 ` [kbuild] drivers/regulator/bd718x7-regulator.c:531:8: warning: Excessive padding in 'struct bd718xx_regulator_data' (8 padding bytes, where 0 is optimal) kernel test robot
2021-08-19 5:34 ` Matti Vaittinen
2021-08-19 11:37 ` Mark Brown
2021-08-19 14:49 ` kernel test robot
2021-08-19 15:23 ` Mark Brown [this message]
2021-08-21 4:38 ` 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=20210819152353.GN4177@sirena.org.uk \
--to=broonie@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=cristian.marussi@arm.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--cc=yujie.liu@intel.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;
as well as URLs for NNTP newsgroup(s).