mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Quentin Schulz <quentin.schulz@free-electrons.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	Greg KH <gregkh@linuxfoundation.org>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	shawn.lin@rock-chips.com, adrian.hunter@intel.com,
	baolin.wang@linaro.org, Hans de Goede <hdegoede@redhat.com>,
	maxime.ripard@free-electrons.com,
	thomas.petazzoni@free-electrons.com,
	kernel list <linux-kernel@vger.kernel.org>,
	linux-mmc@vger.kernel.org, devel@driverdev.osuosl.org,
	icenowy@aosc.xyz, wens@csie.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] staging: net: wireless: add ESP8089 WiFi driver
Date: Tue, 25 Jul 2017 11:31:22 +0300	[thread overview]
Message-ID: <87k22wyl2d.fsf@purkki.adurom.net> (raw)
In-Reply-To: <37e6e8f9-8f36-cb78-276d-01f4656c6e47@free-electrons.com> (Quentin Schulz's message of "Fri, 21 Jul 2017 19:05:26 +0200")

(adding linux-wireless)

Quentin Schulz <quentin.schulz@free-electrons.com> writes:

> Hi Marcel,
>
> On 21/07/2017 18:52, Marcel Holtmann wrote:
>> Hi Quentin,
>> 
>>>>> The Espressif ESP8089 WiFi chips can be often found in cheap tablets.
>>>>> There is one in A23 Polaroid tablets for example.
>>>>>
>>>>> The chip is often embedded as an eMMC SDIO device.
>>>>>
>>>>> The code was taken from an out-of-tree repository and has seen a first
>>>>> pass in the cleanup process.
>>>>>
>>>>> At the moment, there is no publicly available datasheet for this chip.
>>>>>
>>>>> Cc: Hans de Goede <hdegoede@redhat.com>
>>>>> Cc: Icenowy Zheng <icenowy@aosc.xyz>
>>>>> Signed-off-by: Quentin Schulz <quentin.schulz@free-electrons.com>
>>>>
>>>> Staging drivers need a TODO file that lists what has to be done to the
>>>> code to get it out of staging.  Why not just take a day or so and fix up
>>>> the remaining issues and get it into the "real" part of the kernel
>>>> correctly?
>>>>
>>>
>>> OK, I'll work on a TODO list. Is there anything else I should know about
>>> staging drivers so I can address everything at the same time?
>>>
>>> From a driver that has already been cleaned up a bit by Icenowy and
>>> Hans, it took me between 10 and 15 working days to this step, which I
>>> estimate to be around 50% of total clean up (and we're only speaking
>>> about coding style and dead code mainly, nothing about a bit of code
>>> review, code robustness...). I find the code not really easy to follow
>>> (might be because I'm a beginner in the subsystem as well).
>>>
>>> I might not be the most efficient person in cleaning up drivers but I'm
>>> pretty sure this isn't a one day cleanup. (Would be happy to be proven
>>> otherwise :) ), else I would have done it as you suggest.
>> 
>> even if it takes you 1 month to clean it up, get it reviewed on
>> linux-wireless and target wireless-drivers instead of staging. When I
>> had a brief a look at your patch, it didn't look like staging
>> material to me.

I did only a 30 sec review (right now no time for proper review because
I have quite a lot of catching up after vacation) but based on what I
saw the driver looks promising. So I agree with Marcel, you should try
to submit this via linux-wireless first and only use staging as the last
resort.

> We don't have a client supporting this effort and I don't think the
> company I work for would support this effort (maybe it would, but
> definitely spread over a long long period), so we're talking about 10-15
> working days spread over my free time/week-end, that isn't for in one
> month :) I could use help for sure on this driver, that's why I posted
> it in staging.
>
> I've done the cleanup on a per-file basis so maybe you looked at one of
> the cleaned up files?
>
> Just to be sure, you're telling me that I should post it as is on
> linux-wireless and then work with the reviews? Or are you telling me to
> take "1 month to clean it up" and then post it on linux-wireless?

I recommend to post the patch to linux-wireless now and see what
comments you get. Then I can also when a proper review and have better
guidance.

-- 
Kalle Valo

  reply	other threads:[~2017-07-25  8:31 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-21 14:35 [PATCH 0/2] add ESP8089 WiFi chip driver Quentin Schulz
2017-07-21 14:35 ` [PATCH 1/2] staging: net: wireless: add ESP8089 WiFi driver Quentin Schulz
2017-07-21 15:01   ` Greg KH
2017-07-21 16:47     ` Quentin Schulz
2017-07-21 16:52       ` Marcel Holtmann
2017-07-21 17:05         ` Quentin Schulz
2017-07-25  8:31           ` Kalle Valo [this message]
2017-07-21 15:01   ` Marcel Holtmann
2017-07-23  7:06   ` kbuild test robot
2017-07-23  8:25   ` [PATCH] staging: net: wireless: fix badzero.cocci warnings kbuild test robot
2017-07-23  8:25   ` [PATCH 1/2] staging: net: wireless: add ESP8089 WiFi driver kbuild test robot
2017-07-25 10:31   ` Dan Carpenter
2017-07-21 14:35 ` [PATCH 2/2] mmc: Add mmc_force_detect_change_begin / _end functions Quentin Schulz
2017-07-22 14:07   ` Shawn Lin
2017-08-30 12:44   ` Hans de Goede
2017-08-30 13:43     ` Ulf Hansson
2018-02-08 14:59       ` Quentin Schulz
2018-02-08 21:31         ` Ulf Hansson
2018-02-09  8:05           ` Quentin Schulz
2018-02-09 14:01             ` Ulf Hansson
2018-03-23  7:25               ` Quentin Schulz
2018-09-26 14:44               ` Frieder Schrempf
2018-09-26 20:19                 ` Hans de Goede
2018-09-27  8:14                   ` Maxime Ripard
2018-10-08  9:53                     ` Frieder Schrempf
2018-10-09  7:52                       ` Quentin Schulz
2018-10-09 14:03                         ` Frieder Schrempf

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=87k22wyl2d.fsf@purkki.adurom.net \
    --to=kvalo@codeaurora.org \
    --cc=adrian.hunter@intel.com \
    --cc=baolin.wang@linaro.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hdegoede@redhat.com \
    --cc=icenowy@aosc.xyz \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=maxime.ripard@free-electrons.com \
    --cc=quentin.schulz@free-electrons.com \
    --cc=shawn.lin@rock-chips.com \
    --cc=thomas.petazzoni@free-electrons.com \
    --cc=ulf.hansson@linaro.org \
    --cc=wens@csie.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

all inboxes | Powered by JetHome®