From: Dan Carpenter <error27@gmail.com>
To: David Laight <David.Laight@aculab.com>
Cc: 'Deepak R Varma' <drv@mailo.com>,
"outreachy@lists.linux.dev" <outreachy@lists.linux.dev>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-staging@lists.linux.dev" <linux-staging@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: rtl8192e: Use min_t/max_t macros for variable comparison
Date: Thu, 3 Nov 2022 11:53:45 +0300 [thread overview]
Message-ID: <Y2OBmWIwhRMOk6V/@kadam> (raw)
In-Reply-To: <d8fa86bf71694f23b8f175245722e86f@AcuMS.aculab.com>
On Thu, Nov 03, 2022 at 08:24:15AM +0000, David Laight wrote:
> > --- a/drivers/staging/rtl8192e/rtl819x_HTProc.c
> > +++ b/drivers/staging/rtl8192e/rtl819x_HTProc.c
> > @@ -587,17 +587,12 @@ void HTOnAssocRsp(struct rtllib_device *ieee)
> > else
> > pHTInfo->CurrentAMPDUFactor = HT_AGG_SIZE_64K;
> > } else {
> > - if (pPeerHTCap->MaxRxAMPDUFactor < HT_AGG_SIZE_32K)
> > - pHTInfo->CurrentAMPDUFactor =
> > - pPeerHTCap->MaxRxAMPDUFactor;
> > - else
> > - pHTInfo->CurrentAMPDUFactor = HT_AGG_SIZE_32K;
> > + pHTInfo->CurrentAMPDUFactor = min_t(u32, pPeerHTCap->MaxRxAMPDUFactor,
> > + HT_AGG_SIZE_32K);
>
> For min() to fail there must be a signed v unsigned mismatch.
> Maybe that ought to be fixed.
>
u32 is the right choice here.
I'm having a hard time understanding your email. You might be saying
we could declare HT_AGG_SIZE_32K as a u32 so then we could use min()
instead of min_t()? HT_AGG_SIZE_32K is an enum.
pPeerHTCap->MaxRxAMPDUFactor is a bitfield.
u8 MaxRxAMPDUFactor:2;
We will never be able to use min().
> > }
> > }
> > - if (pHTInfo->MPDU_Density > pPeerHTCap->MPDUDensity)
> > - pHTInfo->current_mpdu_density = pHTInfo->MPDU_Density;
> > - else
> > - pHTInfo->current_mpdu_density = pPeerHTCap->MPDUDensity;
> > + pHTInfo->current_mpdu_density = max_t(u8, pHTInfo->MPDU_Density,
> > + pPeerHTCap->MPDUDensity);
>
> Using u8 with max_t() really doesn't make any sense.
Using u8 looks wrong because you would worry that one of the types is
larger than U8_MAX. But it's actually fine. The types are u8 vs another
bitfield. I would probably have gone with u32 here as well.
> The value will get promoted to signed int prior to the comparison.
>
That's sort of true-ish but I don't understand what you are saying?
#confused
regards,
dan carpenter
next prev parent reply other threads:[~2022-11-03 8:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 22:36 [PATCH] staging: rtl8192e: Use min_t/max_t macros for variable comparison Deepak R Varma
2022-11-02 22:56 ` Philipp Hortmann
2022-11-03 8:24 ` David Laight
2022-11-03 8:53 ` Dan Carpenter [this message]
2022-11-03 9:18 ` Deepak R Varma
2022-11-03 10:09 ` Dan Carpenter
2022-11-04 8:01 ` Deepak R Varma
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=Y2OBmWIwhRMOk6V/@kadam \
--to=error27@gmail.com \
--cc=David.Laight@aculab.com \
--cc=drv@mailo.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
/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