From: Jakub Kicinski <kuba@kernel.org>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: Wolfram Sang <wsa@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
linux-acpi@vger.kernel.org, linux-i2c@vger.kernel.org,
netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Eric Dumazet <edumazet@google.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH RFC v2 0/2] Add I2C fwnode lookup/get interfaces
Date: Tue, 10 Jan 2023 09:36:04 -0800 [thread overview]
Message-ID: <20230110093604.15d7c113@kernel.org> (raw)
In-Reply-To: <Y71h7OF6ydo2A0dw@shell.armlinux.org.uk>
On Tue, 10 Jan 2023 13:02:36 +0000 Russell King (Oracle) wrote:
> On Mon, Jan 09, 2023 at 12:48:37PM +0100, Wolfram Sang wrote:
> > > This RFC series is intended for the next merge window, but we will need
> > > to decide how to merge it as it is split across two subsystems. These
> > > patches have been generated against the net-next, since patch 2 depends
> > > on a recently merged patch in that tree (which is now in mainline.)
> >
> > I'd prefer to apply it all to my I2C tree then. I can also provide an
> > immutable branch for net if that is helpful.
>
> If we go for the immutable branch, then patch 2 might as well be
> merged via the net tree, if net-next is willing to pull your
> immutable branch.
>
> Dave? Jakub? Paolo? Do you have any preferences how you'd like to
> handle this?
No strong preference here. Immutable branch works.
Patch 2 will stick out in the diffstat for i2c so may indeed be better
to apply it to net-next only, then again perhaps Wolfram prefers to
have the user merged with the API? We're fine either way.
prev parent reply other threads:[~2023-01-10 17:36 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
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 [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=20230110093604.15d7c113@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mika.westerberg@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wsa@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 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.