From mboxrd@z Thu Jan  1 00:00:00 1970
From: gregkh@linuxfoundation.org (Greg KH)
Date: Mon, 26 Jun 2017 06:56:30 +0200
Subject: ks7010 cfg80211 re-write
In-Reply-To: <20170626012411.GA10047@eros>
References: <20170622011047.GA16262@eros> <20170623141906.GA1032@kroah.com>
	<20170626012411.GA10047@eros>
Message-ID: <20170626045630.GB17296@kroah.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

On Mon, Jun 26, 2017 at 11:24:11AM +1000, Tobin C. Harding wrote:
> > Every other time a wifi driver has moved out of staging, the author has
> > just given up on the staging driver, and rewritten it "properly" and
> > gotten that rewrite merged as one patch, into the real part of the
> > kernel, and after that is merged, we delete the staging driver.
> > 
> > Doing it that way is _much_ easier for the developer, as you don't have
> > to deal with any interm state at all, you can tear the thing apart and
> > put it back together on your own, and just submit the end result.
> > 
> > I strongly recommend doing it this way, but it's up to you in the end :)
> 
> I will follow your advice. I am not totally clear on the path into the
> kernel once I have a re-written functional driver but let's cross that
> bridge when we get to it.

Just submit a patch adding your new driver to
drivers/net/wireless/somewhere... to the correct mailing list, and all
will be fine.  When that gets accepted, let me know by either just
emailing me, or sending me a patch to delete the old driver out of
staging.

good luck, and see you in LA!

greg k-h