[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0hBG-ccWdhiKtcasAVOph+===AZoOroznf2k5OG0BOnkg@mail.gmail.com>
Date: Wed, 25 Jun 2025 11:17:33 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Danilo Krummrich <dakr@...nel.org>, Igor Korotin <igor.korotin.linux@...il.com>
Cc: ojeda@...nel.org, alex.gaynor@...il.com, rafael@...nel.org,
gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
rust-for-linux@...r.kernel.org, linux-acpi@...r.kernel.org,
boqun.feng@...il.com, gary@...yguo.net, bjorn3_gh@...tonmail.com,
benno.lossin@...ton.me, a.hindborg@...nel.org, aliceryhl@...gle.com,
tmgross@...ch.edu, lenb@...nel.org, wedsonaf@...il.com,
viresh.kumar@...aro.org, alex.hung@....com, dingxiangfei2009@...il.com
Subject: Re: [PATCH v6 6/6] samples: rust: add ACPI match table example to
platform driver
On Tue, Jun 17, 2025 at 7:15 PM Danilo Krummrich <dakr@...nel.org> wrote:
>
> On Tue, Jun 17, 2025 at 05:39:07PM +0100, Igor Korotin wrote:
> > I could suggest on of the following:
> > DRV0001
> > DRVR0001
> > PDRV0001
>
> This one looks reasonable to me.
>
> > TEST0001
> > TST0001
Can we please avoid using made up device IDs in the code, even if it
is just sample code?
It is way better to use a real one that's been reserved already as
"never use in real ACPI tables" for some reason. I think I can find a
few of these for you if need be.
Thanks!
Powered by blists - more mailing lists