From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m32r: fix build warning about putc
Date: Tue, 28 Jun 2016 22:29:25 +0100 [thread overview]
Message-ID: <5772EC35.904@gmail.com> (raw)
In-Reply-To: <201606271139.pUB2VEVU%fengguang.wu@intel.com>
On Monday 27 June 2016 04:48 AM, kbuild test robot wrote:
> Hi,
>
> [auto build test WARNING on v4.7-rc5]
> [also build test WARNING on next-20160624]
> [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/Sudip-Mukherjee/m32r-fix-build-warning-about-putc/20160627-094312
> config: m32r-m32104ut_defconfig (attached as .config)
> compiler: m32r-linux-gcc (GCC) 4.9.0
> reproduce:
> wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # save the attached .config to linux build tree
> make.cross ARCH=m32r
>
> All warnings (new ones prefixed by >>):
>
> In file included from arch/m32r/boot/compressed/misc.c:25:0:
> arch/m32r/boot/compressed/m32r_sio.c: In function 'puts':
>>> arch/m32r/boot/compressed/m32r_sio.c:16:2: warning: suggest parentheses around assignment used as truth value [-Wparentheses]
> while (c = *s++)
> ^
This was fixed in v2 which was sent just after this patch was posted.
Regards
Sudip
prev parent reply other threads:[~2016-06-28 21:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-26 21:16 [PATCH] m32r: fix build warning about putc Sudip Mukherjee
2016-06-27 3:48 ` kbuild test robot
2016-06-28 21:29 ` Sudip Mukherjee [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=5772EC35.904@gmail.com \
--to=sudipm.mukherjee@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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.