From: Hau <hau@realtek.com>
To: Jakub Kicinski <kuba@kernel.org>,
"hkallweit1@gmail.com" <hkallweit1@gmail.com>,
Andrew Lunn <andrew@lunn.ch>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
nic_swsd <nic_swsd@realtek.com>
Subject: RE: [PATCH net-next v4] r8169: add support for rtl8168h(revid 0x2a) + rtl8211fs fiber application
Date: Mon, 3 Oct 2022 12:28:50 +0000 [thread overview]
Message-ID: <36b777afdb2a40fbb56ce6694e01e48b@realtek.com> (raw)
In-Reply-To: <20220921172707.2b1399cb@kernel.org>
> From: Jakub Kicinski [mailto:kuba@kernel.org]
> Sent: Thursday, September 22, 2022 8:27 AM
> To: hkallweit1@gmail.com; Andrew Lunn <andrew@lunn.ch>
> Cc: Hau <hau@realtek.com>; netdev@vger.kernel.org; nic_swsd
> <nic_swsd@realtek.com>
> Subject: Re: [PATCH net-next v4] r8169: add support for rtl8168h(revid 0x2a)
> + rtl8211fs fiber application
>
> On Tue, 20 Sep 2022 14:59:44 -0700 Jakub Kicinski wrote:
> > On Thu, 15 Sep 2022 22:48:07 +0800 Chunhao Lin wrote:
> > > rtl8168h(revid 0x2a) + rtl8211fs is for fiber related application.
> > > rtl8168h is connected to rtl8211fs mdio bus via its eeprom or gpio pins.
> > >
> > > In this patch, use bitbanged MDIO framework to access rtl8211fs via
> > > rtl8168h's eeprom or gpio pins.
> > >
> > > And set mdiobb_ops owner to NULL to avoid increase module's refcount
> > > to prevent rmmod cannot be done.
> > > https://patchwork.kernel.org/project/linux-renesas-soc/patch/2020073
> > > 0100151.7490-1-ashiduka@fujitsu.com/
> >
> > Heiner, Andrew, good?
>
> Well, we need Hainer or Andrew to ack, I'm marking this patch as Deferred
> until such endorsement is obtained.
>
Hi Heiner, could you help to check this patch?
Thanks.
------Please consider the environment before printing this e-mail.
next prev parent reply other threads:[~2022-10-03 12:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 14:48 [PATCH net-next v4] r8169: add support for rtl8168h(revid 0x2a) + rtl8211fs fiber application Chunhao Lin
[not found] ` <CAFSsGVvKYRKtxXTSRuqhf9nec0hQv3PQS5rjZBjZDGyjU4+Bbw@mail.gmail.com>
[not found] ` <5cca2b9476fa42a1b0397e1465f0ef73@realtek.com>
2022-09-15 18:13 ` Hau
2022-09-20 21:59 ` Jakub Kicinski
2022-09-22 0:27 ` Jakub Kicinski
2022-10-03 12:28 ` Hau [this message]
2022-10-08 21:36 ` Heiner Kallweit
2022-10-12 16:28 ` Hau
2022-10-15 8:29 ` Heiner Kallweit
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=36b777afdb2a40fbb56ce6694e01e48b@realtek.com \
--to=hau@realtek.com \
--cc=andrew@lunn.ch \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.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).