From: Andrei Lalaev <andrey.lalaev@gmail.com>
To: dmitry.torokhov@gmail.com
Cc: andrey.lalaev@gmail.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, robh@kernel.org,
m.felsch@pengutronix.de
Subject: Re: [PATCH] Input: qt1050 - handle CHIP_ID reading error
Date: Tue, 25 Jun 2024 21:30:33 +0200 [thread overview]
Message-ID: <20240625193047.35564-1-andrey.lalaev@gmail.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 319 bytes --]
> But how did we get into the situation with the chip being missing?
In my case, this chip is a part of an external board.
So, for example, I see this message in the case of a bad cable connection.
Also, I prefer to see messages with error codes instead of random values from a stack :)
Best regards,
Andrei Lalaev
next reply other threads:[~2024-06-25 19:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 19:30 Andrei Lalaev [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-17 18:30 [PATCH] Input: qt1050 - handle CHIP_ID reading error Andrei Lalaev
2024-06-25 8:32 ` Marco Felsch
2024-06-25 16:14 ` Dmitry Torokhov
2024-06-25 19:35 ` Andrei Lalaev
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=20240625193047.35564-1-andrey.lalaev@gmail.com \
--to=andrey.lalaev@gmail.com \
--cc=Znrs5QVAuSjH5sCT@google.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=robh@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).