From: Mika Westerberg <mika.westerberg@linux•intel.com>
To: "Russell King (Oracle)" <rmk+kernel@armlinux•org.uk>
Cc: linux-acpi@vger•kernel.org, linux-i2c@vger•kernel.org,
netdev@vger•kernel.org, Andrew Lunn <andrew@lunn•ch>,
"David S. Miller" <davem@davemloft•net>,
Eric Dumazet <edumazet@google•com>,
Heiner Kallweit <hkallweit1@gmail•com>,
Jakub Kicinski <kuba@kernel•org>, Paolo Abeni <pabeni@redhat•com>,
Wolfram Sang <wsa@kernel•org>
Subject: Re: [PATCH RFC net-next v2 1/2] i2c: add fwnode APIs
Date: Mon, 19 Dec 2022 12:55:06 +0200 [thread overview]
Message-ID: <Y6BDCl4VXygVrjCU@black.fi.intel.com> (raw)
In-Reply-To: <E1p7CoU-0012Ul-MM@rmk-PC.armlinux.org.uk>
On Mon, Dec 19, 2022 at 09:52:02AM +0000, Russell King (Oracle) wrote:
> Add fwnode APIs for finding and getting I2C adapters, which will be
> used by the SFP code. These are passed the fwnode corresponding to
> the adapter, and return the I2C adapter. It is the responsibility of
> the caller to find the appropriate fwnode.
>
> We keep the DT and ACPI interfaces, but where appropriate, recode them
> to use the fwnode interfaces internally.
>
> Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux•org.uk>
Reviewed-by: Mika Westerberg <mika.westerberg@linux•intel.com>
next prev parent reply other threads:[~2022-12-19 10:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 9:50 [PATCH RFC v2 0/2] Add I2C fwnode lookup/get interfaces Russell King (Oracle)
2022-12-19 9:52 ` [PATCH RFC net-next v2 1/2] i2c: add fwnode APIs Russell King (Oracle)
2022-12-19 10:55 ` Mika Westerberg [this message]
2022-12-19 9:52 ` [PATCH RFC net-next v2 2/2] net: sfp: use i2c_get_adapter_by_fwnode() Russell King (Oracle)
2022-12-19 10:55 ` Mika Westerberg
2023-01-03 12:20 ` [PATCH RFC v2 0/2] Add I2C fwnode lookup/get interfaces Russell King (Oracle)
2023-01-09 11:48 ` Wolfram Sang
2023-01-10 13:02 ` Russell King (Oracle)
2023-01-10 17:36 ` Jakub Kicinski
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=Y6BDCl4VXygVrjCU@black.fi.intel.com \
--to=mika.westerberg@linux$(echo .)intel.com \
--cc=andrew@lunn$(echo .)ch \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=hkallweit1@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-acpi@vger$(echo .)kernel.org \
--cc=linux-i2c@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=rmk+kernel@armlinux$(echo .)org.uk \
--cc=wsa@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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