From: Fabio Aiuto <fabioaiuto83@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: hdegoede@redhat.com, Larry.Finger@lwfinger.net,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: staging: rtl8723bs: questions on TODO list
Date: Fri, 14 May 2021 18:29:25 +0200 [thread overview]
Message-ID: <20210514162925.GA1568@agape.jhs> (raw)
In-Reply-To: <YJ44mtOUVZwhxW4m@kroah.com>
On Fri, May 14, 2021 at 10:45:14AM +0200, Greg KH wrote:
> On Fri, May 14, 2021 at 10:38:57AM +0200, Fabio Aiuto wrote:
> > Hello all,
> >
> > I'd like to have some clarifications about rtl8723bs driver.
> > In order to make this driver ready for moving out of staging
> > I would like to know:
> >
> > - find and remove remaining code valid only for 5 GHz. Most of the obvious
> > ones have been removed, but things like channel > 14 still exist.
> >
> > is it possible to remove all 5g code, even the one related to power
> > regulation when on band 5g? As far as I know about this card is that
> > it doesn't support 5g, so may I just delete all 5g code or there are some
> > constraints I'd take care of?
> >
> > - find and remove any code for other chips that is left over
> >
> > Ok this seems clear, are there some suggestion to do it safely?
> >
> > - convert any remaining unusual variable types
> >
> > Ok (but feel free to suggest anything)
> >
> > - find codes that can use %pM and %Nph formatting
> >
> > Ok (but feel free to suggest anything)
> >
> > - checkpatch.pl fixes - most of the remaining ones are lines too long. Many
> > of them will require refactoring
> >
> > Ok
> >
> > - merge Realtek's bugfixes and new features into the driver
> >
> > Please, can you explain what one could do that?
> >
> > - switch to use LIB80211
> > - switch to use MAC80211
> >
> > I think I need a few details for these last points as well.
> >
> > Do you think that one will need real hardware to complete
> > these tasks? I don't have rtl8723bs card at the moment, so
> > I think I will focus on those TODO activities which
> > don't need it.
>
> I recommend getting one of these devices to do the more complex tasks as
> described above. Otherwise it's going to be hard to verify that your
> changes are valid.
>
> thanks,
>
> greg k-h
got it,
thank you,
fabio
next prev parent reply other threads:[~2021-05-14 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 8:38 staging: rtl8723bs: questions on TODO list Fabio Aiuto
2021-05-14 8:45 ` Greg KH
2021-05-14 16:29 ` Fabio Aiuto [this message]
2021-05-14 9:15 ` Hans de Goede
2021-05-14 9:31 ` Fabio Aiuto
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=20210514162925.GA1568@agape.jhs \
--to=fabioaiuto83@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@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