All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Vecheslav Filatov" <harepro29@gmail.com>
Cc: linux-input@vger.kernel.org, dmitry.torokhov@gmail.com,
	ojeda@kernel.org, gary@garyguo.net
Subject: Re: [PATCH v7 2/2] rust: serio: add serio bus abstractions and port Gravis Stinger driver
Date: Sat, 07 Nov 2026 06:50:02 +0000	[thread overview]
Message-ID: <sashiko-outbox-202671@kernel.org> (raw)
In-Reply-To: <20261107063520.489958-3-harepro29@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [High] rust: serio: non-existent crate::bindings::irqreturn::IRQ_* in
  mod bindings
--

commit e108571e336aa2835a298065109700e94f7a4ab9
Author: Vecheslav Filatov <harepro29@gmail.com>

rust: serio: add serio bus abstractions and port Gravis Stinger driver

This commit adds Rust abstractions for the serio bus subsystem and ports
the Gravis Stinger serial gamepad driver to Rust.

> diff --git a/rust/kernel/serio.rs b/rust/kernel/serio.rs
> new file mode 100644
> index 0000000000000..dc0de5f527158
> --- /dev/null
> +++ b/rust/kernel/serio.rs
> @@ -0,0 +1,341 @@

[ ... ]

> +mod bindings {
> +    pub(super) use crate::bindings::*;
> +
> +    #[allow(non_upper_case_globals)]
> +    pub(super) const irqreturn_IRQ_NONE: crate::bindings::irqreturn_t =
> +        crate::bindings::irqreturn::IRQ_NONE;
> +    #[allow(non_upper_case_globals)]
> +    pub(super) const irqreturn_IRQ_HANDLED: crate::bindings::irqreturn_t =
> +        crate::bindings::irqreturn::IRQ_HANDLED;
> +}

[Severity: High]
Does this fail to build when CONFIG_RUST=y and CONFIG_SERIO=y are enabled?

bindgen generates crate::bindings::irqreturn as a type alias for c_uint
and exposes the enum variants as top-level constants
crate::bindings::irqreturn_IRQ_NONE and
crate::bindings::irqreturn_IRQ_HANDLED (as used in
rust/kernel/irq/request.rs). Referencing crate::bindings::irqreturn::IRQ_*
fails to compile with E0599 and shadows the existing top-level constants;
importing crate::bindings directly avoids the need for this wrapper
module.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261107063520.489958-1-harepro29@gmail.com?part=2

      reply	other threads:[~2026-11-07  6:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-07  6:35 [PATCH v7 0/2] rust: input: add input/serio abstractions and port Gravis Stinger driver Vecheslav Filatov
2026-11-07  6:35 ` [PATCH v7 1/2] rust: input: add input device abstractions Vecheslav Filatov
2026-11-07  6:35 ` [PATCH v7 2/2] rust: serio: add serio bus abstractions and port Gravis Stinger driver Vecheslav Filatov
2026-11-07  6:50   ` sashiko-bot [this message]

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=sashiko-outbox-202671@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=gary@garyguo.net \
    --cc=harepro29@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=ojeda@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.