From: Lee Jones <lee@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Marek Vasut <marex@denx.de>,
devicetree@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Pavel Machek <pavel@ucw.cz>, Rob Herring <robh@kernel.org>,
linux-leds@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: leds: Document "netdev" trigger
Date: Fri, 16 Aug 2024 16:47:30 +0100 [thread overview]
Message-ID: <20240816154626.GC5853@google.com> (raw)
In-Reply-To: <ed20f083-90e1-406c-bcda-f9fc92807278@lunn.ch>
On Tue, 06 Aug 2024, Andrew Lunn wrote:
> > > We could do, but we have to keep netdev around for backwards
> > > compatibility. There are DT blobs using it which we cannot break.
> >
> > Oh, this 'just' a documentation patch? 'netdev' is already in use?
> >
>
> A few examples:
>
> intel/ixp/intel-ixp42x-iomega-nas100d.dts: linux,default-trigger = "netdev";
> intel/ixp/intel-ixp42x-dlink-dsm-g600.dts: linux,default-trigger = "netdev";
> nxp/imx/imx53-m53menlo.dts: linux,default-trigger = "netdev";
> rockchip/rk3128-xpi-3128.dts: * linux,default-trigger = "netdev";
> ti/omap/am5729-beagleboneai.dts: linux,default-trigger = "netdev";
> ti/omap/am335x-netcan-plus-1xx.dts: linux,default-trigger = "netdev";
Gross! Okay.
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2024-08-16 15:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 11:46 [PATCH v2] dt-bindings: leds: Document "netdev" trigger Marek Vasut
2024-07-09 9:06 ` Krzysztof Kozlowski
2024-07-25 8:50 ` Lee Jones
2024-07-25 12:37 ` Andrew Lunn
2024-08-01 12:53 ` Lee Jones
2024-08-01 13:03 ` Andrew Lunn
2024-08-05 13:56 ` Lee Jones
2024-08-05 22:56 ` Andrew Lunn
2024-08-16 15:47 ` Lee Jones [this message]
2024-08-16 15:53 ` (subset) " Lee Jones
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=20240816154626.GC5853@google.com \
--to=lee@kernel.org \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jacek.anaszewski@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=marex@denx.de \
--cc=netdev@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robh@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 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).