From: Daniel Almeida <daniel.almeida@collabora.com>
To: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Boris Brezillon" <boris.brezillon@collabora.com>,
"Sebastian Reichel" <sebastian.reichel@collabora.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v6 0/2] Add a bare-minimum Regulator abstraction
Date: Tue, 1 Jul 2025 12:28:37 -0300 [thread overview]
Message-ID: <CC8F34AD-811F-4504-B625-AFD845198549@collabora.com> (raw)
In-Reply-To: <20250627-topics-tyr-regulator-v6-0-1d015219b454@collabora.com>
Mark,
Is it ok for the abstraction to only be built when CONFIG_REGULATOR=y? This
means that any Rust drivers using it have to depend on CONFIG_REGULATOR too.
I thought this was acceptable, but apparently that is not the case? See this
comment from Rob Herring [0].
-- Daniel
[0] https://lore.kernel.org/rust-for-linux/a1b3561d-f5de-4474-85ef-1525a6c36bc5@arm.com/T/#mdf9d4005ee99929d0009ccc988efbc0789164b6d
next prev parent reply other threads:[~2025-07-01 15:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 17:11 Daniel Almeida
2025-06-27 17:11 ` [PATCH v6 1/2] rust: regulator: add a bare minimum regulator abstraction Daniel Almeida
2025-06-29 13:10 ` kernel test robot
2025-07-02 10:35 ` Alice Ryhl
2025-07-02 13:03 ` Daniel Almeida
2025-07-02 13:12 ` Alice Ryhl
2025-07-02 13:14 ` Daniel Almeida
2025-06-27 17:11 ` [PATCH v6 2/2] MAINAINTERS: add regulator.rs to the regulator API entry Daniel Almeida
2025-07-01 15:28 ` Daniel Almeida [this message]
2025-07-01 15:34 ` [PATCH v6 0/2] Add a bare-minimum Regulator abstraction Mark Brown
2025-07-01 16:09 ` Daniel Almeida
2025-07-01 18:22 ` Miguel Ojeda
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=CC8F34AD-811F-4504-B625-AFD845198549@collabora.com \
--to=daniel.almeida@collabora.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=broonie@kernel.org \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=tmgross@umich.edu \
/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
all inboxes | Powered by JetHome®