From: Jeff LaBundy <jeff@labundy.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: robh+dt@kernel.org, linux-input@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 5/7] Input: iqs7222 - remove support for RF filter
Date: Thu, 23 Jun 2022 20:13:31 -0500 [thread overview]
Message-ID: <20220624011331.GA87950@nixie71> (raw)
In-Reply-To: <YrUN115qdy14sfEx@google.com>
Hi Dmitry,
On Thu, Jun 23, 2022 at 06:05:27PM -0700, Dmitry Torokhov wrote:
> On Wed, Jun 22, 2022 at 10:53:07PM -0500, Jeff LaBundy wrote:
> > The vendor has redacted the RF filter enable control; remove it from
>
> Did you mean "retracted" by chance?
I did mean redact, as in 'to censor,' as the field has since been
marked reserved in the datasheet since silicon was released.
That being said, I'm happy to re-spin with this stated explicitly
in case of poor word choice on my part.
>
> Thanks.
>
> --
> Dmitry
Kind regards,
Jeff LaBundy
next prev parent reply other threads:[~2022-06-24 1:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 3:53 [PATCH 0/7] Miscellaneous fixes for Azoteq IQS7222A/B/C Jeff LaBundy
2022-06-23 3:53 ` [PATCH 1/7] Input: iqs7222 - fortify slider event reporting Jeff LaBundy
2022-06-23 3:53 ` [PATCH 2/7] Input: iqs7222 - protect volatile registers Jeff LaBundy
2022-06-23 3:53 ` [PATCH 3/7] Input: iqs7222 - acknowledge reset before writing registers Jeff LaBundy
2022-06-23 3:53 ` [PATCH 4/7] Input: iqs7222 - handle reset during ATI Jeff LaBundy
2022-06-23 3:53 ` [PATCH 5/7] Input: iqs7222 - remove support for RF filter Jeff LaBundy
2022-06-24 1:05 ` Dmitry Torokhov
2022-06-24 1:13 ` Jeff LaBundy [this message]
2022-06-23 3:53 ` [PATCH 6/7] dt-bindings: input: iqs7222: Remove " Jeff LaBundy
2022-06-23 3:53 ` [PATCH 7/7] dt-bindings: input: iqs7222: Correct bottom speed step size Jeff LaBundy
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=20220624011331.GA87950@nixie71 \
--to=jeff@labundy.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--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).