From: Greg KH <gregkh@linuxfoundation.org>
To: Brajeswar Ghosh <brajeswar.linux@gmail.com>
Cc: kbuild test robot <lkp@intel.com>,
devel@driverdev.osuosl.org, tkjos@android.com,
sabyasachi.linux@gmail.com, linux-kernel@vger.kernel.org,
arve@android.com, kbuild-all@01.org, joel@joelfernandes.org,
maco@android.com, jrdr.linux@gmail.com
Subject: Re: [PATCH] drivers/android/binder.c: Remove duplicate header
Date: Fri, 9 Nov 2018 06:47:24 -0800 [thread overview]
Message-ID: <20181109144724.GA20089@kroah.com> (raw)
In-Reply-To: <201811092225.ABFKAgV4%fengguang.wu@intel.com>
On Fri, Nov 09, 2018 at 10:40:14PM +0800, kbuild test robot wrote:
> Hi Brajeswar,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on staging/staging-testing]
> [also build test ERROR on v4.20-rc1 next-20181109]
> [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/Brajeswar-Ghosh/drivers-android-binder-c-Remove-duplicate-header/20181109-154717
> config: i386-allmodconfig (attached as .config)
> compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=i386
>
> All errors (new ones prefixed by >>):
<snip>
Yeah, I was right :(
Always test-build your patches.
greg k-h
next prev parent reply other threads:[~2018-11-09 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 4:14 [PATCH] drivers/android/binder.c: Remove duplicate header Brajeswar Ghosh
2018-11-09 11:24 ` Greg KH
2018-11-09 14:40 ` kbuild test robot
2018-11-09 14:47 ` Greg KH [this message]
2018-11-10 6:28 ` Souptick Joarder
2018-11-10 1:51 ` kbuild test robot
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=20181109144724.GA20089@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arve@android.com \
--cc=brajeswar.linux@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=joel@joelfernandes.org \
--cc=jrdr.linux@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=maco@android.com \
--cc=sabyasachi.linux@gmail.com \
--cc=tkjos@android.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.