From: Kent Gibson <warthog618@gmail.com>
To: Erik Schilling <erik.schilling@linaro.org>
Cc: linux-gpio@vger.kernel.org, brgl@bgdev.pl, viresh.kumar@linaro.org
Subject: Re: [libgpiod][PATCH] bindings: rust: fix clippy lint warnings
Date: Mon, 19 Jun 2023 16:33:09 +0800 [thread overview]
Message-ID: <ZJASxQpvNuWWNXfo@sol> (raw)
In-Reply-To: <CTGH61DGZBIQ.RVXF4UG9BYH2@fedora>
On Mon, Jun 19, 2023 at 10:13:52AM +0200, Erik Schilling wrote:
> On Mon Jun 19, 2023 at 9:57 AM CEST, Kent Gibson wrote:
> > On Mon, Jun 19, 2023 at 09:36:48AM +0200, Erik Schilling wrote:
> > > Sorry, got distracted while sorting out the MSRV mess that I sent a
> > > separate patch for [4].
> > >
> >
> > 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
> > removed, in fact in my initial comment I lamented the fact they were
> > necessary.
>
> ACK. Not sure how the situation was when the patches came together, but
> today I would suggest to just drop the casts. Do you want to respin your
> series or shall I send the fixes?
>
You go ahead.
Cheers,
Kent.
next prev parent reply other threads:[~2023-06-19 8:33 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 [this message]
2023-06-19 8:50 ` Viresh Kumar
2023-06-19 8:59 ` Erik Schilling
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=ZJASxQpvNuWWNXfo@sol \
--to=warthog618@gmail.com \
--cc=brgl@bgdev.pl \
--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 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.