From: "Onur Özkan" <work@onurozkan.dev>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: paulmck@kernel.org, Gary Guo <gary@garyguo.net>,
rcu@vger.kernel.org, rust-for-linux@vger.kernel.org,
linux-kernel@vger.kernel.org, ojeda@kernel.org, boqun@kernel.org,
bjorn3_gh@protonmail.com, lossin@kernel.org,
a.hindborg@kernel.org, aliceryhl@google.com, tmgross@umich.edu,
dakr@kernel.org, peterz@infradead.org, fujita.tomonori@gmail.com,
tamird@kernel.org, jiangshanlai@gmail.com, josh@joshtriplett.org,
rostedt@goodmis.org, mathieu.desnoyers@efficios.com
Subject: Re: [PATCH v7 3/4] rust: sync: add SRCU abstraction
Date: Sun, 31 May 2026 22:11:04 +0300 [thread overview]
Message-ID: <20260531191107.35357-1-work@onurozkan.dev> (raw)
In-Reply-To: <CANiq72=jVHEu5veW_k9B66avYgVR2aHDN2QmDny=j4EK2uRXbw@mail.gmail.com>
On Sun, 31 May 2026 20:53:07 +0200
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> wrote:
> On Sun, May 31, 2026 at 8:06 PM Paul E. McKenney <paulmck@kernel.org> wrote:
> >
> > Is there a Rust-language counterpart to checkpatch.pl that could warn
> > when it sees patches adding calls to this function?
>
> We had some patches for proposed Rust checks for `checkpatch.pl`, so
> it could be there (there was also a proposed `rust_checkpatch.pl`).
>
> Having said that, Clippy's `disallowed_methods` is likely better
> (modulo bugs), and we already have a couple entries on it (please see
> `.clippy.toml` in the root). So I would suggest that first.
>
> There is also Klint if something more custom/complex is needed.
>
I am waiting for the v9 [1] reviews. If we get a complain on the current
approach we can consider the Rust-specific clean-up C function +
disallowed_methods from Clippy.
Thanks,
Onur
[1]: https://lore.kernel.org/all/20260529134004.396743-1-work@onurozkan.dev
> Cheers,
> Miguel
next prev parent reply other threads:[~2026-05-31 19:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 6:27 [PATCH v7 0/4] rust: helpers: add SRCU helpers Onur Özkan
2026-05-28 6:27 ` [PATCH v7 1/4] " Onur Özkan
2026-05-28 6:27 ` [PATCH v7 2/4] srcu: expose srcu_readers_active() Onur Özkan
2026-05-28 6:27 ` [PATCH v7 3/4] rust: sync: add SRCU abstraction Onur Özkan
2026-05-28 8:20 ` Onur Özkan
2026-05-28 8:35 ` Onur Özkan
2026-05-28 12:23 ` Gary Guo
2026-05-29 6:57 ` Onur Özkan
2026-05-29 12:07 ` Gary Guo
2026-05-29 12:29 ` Onur Özkan
2026-05-29 12:41 ` Gary Guo
2026-05-29 12:49 ` Onur Özkan
2026-05-31 18:04 ` Paul E. McKenney
2026-05-29 15:36 ` Paul E. McKenney
2026-05-30 6:27 ` Onur Özkan
2026-05-31 18:06 ` Paul E. McKenney
2026-05-31 18:53 ` Miguel Ojeda
2026-05-31 19:11 ` Onur Özkan [this message]
2026-06-01 9:29 ` Miguel Ojeda
2026-06-04 17:50 ` Paul E. McKenney
2026-05-28 6:27 ` [PATCH v7 4/4] MAINTAINERS: add Rust SRCU files to SRCU entry Onur Özkan
2026-05-28 18:50 ` [PATCH v7 0/4] rust: helpers: add SRCU helpers Paul E. McKenney
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=20260531191107.35357-1-work@onurozkan.dev \
--to=work@onurozkan.dev \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@kernel.org \
--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