public inbox for linux-gpio@vger.kernel.org
 help / color / mirror / Atom feed
From: "Erik Schilling" <erik.schilling@linaro.org>
To: "Viresh Kumar" <viresh.kumar@linaro.org>
Cc: "Kent Gibson" <warthog618@gmail.com>,
	<linux-gpio@vger.kernel.org>, <brgl@bgdev.pl>
Subject: Re: [libgpiod][PATCH] bindings: rust: fix clippy lint warnings
Date: Mon, 19 Jun 2023 10:59:17 +0200	[thread overview]
Message-ID: <CTGI4TBHMWFZ.1M1XOQ3SK26IF@fedora> (raw)
In-Reply-To: <20230619085017.lifz2hcqzi6fam2k@vireshk-i7>

On Mon Jun 19, 2023 at 10:50 AM CEST, Viresh Kumar wrote:
> I missed these earlier, thanks for cc'ing me now Kent.
>
> On 19-06-23, 10:13, Erik Schilling wrote:
> > On Mon Jun 19, 2023 at 9:57 AM CEST, Kent Gibson wrote:
> > > My reasoning was simply that building the bindings as you suggested
> > > resulted in lint warnings, which is noisy and iritating when trying to
> > > lint my own code.
> > 
> > I fully agree that we should fix them! I was just confused about the
> > explanation.
> > 
> > > But I'm just the messenger.  Your question would be better directed at
> > > Viresh - it is his code so he should be able to tell you why the casts
> > > are there.
> > > IIRC we needed the casts historically, though I don't recall the rust
> > > version we were using at the time.
> > > If we've moved beyond that then I have no problem with the casts being
> > > removedi, in fact in my initial comment I lamented the fact they were
> > > necessary.
>
> I don't remember the versions used at that time, but here [1] are few
> of the auto-generated FFI bindings that I used to keep in my series
> then, in case these can help.
>
> IIRC, some of these were required for 32 bit builds. Don't remember
> the exact details but there were build / clippy errors / warnings
> without them.
>
> I am fine with updating code based on latest version of Rust and get
> these removed.
>
> Erik: Please build for 32 bit ARM too btw.

Will do. Will try to come up with some test suite that may be
upstreamable too.

>
> -- 
> viresh
>
> [1] https://lore.kernel.org/all/401d9417d895b8b1b19ca577c84347d89f7e0fbd.1667815011.git.viresh.kumar@linaro.org/


      reply	other threads:[~2023-06-19  8:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12 15:40 [libgpiod][PATCH] bindings: rust: fix clippy lint warnings Kent Gibson
2023-06-14  8:14 ` Erik Schilling
2023-06-14  8:29   ` Kent Gibson
2023-06-14  8:40     ` Erik Schilling
2023-06-14  9:06       ` Kent Gibson
2023-06-14  9:16         ` Erik Schilling
2023-06-19  7:36     ` Erik Schilling
2023-06-19  7:49       ` Erik Schilling
2023-06-19  7:57       ` Kent Gibson
2023-06-19  8:13         ` Erik Schilling
2023-06-19  8:33           ` Kent Gibson
2023-06-19  8:50           ` Viresh Kumar
2023-06-19  8:59             ` Erik Schilling [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=CTGI4TBHMWFZ.1M1XOQ3SK26IF@fedora \
    --to=erik.schilling@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=linux-gpio@vger.kernel.org \
    --cc=viresh.kumar@linaro.org \
    --cc=warthog618@gmail.com \
    /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