From: Chanwoo Choi <cw00.choi@samsung.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
MyungJoo Ham <myungjoo.ham@samsung.com>
Subject: Re: Build regressions/improvements in v3.17
Date: Tue, 07 Oct 2014 18:36:44 +0900 [thread overview]
Message-ID: <5433B42C.2090902@samsung.com> (raw)
In-Reply-To: <CAMuHMdWCTfJWWdeHSh3jOJx+9CCGfsONrR6X4vew4j5cULUpzg@mail.gmail.com>
Dear Geert,
On 10/07/2014 03:39 AM, Geert Uytterhoeven wrote:
> On Mon, Oct 6, 2014 at 8:28 PM, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>> JFYI, when comparing v3.17[1] to v3.17-rc7[3], the summaries are:
>> - build errors: +12/-6
>
> + /scratch/kisskb/src/drivers/base/regmap/regmap-i2c.c: error:
> implicit declaration of function 'i2c_check_functionality'
> [-Werror=implicit-function-declaration]: => 117:2
> + /scratch/kisskb/src/drivers/base/regmap/regmap-i2c.c: error:
> implicit declaration of function 'i2c_master_send'
> [-Werror=implicit-function-declaration]: => 96:2
> + /scratch/kisskb/src/drivers/base/regmap/regmap-i2c.c: error:
> implicit declaration of function 'i2c_smbus_read_byte_data'
> [-Werror=implicit-function-declaration]: => 28:2
> + /scratch/kisskb/src/drivers/base/regmap/regmap-i2c.c: error:
> implicit declaration of function 'i2c_smbus_read_word_data'
> [-Werror=implicit-function-declaration]: => 64:2
> + /scratch/kisskb/src/drivers/base/regmap/regmap-i2c.c: error:
> implicit declaration of function 'i2c_smbus_write_byte_data'
> [-Werror=implicit-function-declaration]: => 46:2
> + /scratch/kisskb/src/drivers/base/regmap/regmap-i2c.c: error:
> implicit declaration of function 'i2c_smbus_write_word_data'
> [-Werror=implicit-function-declaration]: => 82:2
> + /scratch/kisskb/src/drivers/base/regmap/regmap-i2c.c: error:
> implicit declaration of function 'i2c_transfer'
> [-Werror=implicit-function-declaration]: => 130:2
> + /scratch/kisskb/src/drivers/extcon/extcon-sm5502.c: error:
> implicit declaration of function 'i2c_add_driver'
> [-Werror=implicit-function-declaration]: => 718:2
>
> x86_64-randconfig
>
> Fix available, even promised by the maintainer to be in 3.17-rc2:
I'm so sorry, I didn't send this patch to fix this issue in 3.17-rc2.
This issue will be fixed on 3.18-rc1. This patch was merged and you can check it as following:
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=0746d5d31f61721bf3e4ab84d75fac08d03e2a9a
Best Regards,
Chanwoo Choi
>
> https://lkml.org/lkml/2014/8/20/874
>
>> [1] http://kisskb.ellerman.id.au/kisskb/head/7938/ (118 out of 119 configs)
>> [3] http://kisskb.ellerman.id.au/kisskb/head/7921/ (all 119 configs)
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
prev parent reply other threads:[~2014-10-07 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 18:28 Build regressions/improvements in v3.17 Geert Uytterhoeven
2014-10-06 18:39 ` Geert Uytterhoeven
2014-10-07 9:36 ` Chanwoo Choi [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=5433B42C.2090902@samsung.com \
--to=cw00.choi@samsung.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.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).