All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: linux-wireless@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>,
	libertas-dev@lists.infradead.org
Subject: Re: [PATCH] move wlan_*_association_work from header to c file
Date: Tue, 06 Nov 2007 09:20:56 -0500	[thread overview]
Message-ID: <1194358856.12229.3.camel@localhost.localdomain> (raw)
In-Reply-To: <200711061351.14673.hs4233@mail.mn-solutions.de>

On Tue, 2007-11-06 at 13:51 +0100, Holger Schurig wrote:
> > The 2nd patch "libertas: move to uniform lbs_/LBS_ namespace"
> > breaks the compile of if_sdio.c, so I had to drop it.  I
> > dropped "libertas: clean up association debug messages" as
> > well.
> 
> I didn't see an if_sdio.c in my tree when I made the patch.
> 
> And I wont make a third patch. It's quite discouraging to send 
> things which don't get applied (for no known reasons) for more 
> than a week. And during that time they bitrot. Would the patch 
> have been applied timely, it would have worked in the first 
> place.

This is the way things work.  The patch clearly was not material for
2.6.24 given the timing.  Therefore, it's 2.6.25.  Therefore, since
if_sdio.c was ready to go in _August_, it hit 2.6.24, but you didn't
have it because your patch was based on 2.6.23, not 2.6.24-rc1.  That's
distributed development.  If you want a feature, you have to keep coming
back until it gets where you need to go, if you want the benefits of
distributed development.

> Also, changing all things wlan_XXX in libertas_XXX is soooo easy. 
> However, I won't do it. The one who originally asked for the 
> cleanup patch should do the work and have the patience to get 
> the patch through, I have real work to do.

In any case, thanks for the work.  I'll see if I can pick it up.

Dan


  reply	other threads:[~2007-11-06 14:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11  9:51 [PATCH] move wlan_*_association_work from header to c file Holger Schurig
2007-10-11 11:05 ` Dan Williams
2007-10-11 12:57 ` John W. Linville
2007-10-11 14:16 ` Christoph Hellwig
2007-10-11 14:50   ` Dan Williams
2007-10-15  7:18     ` Holger Schurig
     [not found]       ` <200710151247.31049.hs4233@mail.mn-solutions.de>
2007-10-15 10:58         ` [PATCH] libertas: move to uniform lbs_/LBS_ namespace Holger Schurig
2007-10-15 11:07           ` Holger Schurig
2007-10-15 11:21             ` Johannes Berg
2007-10-15 12:26               ` Holger Schurig
2007-10-15 14:13       ` [PATCH] move wlan_*_association_work from header to c file Dan Williams
2007-10-15 14:28         ` Holger Schurig
2007-10-15 14:42           ` Dan Williams
2007-10-15 14:49             ` Holger Schurig
2007-10-15 16:43               ` Dan Williams
2007-10-22 17:20                 ` Dan Williams
2007-10-25  8:37                   ` Holger Schurig
2007-10-25 13:55                     ` Dan Williams
2007-10-26 11:43                     ` Holger Schurig
2007-11-06  1:16                       ` John W. Linville
2007-11-06 12:51                         ` Holger Schurig
2007-11-06 14:20                           ` Dan Williams [this message]
2007-10-22 17:17 ` Dan Williams

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=1194358856.12229.3.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=hs4233@mail.mn-solutions.de \
    --cc=libertas-dev@lists.infradead.org \
    --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 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.