Linux Input/HID development
 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 v8 2/2] rust: serio: add serio bus abstractions and port Gravis Stinger driver
Date: Sat, 07 Nov 2026 07:22:48 +0000	[thread overview]
Message-ID: <sashiko-outbox-202704@kernel.org> (raw)
In-Reply-To: <20261107070010.500128-3-harepro29@gmail.com>

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

commit 7de59dece60ff6273292c2ada6f83924d551c7fd
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..4e16917ddd70c
> --- /dev/null
> +++ b/rust/kernel/serio.rs
[ ... ]
> +pub use crate::irq::IrqReturn;
> +
> +#[allow(non_upper_case_globals)]
> +const irqreturn_IRQ_NONE: bindings::irqreturn_t = bindings::irqreturn::IRQ_NONE;
> +#[allow(non_upper_case_globals)]
> +const irqreturn_IRQ_HANDLED: bindings::irqreturn_t = bindings::irqreturn::IRQ_HANDLED;

[Severity: High]
Does this fail to build when CONFIG_RUST=y and CONFIG_SERIO=y are enabled?
bindgen generates bindings::irqreturn as a u32 type alias with flat top-level
constants bindings::irqreturn_IRQ_NONE and bindings::irqreturn_IRQ_HANDLED
(as used in rust/kernel/irq/request.rs), so resolving associated items
IRQ_NONE and IRQ_HANDLED on bindings::irqreturn fails with E0599.  Dropping
these local constants and using bindings::irqreturn_IRQ_NONE and
bindings::irqreturn_IRQ_HANDLED directly in Registration::interrupt_callback()
will fix the build.

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

      reply	other threads:[~2026-11-07  7:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-07  7:00 [PATCH v8 0/2] rust: input: add input/serio abstractions and port Gravis Stinger driver Vecheslav Filatov
2026-11-07  7:00 ` [PATCH v8 1/2] rust: input: add input device abstractions Vecheslav Filatov
2026-11-07  7:00 ` [PATCH v8 2/2] rust: serio: add serio bus abstractions and port Gravis Stinger driver Vecheslav Filatov
2026-11-07  7:22   ` 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-202704@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox