From: Mauro Salvini <mauro.salvini@smigroup.net>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-input@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: input: tsc2005: fix vio-supply property
Date: Wed, 12 Jul 2017 14:08:34 +0200 [thread overview]
Message-ID: <1499861314.2301.4.camel@smigroup.net> (raw)
In-Reply-To: <20170712080111.7094-1-mauro.salvini@smigroup.net>
On Wed, 2017-07-12 at 10:01 +0200, Mauro Salvini wrote:
> tsc2005 documentation reports that vio-supply property is
> optional, but
> actually this property is required (driver fails with error if not
> present)
Hi,
completely forget my previous patch: I missed some commits (especially
f7bf6f58675a76c08e6e) and I wrongly deduced from driver probe fail that
vio-supply property must be required.
Sorry for the noise.
Mauro
prev parent reply other threads:[~2017-07-12 12:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 8:01 [PATCH] dt-bindings: input: tsc2005: fix vio-supply property Mauro Salvini
2017-07-12 12:08 ` Mauro Salvini [this message]
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=1499861314.2301.4.camel@smigroup.net \
--to=mauro.salvini@smigroup.net \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@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).