From: Stanislaw Gruszka <stf_xl@wp.pl>
To: Ariel Otilibili-Anieli <Ariel.Otilibili-Anieli@eurecom.fr>
Cc: "Daniel Golle" <daniel@makrotopia.org>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
"Kalle Valo" <kvalo@kernel.org>,
"Tomislav Požega" <pozega.tomislav@gmail.com>
Subject: Re: [PATCH 1/2] rt2x00: Remove unusued value
Date: Sat, 4 Jan 2025 11:37:53 +0100 [thread overview]
Message-ID: <20250104103753.GA2228@wp.pl> (raw)
In-Reply-To: <2f7a83-6777e880-a451-5cf12280@99910178>
Hi
On Fri, Jan 03, 2025 at 02:39:21PM +0100, Ariel Otilibili-Anieli wrote:
> On Friday, January 03, 2025 14:10 CET, Stanislaw Gruszka <stf_xl@wp.pl> wrote:
>
> > On Fri, Jan 03, 2025 at 11:40:52AM +0000, Daniel Golle wrote:
> > > On Fri, Jan 03, 2025 at 09:55:40AM +0100, Stanislaw Gruszka wrote:
> > >
> > > I agree with the likely intention here, however, the vendor driver
> > > also comes with the dead code, see
> > > https://github.com/lixuande/rt2860v2/blob/master/files/rt2860v2/common/cmm_rf_cal.c#L2690
> > >
> > > So this is certainly a bug in the vendor driver as well which got ported
> > > bug-by-bug to rt2x00... Not sure what is the best thing to do in this
> > > case.
> >
> > As this was already tested and match vendor driver I would prefer
> > not to change behavior even if it looks suspicious.
>
> Thanks for having looked into this; I much appreciate your feedback.
>
> From what you two said, I understand that the patch should remove the duplicate code, and not change the logic behind.
>
> Is this right?
Yes.
Regards
Stanislaw
>
> If so; then, I have nothing else to do.
> >
> > Regards
> > Stanislaw
> >
>
next prev parent reply other threads:[~2025-01-04 10:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-21 12:39 [PATCH 0/2] rt2x00,net/phy,neterion: Remove dead values Ariel Otilibili
2024-12-21 12:39 ` [PATCH 1/2] rt2x00: Remove unusued value Ariel Otilibili
2025-01-03 8:55 ` Stanislaw Gruszka
2025-01-03 11:40 ` Daniel Golle
2025-01-03 13:10 ` Stanislaw Gruszka
2025-01-03 13:39 ` Ariel Otilibili-Anieli
2025-01-04 10:37 ` Stanislaw Gruszka [this message]
2025-01-04 12:51 ` Ariel Otilibili-Anieli
2025-01-05 21:21 ` Daniel Golle
2025-01-06 7:23 ` Ariel Otilibili-Anieli
2025-01-07 10:23 ` Stanislaw Gruszka
2025-01-07 11:01 ` Jonas Gorski
2025-01-10 13:12 ` [1/2] wifi: rt2x00: Remove unused rfval values Kalle Valo
2024-12-21 12:39 ` [PATCH 2/2] net/phy,neterion: Remove dead values Ariel Otilibili
2024-12-21 15:06 ` Andrew Lunn
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=20250104103753.GA2228@wp.pl \
--to=stf_xl@wp.pl \
--cc=Ariel.Otilibili-Anieli@eurecom.fr \
--cc=daniel@makrotopia.org \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pozega.tomislav@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 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.