From: Jakub Kicinski <kuba@kernel.org>
To: Daniel Golle <daniel@makrotopia.org>, Andrew Lunn <andrew@lunn.ch>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
netdev@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Qingfang Deng <dqfext@gmail.com>,
SkyLake Huang <SkyLake.Huang@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Subject: Re: [PATCH v2] net: phy: add driver for MediaTek SoC built-in GE PHYs
Date: Tue, 25 Apr 2023 07:24:04 -0700 [thread overview]
Message-ID: <20230425072404.28b798e1@kernel.org> (raw)
In-Reply-To: <ZEePDK2oW5xkiEIv@makrotopia.org>
On Tue, 25 Apr 2023 09:27:56 +0100 Daniel Golle wrote:
> > Daniel, is it high prio for you to get it into 6.4 or 6.5 is okay?
>
> No rush, as this is mostly relevant for OpenWrt the thing which matters
> most to me is having it in the next LTS kernel, so 6.5 should still be
> fine I suppose.
>
> >
> > I'm trying to get a read on whether we should merge it because it's
> > kind of on the goal line for this merge window.
> >
> > If nobody feels strongly we can do this the traditional way - I'll
> > just complain about RCT, hence kicking it back out into the field :)
>
> I understand Andrew's concerns and will resubmit for the next merge
> window in 2 weeks, and without the LED part for now until PHY LED
> infrastructure is more ready (ie. able to offload 'netdev' trigger
> to hardware)
Perfect, thanks!
prev parent reply other threads:[~2023-04-25 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-22 12:36 [PATCH v2] net: phy: add driver for MediaTek SoC built-in GE PHYs Daniel Golle
2023-04-25 1:37 ` Jakub Kicinski
2023-04-25 3:20 ` Andrew Lunn
2023-04-25 8:27 ` Daniel Golle
2023-04-25 14:24 ` 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=20230425072404.28b798e1@kernel.org \
--to=kuba@kernel.org \
--cc=SkyLake.Huang@mediatek.com \
--cc=andrew@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=dqfext@gmail.com \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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).