linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Pkshih <pkshih@realtek.com>
Cc: "Larry Finger" <Larry.Finger@lwfinger.net>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Dan Carpenter" <dan.carpenter@oracle.com>,
	莊彥宣 <yhchuang@realtek.com>,
	"Johannes Berg" <johannes.berg@intel.com>,
	"Souptick Joarder" <jrdr.linux@gmail.com>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Two rtlwifi drivers?
Date: Wed, 18 Oct 2017 08:33:37 +0300	[thread overview]
Message-ID: <87lgk92f66.fsf@codeaurora.org> (raw)
In-Reply-To: <5B2DA6FDDF928F4E855344EE0A5C39D105821780@RTITMBSV07.realtek.com.tw> (pkshih@realtek.com's message of "Tue, 17 Oct 2017 01:45:45 +0000")

Pkshih <pkshih@realtek.com> writes:

>> My recommendation is to avoid accumulating patches at all cost and start
>> submitting them as soon as you can. This way you get patches committed
>> much more smoother. So do not wait until _all_ patches are ready,
>> instead start submitting patches as soon as you have _some_ patches
>> ready. In other words, keep the delta between mainline and your
>> not-yet-submitted patches as small as possible.
>> 
>> And the patches don't need to be bug free as you can always fix bugs
>> later. Just mention in the commit logs that this is preparation for some
>> new feature and not fully tested yet. We do that all the time, for
>> example Intel's iwlwifi has support for hardware which have not reached
>> customers yet.
>> 
>
> Thanks for your answer. I'll submit patches when the drivers are ready and
> stable. I have another question about the rules of new files. If I want to
> add some new files, could I send a big patch with all new files? Is there
> any limit? 

The only limit I know is the byte size limit in the mailing list. When
submitting a new driver some people split the driver to one file per
patch for easier review but the final commit needs to be one big patch
with all files included. If you are adding big files to rtlwifi I think
you could try to follow the same model.

-- 
Kalle Valo

  reply	other threads:[~2017-10-18  5:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-24 10:08 [PATCH] staging: rtlwifi: check for array overflow Dan Carpenter
2017-08-24 12:14 ` Two rtlwifi drivers? Kalle Valo
2017-08-24 14:41   ` Larry Finger
2017-10-11  9:06     ` Kalle Valo
2017-10-11 13:13       ` Greg Kroah-Hartman
2017-10-11 13:54         ` Dan Carpenter
2017-10-11 14:19         ` Larry Finger
2017-10-12  8:57           ` Kalle Valo
2017-10-12  8:38         ` Kalle Valo
2017-10-12 10:34           ` Greg Kroah-Hartman
2017-10-16  2:41             ` Pkshih
2017-10-16  6:46               ` Oleksij Rempel
2017-10-16 13:07                 ` Kalle Valo
2017-10-16 13:11                   ` Oleksij Rempel
2017-10-16  7:45               ` Dan Carpenter
2017-10-16 13:03                 ` Kalle Valo
2017-10-16  7:50               ` Greg Kroah-Hartman
2017-10-17  1:24                 ` Pkshih
2017-10-16 13:22               ` Kalle Valo
2017-10-17  1:45                 ` Pkshih
2017-10-18  5:33                   ` Kalle Valo [this message]
2017-08-24 18:51 ` [PATCH] staging: rtlwifi: check for array overflow Larry Finger

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=87lgk92f66.fsf@codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=johannes.berg@intel.com \
    --cc=jrdr.linux@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.com \
    --cc=yhchuang@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 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).