[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2fee02c2-4404-cd2e-8889-97e512a117f4@gmail.com>
Date: Fri, 24 Jul 2020 13:13:17 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Andy Shevchenko <andy.shevchenko@...il.com>,
Andrew Lunn <andrew@...n.ch>
Cc: Jeremy Linton <jeremy.linton@....com>,
Calvin Johnson <calvin.johnson@....nxp.com>,
Russell King - ARM Linux admin <linux@...linux.org.uk>,
Jon <jon@...id-run.com>,
Cristi Sovaiala <cristian.sovaiala@....com>,
Ioana Ciornei <ioana.ciornei@....com>,
Madalin Bucur <madalin.bucur@....nxp.com>,
netdev <netdev@...r.kernel.org>, linux.cj@...il.com,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>
Subject: Re: [net-next PATCH v7 1/6] Documentation: ACPI: DSD: Document MDIO
PHY
On 7/24/20 1:12 PM, Andy Shevchenko wrote:
> On Fri, Jul 24, 2020 at 10:20 PM Andrew Lunn <andrew@...n.ch> wrote:
>
>> I think we need to NACK all attempts to add ACPI support to phylib and
>> phylink until an authoritative ACPI Linux maintainer makes an
>> appearance and actively steers the work. And not just this patchset,
>> but all patchsets in the networking domain which have an ACPI
>> component.
>
> It's funny, since I see ACPI mailing list and none of the maintainers
> in the Cc here...
> I'm not sure they pay attention to some (noise-like?) activity which
> (from their perspective) happens on unrelated lists.
If you what you describe here is their perception of what is going on
here, that is very encouraging, we are definitively going to make progress.
--
Florian
Powered by blists - more mailing lists