From: Wolfram Sang <wsa@kernel.org>
To: Aryan Srivastava <aryan.srivastava@alliedtelesis.co.nz>
Cc: rric@kernel.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org, Chris.Packham@alliedtelesis.co.nz
Subject: Re: [PATCH] i2c:thunderx:Add disabled node check
Date: Sun, 29 Oct 2023 18:11:49 +0100 [thread overview]
Message-ID: <ZT6SVZNUT/KPucdI@shikoro> (raw)
In-Reply-To: <20230711054147.506437-1-aryan.srivastava@alliedtelesis.co.nz>
[-- Attachment #1: Type: text/plain, Size: 355 bytes --]
On Tue, Jul 11, 2023 at 05:41:46PM +1200, Aryan Srivastava wrote:
> Add check for disabled nodes. These nodes should not be probed. Can
> result in logging for HW which is not present.
>
> Signed-off-by: Aryan Srivastava <aryan.srivastava@alliedtelesis.co.nz>
I am confused. This is a PCI driver, no? Why should we deal with DT
settings here?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-10-29 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 5:41 [PATCH] i2c:thunderx:Add disabled node check Aryan Srivastava
2023-10-29 17:11 ` Wolfram Sang [this message]
2023-10-29 21:47 ` Chris Packham
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=ZT6SVZNUT/KPucdI@shikoro \
--to=wsa@kernel.org \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=aryan.srivastava@alliedtelesis.co.nz \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rric@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