linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jes Sorensen <jes.sorensen@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Larry Finger <Larry.Finger@lwfinger.net>
Cc: Hans de Goede <hdegoede@redhat.com>,
	Bastien Nocera <hadess@hadess.net>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH] staging: Add rtl8723bs sdio wifi driver
Date: Thu, 30 Mar 2017 10:06:09 -0400	[thread overview]
Message-ID: <d4f84482-1ed3-7ba5-10ba-406afbe2a372@gmail.com> (raw)
In-Reply-To: <20170330071515.GA4945@kroah.com>

On 03/30/2017 03:15 AM, Greg Kroah-Hartman wrote:
> On Wed, Mar 29, 2017 at 08:20:19PM -0500, Larry Finger wrote:
>> On 03/29/2017 12:47 PM, Hans de Goede wrote:
>>> The rtl8723bs is found on quite a few systems used by Linux users,
>>> such as on Atom systems (Intel Computestick and various other
>>> Atom based devices) and on many (budget) ARM boards such as
>>> the CHIP.
>>>
>>> The plan moving forward with this is for the new clean,
>>> written from scratch, rtl8xxxu driver to eventually gain
>>> support for sdio devices. But there is no clear timeline
>>> for that, so lets add this driver included in staging for now.
>>>
>>> Cc: Bastien Nocera <hadess@hadess.net>
>>> Cc: Larry Finger <Larry.Finger@lwfinger.net>
>>> Cc: Jes Sorensen <jes.sorensen@gmail.com>
>>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>>
>> Hans,
>>
>> I am still building the driver on my CherryTrail tablet, but I did see some
>> warnings and errors listed by Smatch as follows:
>>
[snip]
>> The indent problems can probably be ignored, but many of the others are
>> serious enough to be addressed now.
>>
>> Once this driver is merged into staging, the Outreachy folks will be really busy.
>>
>> Thanks for posting this driver,
>
> So, no objection from you?  Great, I'll go queue it up later today...
>
> thanks,
>
> greg k-h
>

As much as I hate adding more Realtek vendor code to the kernel, I do 
agree this is the right thing to do in the interim. Not sure when I'll 
get to SDIO support in rtl8xxxu, but I will process patches, hint hint :)

Jes

  reply	other threads:[~2017-03-30 14:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170329174751.13184-1-hdegoede@redhat.com>
2017-03-29 17:54 ` [PATCH] staging: Add rtl8723bs sdio wifi driver Hans de Goede
2017-03-30  1:20 ` Larry Finger
2017-03-30  7:15   ` Greg Kroah-Hartman
2017-03-30 14:06     ` Jes Sorensen [this message]
2017-03-30 15:22       ` poma
2017-04-04 18:31 ` Larry Finger
2017-04-04 18:53   ` Hans de Goede
2017-04-04 19:47     ` Larry Finger
2017-04-04 21:38     ` Arend Van Spriel
2017-04-04 21:53       ` Hans de Goede
2017-04-04 23:41         ` Larry Finger
2017-04-05  9:36           ` Hans de Goede
2017-04-05 16:32             ` Larry Finger
2017-04-06  6:55               ` Hans de Goede
2017-04-06  9:04                 ` Bastien Nocera
2017-04-06  9:49                   ` Hans de Goede
2017-04-06 18:32                     ` Larry Finger
2017-04-06 18:36                       ` Jes Sorensen

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=d4f84482-1ed3-7ba5-10ba-406afbe2a372@gmail.com \
    --to=jes.sorensen@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=hadess@hadess.net \
    --cc=hdegoede@redhat.com \
    --cc=linux-wireless@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).