From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
kernel test robot <lkp@intel.com>
Subject: Re: [linux-next:master 15112/15174] drivers/rtc/rtc-ds1307.c:1717:35: error: call to undeclared function 'i2c_client_get_device_id'; ISO C99 and later do not support implicit function declarations
Date: Thu, 22 Dec 2022 23:18:02 +0100 [thread overview]
Message-ID: <Y6TXmiGfTRsdhfEQ@mail.local> (raw)
In-Reply-To: <20221222220812.c5c5azlcl64ewkbc@pengutronix.de>
On 22/12/2022 23:08:12+0100, Uwe Kleine-König wrote:
> Hello Alexandre,
>
> On Thu, Dec 15, 2022 at 08:57:46AM +0100, Uwe Kleine-König wrote:
> > On Thu, Dec 15, 2022 at 01:31:15PM +0800, kernel test robot wrote:
> > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > > head: 459c73db4069c27c1d4a0e20d055b837396364b8
> > > commit: ad6d474d82dfb346573146d1bb0d818a720314fd [15112/15174] rtc: ds1307: Convert to i2c's .probe_new()
> > > config: hexagon-buildonly-randconfig-r004-20221214
> > > compiler: clang version 16.0.0 (https://github.com/llvm/llvm-project 98b13979fb05f3ed288a900deb843e7b27589e58)
> > > 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/next/linux-next.git/commit/?id=ad6d474d82dfb346573146d1bb0d818a720314fd
> > > git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> > > git fetch --no-tags linux-next master
> > > git checkout ad6d474d82dfb346573146d1bb0d818a720314fd
> > > # save the config file
> > > mkdir build_dir && cp config build_dir/.config
> > > COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=hexagon SHELL=/bin/bash drivers/rtc/
> > >
> > > If you fix the issue, kindly add following tag where applicable
> > > | Reported-by: kernel test robot <lkp@intel.com>
> > >
> > > Note: the linux-next/master HEAD 459c73db4069c27c1d4a0e20d055b837396364b8 builds fine.
> > > It may have been fixed somewhere.
> >
> > This is fixed by commit 662233731d66 ("i2c: core: Introduce
> > i2c_client_get_device_id helper function") which should be an ancestor
> > of the blamed commit.
> >
> > FTR: This is currently the only commit with this problem (i.e. a new
> > user of i2c_client_get_device_id that isn't an ancestor of
> > 662233731d66):
> >
> > $ git log --pretty=oneline --abbrev-commit --ancestry-path 662233731d66..next/master > l
> > $ git log --pretty=oneline --abbrev-commit linus/master..next/master -Si2c_client_get_device_id | grep -F -x -v -f l
> > ad6d474d82df rtc: ds1307: Convert to i2c's .probe_new()
> >
> > (If someone knows a single command to get this information, let me
> > know.)
> >
> > The idea was to pull
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/client_device_id_helper-immutable
> >
> > before applying the patch.
>
> The patch for ds1307 didn't make it into Linus' tree yet. Do you still
> have it on your radar for the next merge window? Would it help you if I
> resent it?
>
It is on my radar for the next merge window, no need to resend (this was
simpler for me)
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2022-12-22 22:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 5:31 [linux-next:master 15112/15174] drivers/rtc/rtc-ds1307.c:1717:35: error: call to undeclared function 'i2c_client_get_device_id'; ISO C99 and later do not support implicit function declarations kernel test robot
2022-12-15 7:57 ` Uwe Kleine-König
2022-12-22 22:08 ` Uwe Kleine-König
2022-12-22 22:18 ` Alexandre Belloni [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=Y6TXmiGfTRsdhfEQ@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=u.kleine-koenig@pengutronix.de \
/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).