From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-renesas-soc@vger.kernel.org
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
openbmc@lists.ozlabs.org
Subject: Re: [PATCH v2 0/3] i2c: create debugfs entry per adapter
Date: Tue, 19 Dec 2023 13:42:41 +0100 [thread overview]
Message-ID: <ZYGPwYPW0w20RCet@shikoro> (raw)
In-Reply-To: <20231112225444.4487-1-wsa+renesas@sang-engineering.com>
[-- Attachment #1: Type: text/plain, Size: 789 bytes --]
On Sun, Nov 12, 2023 at 05:54:40PM -0500, Wolfram Sang wrote:
> Two drivers already implement custom debugfs handling for their
> i2c_adapter and more will come. So, let the core create a debugfs
> directory per adapter and pass that to drivers for their debugfs files.
> Convert the two existing users as well. Tested on a Renesas Lager board
> with the i2c-gpio driver. npcm7xx was tested using QEMU with the
> quanta-gsj target.
>
> Changes since v1:
> * rebased to something close to 6.7-rc1 which includes i2c/for-mergewindow
> * tested npcm7xx with QEMU
>
> Wolfram Sang (3):
> i2c: create debugfs entry per adapter
> i2c: gpio: move to per-adapter debugfs directory
> i2c: npcm7xx: move to per-adapter debugfs directory
>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-12-19 12:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 22:54 [PATCH v2 0/3] i2c: create debugfs entry per adapter Wolfram Sang
2023-11-12 22:54 ` [PATCH v2 1/3] " Wolfram Sang
2023-11-12 22:59 ` [PATCH v2 2/3] i2c: gpio: move to per-adapter debugfs directory Wolfram Sang
2023-11-12 22:59 ` [PATCH v2 3/3] i2c: npcm7xx: " Wolfram Sang
2023-11-14 12:57 ` Tali Perry
2023-11-14 12:57 ` Tali Perry
2023-12-19 12:42 ` Wolfram Sang [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=ZYGPwYPW0w20RCet@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=openbmc@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.