From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Lukasz Majewski <lukma@denx.de>
Cc: Lee Jones <lee.jones@linaro.org>,
linux-kernel@vger.kernel.org,
Sascha Hauer <s.hauer@pengutronix.de>,
Enrico Weigelt <info@metux.net>,
Thomas Gleixner <tglx@linutronix.de>,
Kate Stewart <kstewart@linuxfoundation.org>,
linux-input@vger.kernel.org
Subject: Re: [PATCH v2 2/3] input: touchscreen mc13xxx: Make platform data optional
Date: Mon, 15 Jul 2019 11:27:57 -0700 [thread overview]
Message-ID: <20190715182757.GA136092@dtor-ws> (raw)
In-Reply-To: <20190715104344.3f17b660@jawa>
On Mon, Jul 15, 2019 at 10:43:44AM +0200, Lukasz Majewski wrote:
> Hi Dmitry,
>
> Thank you for your reply.
>
> > On Fri, Jul 12, 2019 at 12:23:45AM +0200, Lukasz Majewski wrote:
> > > From: Sascha Hauer <s.hauer@pengutronix.de>
> > >
> > > The platform data once was optional, make it optional again. This
> > > is a first step towards device tree support for the mc13xxx
> > > touchscreen driver.
> >
> > I would prefer seeing it together with patches introducing device tree
> > support.
>
> Ok, I will merge this patch to patch 3/3.
Uh, I must be missing something, but I do not see anything dedicated to
device tree handling in 3/3...
Thanks.
--
Dmitry
next prev parent reply other threads:[~2019-07-15 18:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 22:23 [PATCH v2 0/3] mfd: mc13xxx: Fixes and enhancements for NXP's mc34708 Lukasz Majewski
2019-07-11 22:23 ` [PATCH v2 1/3] mfd: mc13xxx: Add mc34708 adc support Lukasz Majewski
2019-07-11 22:23 ` [PATCH v2 2/3] input: touchscreen mc13xxx: Make platform data optional Lukasz Majewski
2019-07-15 7:10 ` Dmitry Torokhov
2019-07-15 8:43 ` Lukasz Majewski
2019-07-15 18:27 ` Dmitry Torokhov [this message]
2019-07-16 7:02 ` Lukasz Majewski
2019-07-11 22:23 ` [PATCH v2 3/3] input: touchscreen mc13xxx: Add mc34708 support Lukasz Majewski
2019-07-15 7:07 ` Dmitry Torokhov
2019-07-15 9:13 ` Lukasz Majewski
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=20190715182757.GA136092@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=info@metux.net \
--cc=kstewart@linuxfoundation.org \
--cc=lee.jones@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukma@denx.de \
--cc=s.hauer@pengutronix.de \
--cc=tglx@linutronix.de \
/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).