From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Michael Buesch <mb@bu3sch.de>,
linville@tuxdriver.com, Christian <email@christianhoffmann.info>,
netdev@vger.kernel.org
Subject: Re: [PATCH] softmac: Fix WX and association related races
Date: Thu, 28 Sep 2006 11:04:10 +1000 [thread overview]
Message-ID: <1159405450.9974.8.camel@localhost.localdomain> (raw)
In-Reply-To: <451B1AB0.9020302@lwfinger.net>
On Wed, 2006-09-27 at 19:43 -0500, Larry Finger wrote:
> Benjamin Herrenschmidt wrote:
> >>
> > I won't try some random other git tree to test things, it's simply not
> > feasible for me and we need something we can give to distros to backport
> > so they have something remotely stable (I'm thinking for example about
> > the upcoming ubuntu edgy which is coming out soon an a 2.6.17 base).
>
> I don't know what your problem is! Despite your negative attitude, I have tried to accommodate you,
> but obviously you do not appreciate my efforts. My big patch for 2.6.18 concentrated on bcm43xx. Yes
> there were changes in softmac, but they had no major effect until Michael's fix of the race condition.
>
> The bottom line is that I have had it with you! You had best go back to some mainline kernel as you
> will get no further help from me. There are lots of folks that need help _AND_ are appreciative of
> that help. My time will be spent on them.
Maybe because I'm a hot blooded asshole :)
Note that I wasn't complaining about your patch (which is a bit huge tho
for a stable release, but it did make a difference here along with
Michael debug one). I just noticed that none of Michael last "final"
patches would apply on 2.6.18 + your patch, and went into my usual rant
in case they were supposed to apply to the wireless tree.
There is a number of reasons why people can't just use a wireless-git or
whatever else tree, and having something against mainline is the only
way I see to get something to distros now, which is the way to fix the
most people problems rather than only the ones finding this mailing
list.
Ben.
next prev parent reply other threads:[~2006-09-28 1:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 15:26 [PATCH] softmac: Fix WX and association related races Michael Buesch
2006-09-27 16:18 ` Larry Finger
2006-09-27 17:50 ` Michael Buesch
2006-09-27 21:11 ` Christian
2006-09-27 21:21 ` Christian
2006-09-27 22:23 ` Benjamin Herrenschmidt
2006-09-28 0:43 ` Larry Finger
2006-09-28 1:04 ` Benjamin Herrenschmidt [this message]
2006-09-28 4:09 ` Larry Finger
2006-09-28 12:55 ` Michael Buesch
2006-09-28 14:19 ` Dan Williams
2006-09-28 14:27 ` Johannes Berg
2006-09-28 14:37 ` Dan Williams
2006-09-28 14:43 ` Michael Buesch
2006-09-28 14:52 ` Dan Williams
2006-09-28 15:13 ` Michael Buesch
2006-09-28 17:33 ` Jouni Malinen
2006-09-28 15:16 ` Larry Finger
2006-09-28 15:29 ` Michael Buesch
2006-09-28 15:35 ` Michael Wu
2006-09-28 15:52 ` Larry Finger
2006-09-28 16:31 ` Jason Lunz
2006-09-28 17:04 ` Larry Finger
2006-09-28 17:14 ` Michael Buesch
2006-09-28 17:40 ` Larry Finger
2006-09-28 14:43 ` Johannes Berg
2006-09-27 22:20 ` Benjamin Herrenschmidt
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=1159405450.9974.8.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=Larry.Finger@lwfinger.net \
--cc=email@christianhoffmann.info \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=netdev@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).