From: Dan Carpenter <dan.carpenter@oracle.com>
To: hari prasath <gehariprasath@gmail.com>
Cc: kbuild test robot <lkp@intel.com>,
devel@driverdev.osuosl.org, Derek Robson <robsonde@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Joseph Wright <rjosephwright@gmail.com>,
linux@wolf-entwicklungen.de, kbuild-all@01.org,
Colin Ian King <colin.king@canonical.com>
Subject: Re: [PATCH] Remove explicit return type cast
Date: Thu, 3 Aug 2017 16:23:07 +0300 [thread overview]
Message-ID: <20170803132307.vm64tfvcxaurjmku@mwanda> (raw)
In-Reply-To: <CAHHWPbfS7=uySOscSqTM_jrVhchjoHWPAJ+mtUs+RK5ThYnp1w@mail.gmail.com>
On Thu, Aug 03, 2017 at 06:23:54PM +0530, hari prasath wrote:
> On 3 August 2017 at 11:52, kbuild test robot <lkp@intel.com> wrote:
> > Hi Hari,
> >
> > [auto build test WARNING on staging/staging-testing]
> > [also build test WARNING on next-20170802]
> > [cannot apply to v4.13-rc3]
> > [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
> >
> > url: https://github.com/0day-ci/linux/commits/Hari-Prasath/Remove-explicit-return-type-cast/20170803-080312
> > config: blackfin-allyesconfig (attached as .config)
> > compiler: bfin-uclinux-gcc (GCC) 6.2.0
> > reproduce:
> > wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> > chmod +x ~/bin/make.cross
> > # save the attached .config to linux build tree
> > make.cross ARCH=blackfin
> >
>
> >> I tried these steps, it's giving me build error as below.
>
You don't need to cross compile on blackfin to get the warning. Just
use the normal compiler.
regards,
dan carpenter
next prev parent reply other threads:[~2017-08-03 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 12:51 Hari Prasath
2017-08-03 6:22 ` kbuild test robot
2017-08-03 12:53 ` hari prasath
2017-08-03 13:23 ` Dan Carpenter [this message]
2017-08-08 12:59 ` hari prasath
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=20170803132307.vm64tfvcxaurjmku@mwanda \
--to=dan.carpenter@oracle.com \
--cc=colin.king@canonical.com \
--cc=devel@driverdev.osuosl.org \
--cc=gehariprasath@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@wolf-entwicklungen.de \
--cc=lkp@intel.com \
--cc=rjosephwright@gmail.com \
--cc=robsonde@gmail.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
all inboxes | Powered by JetHome®