From: "Jonas Mark (BT-FIR/ENG1)" <Mark.Jonas@de.bosch.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: "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>,
"andy.shevchenko@gmail.com" <andy.shevchenko@gmail.com>,
"ZHU Yi (BT-FIR/ENG1-Zhu)" <Yi.Zhu5@cn.bosch.com>,
"Jonas Mark (BT-FIR/ENG1)" <Mark.Jonas@de.bosch.com>
Subject: Re: [PATCH v5] Input: add bu21029 touch driver
Date: Wed, 13 Jun 2018 15:27:16 +0000 [thread overview]
Message-ID: <73b4ea3ce1aa453681fae87b7bad5cab@de.bosch.com> (raw)
Hello Dmitry,
> > [PATCH v5] Input: add bu21029 touch driver
> >
> > Add Rohm BU21029 resistive touch panel controller support with I2C
> > interface.
>
> Is the patch ready to be pushed upstream? Is there anything I still need to do?
I would like to kindly remind you of the BU21029 touch screen driver.
Could you please forward it to the mainline kernel?
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
next reply other threads:[~2018-06-13 15:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 15:27 Jonas Mark (BT-FIR/ENG1) [this message]
2018-06-13 22:20 ` [PATCH v5] Input: add bu21029 touch driver Dmitry Torokhov
2018-06-14 16:23 ` AW: " Jonas Mark (BT-FIR/ENG1)
-- strict thread matches above, loose matches on Subject: below --
2018-06-15 14:26 Jonas Mark (BT-FIR/ENG1)
2018-05-30 9:42 Jonas Mark (BT-FIR/ENG1)
2018-03-21 17:04 [PATCH] " Mark Jonas
2018-05-17 20:06 ` [PATCH v5] " Mark Jonas
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=73b4ea3ce1aa453681fae87b7bad5cab@de.bosch.com \
--to=mark.jonas@de.bosch.com \
--cc=Yi.Zhu5@cn.bosch.com \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hs@denx.de \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).