public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Luka Gejak <luka.gejak@linux.dev>
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: I need piece of advice regarding rtl8723bs
Date: Wed, 11 Mar 2026 10:27:29 +0100	[thread overview]
Message-ID: <2026031119-retract-obnoxious-0306@gregkh> (raw)
In-Reply-To: <0A9F09AD-0082-489F-878A-0899CB6F7413@linux.dev>

On Wed, Mar 11, 2026 at 10:13:41AM +0100, Luka Gejak wrote:
> On March 11, 2026 9:03:27 AM GMT+01:00, Dan Carpenter <dan.carpenter@linaro.org> wrote:
> >On Wed, Mar 11, 2026 at 08:21:47AM +0100, Luka Gejak wrote:
> >> Hi Greg, 
> >> Sorry if I am taking a lot of your time or disrupting your workflow,
> >> but I would like a piece of advice regarding staging/rtl8723bs. As
> >> you may already know(or you may not), I am working on port of
> >> rtl8723bs to mac80211 architecture. I am currently on stage on
> >> getting wifi scans to work(I can bring up interface, and I believe
> >> that I am close to getting scans working as well) so I want to ask
> >> you if you recommend making patches for staging/rtl8723bs as once I
> >> finish the driver and begin process of upstreaming it
> >> staging/rtl8723bs will be irrelevant/deleted(or will it?).
> >> Thank you for your time, Luka Gejak
> >
> >I'm not 100% sure what you are asking...
> >
> >If you want to port rtl8723bs to mac80211, that's great.  We love
> >that.  When it's ready we can review it.
> >
> >Until then people are free to change staging/rtl8723bs if they want to.
> >Your work on the port is future work.  We can't really be confident of
> >anything that will happen in the future so we just go on with what we
> >have.
> >
> >When your driver is merged and it supports all the hardware that
> >staging/rtl8723bs does then we'll drop the staging driver.  We never
> >keep two drivers for the same code.
> >
> >regards,
> >dan carpenter
> 
> Hi Dan,
> Let me clarify, I am decently sure that I can make driver work and I
> want to ask if I should focus of development of that driver or if I
> should take time to contribute to staging/rtl8723bs as well.

That's your decision to make, we can't tell anyone what to spend their
time on :)

That being said, converting the existing driver, in-place, is probably a
harder task than doing a new one "from scratch", if previous attempts
are any indication.  But that all depends on the developer involved.
So, it's your call.

thanks,

greg k-h

  reply	other threads:[~2026-03-11  9:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-11  7:21 I need piece of advice regarding rtl8723bs Luka Gejak
2026-03-11  8:03 ` Dan Carpenter
2026-03-11  9:13   ` Luka Gejak
2026-03-11  9:27     ` Greg Kroah-Hartman [this message]
2026-03-11 10:37       ` Luka Gejak

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=2026031119-retract-obnoxious-0306@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dan.carpenter@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=luka.gejak@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