mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jonas Mark (BT-FIR/ENG1)" <Mark.Jonas@de.bosch.com>
To: kbuild test robot <lkp@intel.com>
Cc: "kbuild-all@01.org" <kbuild-all@01.org>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"hs@denx.de" <hs@denx.de>,
	"Jonas Mark (BT-FIR/ENG1)" <Mark.Jonas@de.bosch.com>,
	"ZHANG Kevin (BT-FIR/ENG1-Zhu)" <Kevin.Zhang3@cn.bosch.com>,
	"RUAN Tingquan (BT-FIR/ENG1-Zhu)" <Tingquan.Ruan@cn.bosch.com>,
	"zhuyi882004@126.com" <zhuyi882004@126.com>
Subject: Re: [PATCH v3] Input: add bu21029 touch driver
Date: Mon, 18 Jun 2018 09:35:40 +0000	[thread overview]
Message-ID: <d790eaf934274cc6a489c177d1f42674@de.bosch.com> (raw)

Hi kbuild test robot,

> Thank you for the patch! Perhaps something to improve:
> 
> [auto build test WARNING on v4.17-rc4]
> [also build test WARNING on next-20180615]
> [cannot apply to input/next]
> [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/Mark-Jonas/Input-add-bu21029-
> touch-driver/20180512-091305
> reproduce:
>         # apt-get install sparse
>         make ARCH=x86_64 allmodconfig
>         make C=1 CF=-D__CHECK_ENDIAN__
> 
> 
> sparse warnings: (new ones prefixed by >>)
> 
> >> drivers/input/touchscreen/bu21029_ts.c:293:13: sparse: restricted __be16
> degrades to integer
[..]
>    288		if (error < 0) {
>    289			dev_err(&i2c->dev, "failed to read HW ID\n");
>    290			goto out;
>    291		}
>    292
>  > 293		if (cpu_to_be16(hwid) != SUPPORTED_HWID) {
>    294			dev_err(&i2c->dev, "unsupported HW ID 0x%x\n", hwid);
>    295			error = -ENODEV;
>    296			goto out;
>    297		}

Thank you for your effort. The reported problem was already fixed.
Please have a look at the most recent v5 patch posted on this list.

Greetings,
Mark

 Mark Jonas

Building Technologies, Panel Software Fire (BT-FIR/ENG1) 
Bosch Sicherheitssysteme GmbH | Postfach 11 11 | 85626 Grasbrunn | GERMANY | www.boschsecurity.com

Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart HRB 23118 
Aufsichtsratsvorsitzender: Stefan Hartung; Geschäftsführung: Gert van Iperen, Andreas Bartz, Thomas Quante, Bernhard Schuster 


             reply	other threads:[~2018-06-18  9:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-18  9:35 Jonas Mark (BT-FIR/ENG1) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-03-21 17:04 [PATCH] " Mark Jonas
2018-05-11 14:22 ` [PATCH v3] " Mark Jonas
2018-05-13 14:56   ` Andy Shevchenko
2018-05-16 13:24     ` AW: " Jonas Mark (BT-FIR/ENG1)
2018-05-16 17:43       ` Dmitry Torokhov
2018-06-17 19:19   ` 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=d790eaf934274cc6a489c177d1f42674@de.bosch.com \
    --to=mark.jonas@de.bosch.com \
    --cc=Kevin.Zhang3@cn.bosch.com \
    --cc=Tingquan.Ruan@cn.bosch.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hs@denx.de \
    --cc=kbuild-all@01.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=zhuyi882004@126.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®