From: "wsa@kernel.org" <wsa@kernel.org>
To: Mark Tomlinson <Mark.Tomlinson@alliedtelesis.co.nz>
Cc: "klaus.kudielka@gmail.com" <klaus.kudielka@gmail.com>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: Linux 5.11: i2c: Confusing error message
Date: Mon, 15 Mar 2021 21:39:43 +0100 [thread overview]
Message-ID: <20210315203943.GA4618@kunai> (raw)
In-Reply-To: <66fb30d6595ea18f60acf36e6b034e63ec7aac19.camel@alliedtelesis.co.nz>
[-- Attachment #1: Type: text/plain, Size: 405 bytes --]
> I admit that I added a "gpio" state to pinctrl for our board, so didn't
> see this error message. I think the easiest fix for this is to check that
> the gpio pinctrl state exists. e.g. something like:
It affects all drivers, so it should be fixed in the core. See:
http://patchwork.ozlabs.org/project/linux-i2c/patch/20210315115008.19110-1-wsa+renesas@sang-engineering.com/
from today.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-03-15 20:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1787a9ee-efae-7e4b-9e6f-d4bf532c6b63@gmail.com>
2021-03-15 10:10 ` Linux 5.11: i2c: Confusing error message Wolfram Sang
2021-03-15 20:18 ` Mark Tomlinson
2021-03-15 20:39 ` wsa [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=20210315203943.GA4618@kunai \
--to=wsa@kernel.org \
--cc=Mark.Tomlinson@alliedtelesis.co.nz \
--cc=klaus.kudielka@gmail.com \
--cc=linux-i2c@vger.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).