From: kbuild test robot <lkp@intel.com>
To: Felix Brack <fb@ltec.ch>
Cc: kbuild-all@01.org, linux-fbdev@vger.kernel.org,
lee.jones@linaro.org, daniel.thompson@linaro.org,
jingoohan1@gmail.com, b.zolnierkie@samsung.com,
linux-kernel@vger.kernel.org, fb@ltec.ch
Subject: Re: [PATCH] backlight: otm3225a: add support for ORISE OTM3225A LCD SoC
Date: Sat, 23 Dec 2017 06:23:26 +0800 [thread overview]
Message-ID: <201712230655.iSiAPzhF%fengguang.wu@intel.com> (raw)
In-Reply-To: <1513792670-4114-1-git-send-email-fb@ltec.ch>
Hi Felix,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on backlight/for-backlight-next]
[also build test WARNING on v4.15-rc4 next-20171222]
[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/Felix-Brack/backlight-otm3225a-add-support-for-ORISE-OTM3225A-LCD-SoC/20171223-042842
base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/backlight.git for-backlight-next
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2017-12-22 22:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 17:57 [PATCH] backlight: otm3225a: add support for ORISE OTM3225A LCD SoC Felix Brack
2017-12-22 17:23 ` Jingoo Han
2017-12-22 17:33 ` Daniel Thompson
2017-12-27 10:23 ` Felix Brack
2017-12-27 10:16 ` Felix Brack
2017-12-22 22:23 ` kbuild test robot [this message]
2017-12-22 22:23 ` [RFC PATCH] backlight: otm3225a: otm3225a_ops can be static 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=201712230655.iSiAPzhF%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=b.zolnierkie@samsung.com \
--cc=daniel.thompson@linaro.org \
--cc=fb@ltec.ch \
--cc=jingoohan1@gmail.com \
--cc=kbuild-all@01.org \
--cc=lee.jones@linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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