From: Luciano Coelho <luciano.coelho@nokia.com>
To: "ext John W. Linville" <linville@tuxdriver.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 00/24] wl1271: bunch of patches from our internal tree wk12
Date: Fri, 26 Mar 2010 15:37:13 +0200 [thread overview]
Message-ID: <1269610633.22348.29.camel@powerslave> (raw)
In-Reply-To: <20100326132632.GD15128@tuxdriver.com>
On Fri, 2010-03-26 at 14:26 +0100, ext John W. Linville wrote:
> On Fri, Mar 26, 2010 at 03:13:15PM +0200, Luciano Coelho wrote:
> > On Fri, 2010-03-26 at 14:02 +0100, ext John W. Linville wrote:
> > > On Fri, Mar 26, 2010 at 12:53:09PM +0200, Luciano Coelho wrote:
> > >
> > > > Here are 25 more patches for wl1271 which are still pending in our internal
> > > > tree. Please apply. :)
> > >
> > > Are we catching-up? Or will these dumps continue indefinitely?
> >
> > Now we have finally caught up! Sorry for the mess, but we haven't been
> > sending patches for a while and they really got delayed.
> >
> > The idea from now on is to send them weekly (still in patch-sets), but
> > not so many at once. We review and test our patches internally before
> > sending upstream, that's why we have to send them in batches.
>
> Apparently Nokia, Intel, and maybe Atheros need to form some sort of
> support group -- Patch-hoarder's Anonymous... :-)
LOL!
> > I'm currently reconsidering this process and trying to figure out how we
> > can do things in a simpler way. We are already doing all our mac80211
> > work upstream, but for the driver we haven't found a good solution yet.
> >
> > Would you prefer to pull stuff from a git tree instead of applying the
> > patches?
>
> It doesn't make a great deal of difference to me. I have been pulling
> from Intel for a little while now, and that has worked-out fairly
> well from my perspective. But, applying patchbombs is usually easy
> so long as there hasn't been lots of other activity in the driver.
> So, whatever is convenient for you is probably acceptable to me.
Good that this hasn't been causing too much extra work for you. If you
have any trouble applying the patches I send, just let me know and I'll
fix it.
I think the main drawback of sending patchbombs is that we don't get
good reviews from the community. Nobody wants to dig into a so many
patches at once, so it would probably be much better to have the patches
sent one-by-one (or in relevant sets). Unfortunately, we still have
many internal rounds before we're satisfied with the patches. But I'll
see if we can change that.
Tfyh! :)
--
Cheers,
Luca.
prev parent reply other threads:[~2010-03-26 13:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 10:53 [PATCH 00/24] wl1271: bunch of patches from our internal tree wk12 Luciano Coelho
2010-03-26 10:53 ` [PATCH 01/24] wl1271: fix wl1271_spi driver name Luciano Coelho
2010-03-26 10:53 ` [PATCH 02/24] wl1271: Clean up RX rate reporting Luciano Coelho
2010-03-26 10:53 ` [PATCH 03/24] wl1271: Add TX " Luciano Coelho
2010-03-26 10:53 ` [PATCH 04/24] wl1271: Fix memory leaks in SPI initialization Luciano Coelho
2010-03-26 10:53 ` [PATCH 05/24] wl1271: Fix memory leak in scan command handling Luciano Coelho
2010-03-26 10:53 ` [PATCH 06/24] wl1271: Configure clock-request drive mode to open-drain Luciano Coelho
2010-03-26 10:53 ` [PATCH 07/24] wl1271: Warnings caused by wrong format specifiers fixed Luciano Coelho
2010-03-26 10:53 ` [PATCH 08/24] wl1271: Fix memory leak in cmd_data_path Luciano Coelho
2010-03-26 10:53 ` [PATCH 09/24] wl1271: Update busyword checking mechanism Luciano Coelho
2010-03-26 10:53 ` [PATCH 10/24] wl1271: Remove device MAC-address randomization Luciano Coelho
2010-03-26 10:53 ` [PATCH 11/24] wl1271: wait for join command complete event Luciano Coelho
2010-03-26 10:53 ` [PATCH 12/24] wl1271: wait for disconnect " Luciano Coelho
2010-03-26 10:53 ` [PATCH 13/24] wl1271: remove deprecated usage of RX status noise Luciano Coelho
2010-03-26 10:53 ` [PATCH 14/24] wl1271: Disable connection monitoring while not associated Luciano Coelho
2010-03-26 10:53 ` [PATCH 15/24] wl1271: Fix ad-hoc mode handling Luciano Coelho
2010-03-26 10:53 ` [PATCH 16/24] wl1271: Update beacon interval properly for ad-hoc Luciano Coelho
2010-03-26 10:53 ` [PATCH 17/24] wl1271: Removed checking of PSM from handling BSS_LOST_EVENT Luciano Coelho
2010-03-26 10:53 ` [PATCH 18/24] wl1271: Fix memory leak in firmware crash scenario Luciano Coelho
2010-03-26 10:53 ` [PATCH 19/24] wl1271: Configure probe-request template when associated Luciano Coelho
2010-03-26 10:53 ` [PATCH 20/24] wl1271: Disconnect if PSM entry fails Luciano Coelho
2010-03-26 10:53 ` [PATCH 21/24] wl1271: Configure HW connection monitor Luciano Coelho
2010-03-26 10:53 ` [PATCH 22/24] wl1271: Add keep-alive frame template support Luciano Coelho
2010-03-26 10:53 ` [PATCH 23/24] wl1271: Enable hardware keep alive messages Luciano Coelho
2010-03-26 10:53 ` [PATCH 24/24] wl1271: Fix msleep() delay while waiting for completion Luciano Coelho
2010-03-26 13:02 ` [PATCH 00/24] wl1271: bunch of patches from our internal tree wk12 John W. Linville
2010-03-26 13:13 ` Luciano Coelho
2010-03-26 13:26 ` John W. Linville
2010-03-26 13:37 ` Luciano Coelho [this message]
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=1269610633.22348.29.camel@powerslave \
--to=luciano.coelho@nokia.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).