From: <Woojung.Huh@microchip.com>
To: <Allan.Nielsen@microchip.com>, <f.fainelli@gmail.com>
Cc: <u.kleine-koenig@pengutronix.de>, <Nicolas.Ferre@microchip.com>,
<netdev@vger.kernel.org>, <andrew@lunn.ch>,
<kernel@pengutronix.de>, <hkallweit1@gmail.com>,
<Ravi.Hegde@microchip.com>, <Tristram.Ha@microchip.com>,
<Yuiko.Oshino@microchip.com>
Subject: RE: net: micrel: confusion about phyids used in driver
Date: Wed, 21 Aug 2019 19:53:29 +0000 [thread overview]
Message-ID: <BL0PR11MB3012CC53F680EDF4C5146652E7AA0@BL0PR11MB3012.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20190821184947.43iilefgrjn4zrtl@lx-anielsen.microsemi.net>
Hi Allan & Florian,
> > > So we're in need of someone who can get their hands on some more
> > > detailed documentation than publicly available to allow to make the
> > > driver handle the KSZ8051MLL correctly without breaking other stuff.
> > >
> > > I assume you are in a different department of Microchip than the people
> > > caring for PHYs, but maybe you can still help finding someone who cares?
> >
> > Allan, is this something you could help with? Thanks!
> Sorry, I'm new in Microchip (was aquired through Microsemi), and I know next to
> nothing about the Micrel stuff.
>
> Woojung: Can you comment on this, or try to direct this to someone who knows
> something...
Forwarded to Yuiko. Will do follow-up.
Thanks.
Woojung
next prev parent reply other threads:[~2019-08-21 19:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 20:29 net: micrel: confusion about phyids used in driver Uwe Kleine-König
2019-05-09 20:55 ` Heiner Kallweit
2019-05-09 21:07 ` Andrew Lunn
2019-05-10 7:22 ` Uwe Kleine-König
2019-07-02 20:31 ` Uwe Kleine-König
2019-07-02 20:55 ` Yuiko.Oshino
2019-08-08 8:36 ` Uwe Kleine-König
2019-08-20 20:25 ` Uwe Kleine-König
2019-08-20 20:30 ` Heiner Kallweit
2019-08-21 17:24 ` Florian Fainelli
2019-08-21 18:49 ` allan.nielsen
2019-08-21 19:53 ` Woojung.Huh [this message]
2019-10-16 9:09 ` Uwe Kleine-König
2019-10-16 11:45 ` Yuiko.Oshino
2019-05-11 14:00 ` 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=BL0PR11MB3012CC53F680EDF4C5146652E7AA0@BL0PR11MB3012.namprd11.prod.outlook.com \
--to=woojung.huh@microchip.com \
--cc=Allan.Nielsen@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=Ravi.Hegde@microchip.com \
--cc=Tristram.Ha@microchip.com \
--cc=Yuiko.Oshino@microchip.com \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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).