From: Jonathan Richardson <jonathar@broadcom.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Dmitry Torokhov <dtor@google.com>,
Anatol Pomazau <anatol@google.com>,
Scott Branden <sbranden@broadcom.com>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Ray Jui <rjui@broadcom.com>,
<linux-kernel@vger.kernel.org>, <linux-input@vger.kernel.org>,
bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
<devicetree@vger.kernel.org>, "Joe Perches" <joe@perches.com>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
"Kumar Gala" <galak@codeaurora.org>
Subject: Re: [PATCH v5 1/2] Input: touchscreen-iproc: Add Broadcom iProc touchscreen driver
Date: Mon, 23 Mar 2015 10:57:05 -0700 [thread overview]
Message-ID: <551053F1.7070308@broadcom.com> (raw)
In-Reply-To: <20150322042413.GB40622@dtor-ws>
On 15-03-21 09:24 PM, Dmitry Torokhov wrote:
> Hi Jonathan,
>
> On Fri, Mar 20, 2015 at 05:57:25PM -0700, Jonathan Richardson wrote:
>> +config TOUCHSCREEN_IPROC
>> + tristate "IPROC touch panel driver support"
>
> I think this should depend on ARCH_BCM_IPROC || COMPILE_TEST, right?
>
> (No need to resubmit).
Hi Dmitry. That is correct - thanks.
>
> Thanks.
>
next prev parent reply other threads:[~2015-03-23 17:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-21 0:57 [PATCH v5 0/2] Add support for Broadcom iProc touchscreen Jonathan Richardson
2015-03-21 0:57 ` [PATCH v5 1/2] Input: touchscreen-iproc: Add Broadcom iProc touchscreen driver Jonathan Richardson
2015-03-22 4:24 ` Dmitry Torokhov
2015-03-23 17:57 ` Jonathan Richardson [this message]
2015-03-23 18:05 ` Dmitry Torokhov
2015-03-23 10:14 ` Bo Shen
2015-03-23 16:01 ` Dmitry Torokhov
2015-03-21 0:57 ` [PATCH v5 2/2] Input: touchscreen-iproc: add device tree bindings Jonathan Richardson
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=551053F1.7070308@broadcom.com \
--to=jonathar@broadcom.com \
--cc=anatol@google.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=dtor@google.com \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=joe@perches.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.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