linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kent Gibson <warthog618@gmail.com>
To: Erik Schilling <erik.schilling@linaro.org>
Cc: Linux-GPIO <linux-gpio@vger.kernel.org>,
	Viresh Kumar <viresh.kumar@linaro.org>
Subject: Re: [PATCH libgpiod 4/4] bindings: rust: clippy: silence false-positive on iterator
Date: Fri, 30 Jun 2023 18:19:45 +0800	[thread overview]
Message-ID: <ZJ6sQYctu9mHqQP5@sol> (raw)
In-Reply-To: <CTPWFHFJNFFA.2SGA858S5QIJ5@fedora>

On Fri, Jun 30, 2023 at 12:05:28PM +0200, Erik Schilling wrote:
> On Fri Jun 30, 2023 at 11:08 AM CEST, Kent Gibson wrote:
> >
> 
> > (I am seeing this one test failure on arm32, but that doesn't seem to be related
> > to this patch:
> > ---- request_config::verify::default stdout ----
> > thread 'main' panicked at 'assertion failed: `(left == right)`
> >   left: `OperationFailed(RequestConfigGetConsumer, Errno { code: 2, description: Some("No such file or directory") })`,
> >  right: `OperationFailed(RequestConfigGetConsumer, Errno { code: 0, description: Some("Success") })`', libgpiod/tests/request_config.rs:18:13
> > note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
> >
> > Not sure if that is a genuine bug or something funky in my build.)
> 
> Is the GPIO_SIM module loaded? Did you test with a custom kernel or
> some distro that ships with it?
> 

That is the only test failing out of the whole suite, so gpiosim is not
the problem.

That is with the latest from the Raspberry Pi rpi-6.4.y branch[1]
(a867309b7a55 so a few days old now), with CONFIG_GPIO_SIM so that I can
run the tests.
Happens to be running on a Pi ZeroW, but I don't think that test is speed
sensitive.  I have done a complete rebuild - same result.

Are there any distos enabling GPIO_SIM yet?

Cheers,
Kent.

[1] https://github.com/raspberrypi/linux

  reply	other threads:[~2023-06-30 10:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-29 11:08 [PATCH libgpiod 0/4] bindings: rust: clippy: fixed warnings Erik Schilling
2023-06-29 11:08 ` [PATCH libgpiod 1/4] bindings: rust: clippy: drop unnecessary casts Erik Schilling
2023-06-29 11:09 ` [PATCH libgpiod 2/4] bindings: rust: clippy: silence false-positives on casts Erik Schilling
2023-06-29 11:09 ` [PATCH libgpiod 3/4] bindings: rust: clippy: drop unneeded conversions Erik Schilling
2023-06-29 11:09 ` [PATCH libgpiod 4/4] bindings: rust: clippy: silence false-positive on iterator Erik Schilling
2023-06-30  9:08   ` Kent Gibson
2023-06-30 10:05     ` Erik Schilling
2023-06-30 10:19       ` Kent Gibson [this message]
2023-06-30 10:46         ` Erik Schilling
2023-06-30 10:50           ` Kent Gibson
2023-06-30 10:53             ` Erik Schilling
2023-07-01 13:10               ` Kent Gibson
2023-06-30  6:08 ` [PATCH libgpiod 0/4] bindings: rust: clippy: fixed warnings Viresh Kumar

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=ZJ6sQYctu9mHqQP5@sol \
    --to=warthog618@gmail.com \
    --cc=erik.schilling@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=viresh.kumar@linaro.org \
    /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;
as well as URLs for NNTP newsgroup(s).