public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Jim Davis <jim.epost@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next <linux-next@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux@roeck-us.net, lm-sensors@lm-sensors.org
Subject: Re: randconfig build error with next-20141027, in drivers/hwmon/i5500_temp.c
Date: Mon, 27 Oct 2014 16:33:58 +0100	[thread overview]
Message-ID: <20141027163358.1754a025@endymion.delvare> (raw)
In-Reply-To: <CA+r1ZhiTncfpV9wekBK363OmJCHeCfYj6o9o7QkkHCR3H1VhXQ@mail.gmail.com>

Hi Jim,

On Mon, 27 Oct 2014 07:50:09 -0700, Jim Davis wrote:
> Building with the attached random configuration file,
> 
>   CC [M]  drivers/hwmon/i5500_temp.o
> drivers/hwmon/i5500_temp.c:145:1: warning: data definition has no type
> or storage class [enabled by default]
>  module_pci_driver(i5500_temp_driver);
>  ^
> drivers/hwmon/i5500_temp.c:145:1: error: type defaults to ‘int’ in
> declaration of ‘module_pci_driver’ [-Werror=implicit-int]
> drivers/hwmon/i5500_temp.c:145:1: warning: parameter names (without
> types) in function declaration [enabled by default]
> drivers/hwmon/i5500_temp.c:139:26: warning: ‘i5500_temp_driver’
> defined but not used [-Wunused-variable]
>  static struct pci_driver i5500_temp_driver = {
>                           ^
> cc1: some warnings being treated as errors
> make[2]: *** [drivers/hwmon/i5500_temp.o] Error 1

Thanks for the report. The driver should obviously depend on
CONFIG_PCI, not sure how I managed to miss that :( I'll fix it
immediately.

-- 
Jean Delvare
SUSE L3 Support

      reply	other threads:[~2014-10-27 15:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27 14:50 randconfig build error with next-20141027, in drivers/hwmon/i5500_temp.c Jim Davis
2014-10-27 15:33 ` Jean Delvare [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=20141027163358.1754a025@endymion.delvare \
    --to=jdelvare@suse.de \
    --cc=jim.epost@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lm-sensors@lm-sensors.org \
    --cc=sfr@canb.auug.org.au \
    /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