public inbox for linux-hwmon@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: "Václav Kubernát" <kubernat@cesnet.cz>
Cc: kernel test robot <lkp@intel.com>,
	kbuild-all@lists.01.org, linux-hwmon@vger.kernel.org
Subject: Re: [hwmon:hwmon-next 33/33] drivers/hwmon/pmbus/fsp-3y.c:204:48: warning: missing braces around initializer
Date: Thu, 15 Apr 2021 10:52:04 -0700	[thread overview]
Message-ID: <20210415175204.GC30478@roeck-us.net> (raw)
In-Reply-To: <CABKa3npWANE5EQE+bTUZ02ngDMT36kGsLO-8kdf8oroba7kjWw@mail.gmail.com>

On Thu, Apr 15, 2021 at 06:34:41PM +0200, Václav Kubernát wrote:
> Hello.
> 
> I received this email only after I submitted the PSU patch. I'm not
> sure what I should do. Also, I don't understand the warning, I don't
> know where the braces are missing.
> 

It wanted { } to terminate the list instead of { 0 }. Or, of course,
{NULL, 0}, but that would just add unnecessary compexity.

I fixed it up, no need to resend.

Guenter

> Václav
> 
> st 14. 4. 2021 v 17:11 odesílatel kernel test robot <lkp@intel.com> napsal:
> >
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-next
> > head:   f0af35c3a1254fc0cca601cdc4f228b9ad24a2a4
> > commit: f0af35c3a1254fc0cca601cdc4f228b9ad24a2a4 [33/33] hwmon: Add driver for fsp-3y PSUs and PDUs
> > config: arc-allyesconfig (attached as .config)
> > compiler: arceb-elf-gcc (GCC) 9.3.0
> > reproduce (this is a W=1 build):
> >         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> >         chmod +x ~/bin/make.cross
> >         # https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git/commit/?id=f0af35c3a1254fc0cca601cdc4f228b9ad24a2a4
> >         git remote add hwmon https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git
> >         git fetch --no-tags hwmon hwmon-next
> >         git checkout f0af35c3a1254fc0cca601cdc4f228b9ad24a2a4
> >         # save the attached .config to linux build tree
> >         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross W=1 ARCH=arc
> >
> > If you fix the issue, kindly add following tag as appropriate
> > Reported-by: kernel test robot <lkp@intel.com>
> >
> > All warnings (new ones prefixed by >>):
> >
> > >> drivers/hwmon/pmbus/fsp-3y.c:204:48: warning: missing braces around initializer [-Wmissing-braces]
> >      204 | static const struct i2c_device_id fsp3y_id[] = {
> >          |                                                ^
> >    ......
> >      207 |  {0}
> >          |   {}
> >
> >
> > vim +204 drivers/hwmon/pmbus/fsp-3y.c
> >
> >    203
> >  > 204  static const struct i2c_device_id fsp3y_id[] = {
> >    205          {"ym2151e", ym2151e},
> >    206          {"yh5151e", yh5151e},
> >    207          {0}
> >    208  };
> >    209
> >
> > ---
> > 0-DAY CI Kernel Test Service, Intel Corporation
> > https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

      reply	other threads:[~2021-04-15 17:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-14 15:11 [hwmon:hwmon-next 33/33] drivers/hwmon/pmbus/fsp-3y.c:204:48: warning: missing braces around initializer kernel test robot
2021-04-15 16:34 ` Václav Kubernát
2021-04-15 17:52   ` Guenter Roeck [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=20210415175204.GC30478@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=kbuild-all@lists.01.org \
    --cc=kubernat@cesnet.cz \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=lkp@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