From: Kalle Valo <kvalo@codeaurora.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Marcel Holtmann <marcel@holtmann.org>, Greg KH <gregkh@linux.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Birming Chiu <birming@realtek.com>, Pkshih <pkshih@realtek.com>
Subject: Re: New Realtek driver
Date: Tue, 25 Jul 2017 14:51:04 +0300 [thread overview]
Message-ID: <87o9s8ka53.fsf@codeaurora.org> (raw)
In-Reply-To: <daf881fc-918e-7716-2b09-20abe74f6cb3@lwfinger.net> (Larry Finger's message of "Fri, 21 Jul 2017 21:04:37 -0500")
Larry Finger <Larry.Finger@lwfinger.net> writes:
> On 07/21/2017 05:13 AM, Marcel Holtmann wrote:
>> Hi Larry,
>>
>>> Once again I find myself in the awkward position of needing to
>>> submit code to two different trees, i.e. wireless and staging.
>>>
>>> The code in question concerns a new Realtek device, the RTL8822BE.
>>> The device is already shipping, and Realtek would like it to be
>>> available in kernel 3.14. As it consists of ~120,000 new lines of
>>> code, I have assured Realtek that 3.14 would not be possible, at
>>> least in the wireless tree. What I plan to do is submit the changes
>>> in the existing drivers through wireless, and the three totally new
>>> drivers through staging. My expectation is that this code would
>>> live for a relatively short time there, but going that route would
>>> give time for the code to be reviewed properly, but still be
>>> available in a kernel driver. All of the new code will be available
>>> in a GitHub repo maintained by Realtek for those users whose
>>> distros do not configure anything in staging.
>>>
>>> For my part, I will push the wireless tree material as fast as I
>>> can and hope there is time available near the end of the 4.13-rcX
>>> sequence for the material to reach 4.14-rc1.
>>
>> I really do not understand the need for staging if there is already
>> active cleanup and submission to wireless-drivers happening. I find
>> it also unfair to others who submit code to linux-wireless and have
>> it reviewed there before it gets merged.
>>
>> Also the faster it gets into wireless-drivers the faster it can be
>> available via linux-backports. Seems many companies have used
>> linux-backports successfully to deal with older kernel versions.
>
> The part that is being submitted to wireless drivers is only a small
> part of the entire effort.
>
> Beyond that is the new driver with roughly 120,000 lines of code that
> have not yet been seen by any reviewers.
120 kLOC is a lot, why is the driver so big? I would like to take a
quick look, is the code available somewhere?
--
Kalle Valo
next prev parent reply other threads:[~2017-07-25 11:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 1:18 New Realtek driver Larry Finger
2017-07-21 10:13 ` Marcel Holtmann
2017-07-22 2:04 ` Larry Finger
2017-07-25 11:51 ` Kalle Valo [this message]
2017-07-21 15:08 ` Greg KH
2017-07-22 0:36 ` Larry Finger
2017-07-22 3:51 ` Greg KH
2017-07-22 12:51 ` Larry Finger
2017-07-22 13:09 ` Greg KH
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=87o9s8ka53.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=Larry.Finger@lwfinger.net \
--cc=birming@realtek.com \
--cc=gregkh@linux.com \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=pkshih@realtek.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.