From: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Wolfram Sang <wsa@the-dreams.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
Luis Oliveira <Luis.Oliveira@synopsys.com>,
linux-next <linux-next@vger.kernel.org>,
linux-i2c <linux-i2c@vger.kernel.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Today's linux-next build fail on powerpc
Date: Mon, 10 Jul 2017 23:21:57 +0530 [thread overview]
Message-ID: <1499709117.19784.44.camel@abdul.in.ibm.com> (raw)
In-Reply-To: <CAHp75VdSgpviH9U1nh7HVL-t9kHHQeAdDSnAGjsXtFaXXTNnXQ@mail.gmail.com>
On Mon, 2017-07-10 at 18:17 +0300, Andy Shevchenko wrote:
> On Mon, Jul 10, 2017 at 5:37 PM, Abdul Haleem
> <abdhalee@linux.vnet.ibm.com> wrote:
> > On Fri, 2017-07-07 at 19:36 +0300, Andy Shevchenko wrote:
> >> On Thu, Jul 6, 2017 at 9:00 AM, Abdul Haleem
> >> <abdhalee@linux.vnet.ibm.com> wrote:
> >> > next-20170705 fails to build on powerpc with below errors.
> >> I had sent a fix yesterday. Had you chance to test it?
>
> > drivers/i2c/busses/i2c-designware-platdrv.c:331:6: error: implicit
> > declaration of function
> > ‘i2c_detect_slave_mode’ [-Werror=implicit-function-declaration]
> > if (i2c_detect_slave_mode(&pdev->dev))
> > ^
> > CC [M] fs/jffs2/scan.o
> >
> > Please point me to the correct patch you are referring to ?
>
> commit 8f1a357d41a22009150cf404b5aa5876efdb59b1
>
> i2c: Provide a stub for i2c_detect_slave_mode()
>
Thanks Andy for the fix, the patch fixes the build errors.
Machine booted with no issues.
Reported-and-tested-by: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
--
Regard's
Abdul Haleem
IBM Linux Technology Centre
prev parent reply other threads:[~2017-07-10 17:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 6:00 Today's linux-next build fail on powerpc Abdul Haleem
2017-07-07 16:36 ` Andy Shevchenko
2017-07-10 14:37 ` Abdul Haleem
2017-07-10 15:17 ` Andy Shevchenko
2017-07-10 17:51 ` Abdul Haleem [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=1499709117.19784.44.camel@abdul.in.ibm.com \
--to=abdhalee@linux.vnet.ibm.com \
--cc=Luis.Oliveira@synopsys.com \
--cc=andy.shevchenko@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sfr@canb.auug.org.au \
--cc=wsa@the-dreams.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).