[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220222053452.GC3943@kadam>
Date: Tue, 22 Feb 2022 08:34:52 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Michael Straube <straube.linux@...il.com>
Cc: Pavel Skripkin <paskripkin@...il.com>, gregkh@...uxfoundation.org,
Larry.Finger@...inger.net, phil@...lpotter.co.uk,
linux-staging@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3] staging: r8188eu: refactor rtw_ch2freq()
On Mon, Feb 21, 2022 at 08:20:14PM +0100, Michael Straube wrote:
> On 2/21/22 13:22, Dan Carpenter wrote:
> > On Sun, Feb 20, 2022 at 05:30:08PM +0100, Michael Straube wrote:
> > > On 2/20/22 17:20, Pavel Skripkin wrote:
> > Just from a review stand point it would be best to leave the original
> > behavior.
> >
>
> Do you mean to leave the whole original code including the 5 GHz
> frequencies? Or returning a default value if we have a channel value < 1
> or > 14?
I meant what Pavel said:
if (channel == 0 || channel > ARRAY_SIZE(ch_freq_map))
return 2412;
return ch_freq_map[channel - 1];
>
> I'm a bit confused now, because Greg asked how we know that the driver
> is only for 2.4 GHz chips.
>
Haven't you been deleting all the 5GHz code for some time now? Greg
isn't saying you have to keep that if there is no reason. Just put the
reason in the commit message and resend.
regards,
dan carpenter
Powered by blists - more mailing lists