All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/5] b43: Use the b43_phy_maskset where possible
Date: Tue, 18 Mar 2008 02:00:09 +0100	[thread overview]
Message-ID: <200803180200.09331.mb@bu3sch.de> (raw)
In-Reply-To: <1205801249.2329.49.camel@brick>

On Tuesday 18 March 2008 01:47:29 Harvey Harrison wrote:
> [lots of patches]

What do these patches actually fix?
I see they shuffle a _lot_ of code around, but what does that
actually fix? As I said, I won't apply any patch that just shuffles
code without fixing anything.

This shuffling has a _HUGE_ risk of introducing bugs that I am NOT
going to debug and fix afterwards.
The code works pretty well. There's absolutely no need to rewrite it.

And no, "this makes the code 200bytes smaller" doesn't count as a fix. :)

We do _not_ understand what this code does and it is a really really huge
pain in the ass to debug. So I am not going to risk bugs here.

Please search for another target, like the b43-MAC code (everything except
the PHY stuff).
Of course, if you found an actual bug in the PHY code, I'd like to know
and I'd like to have a patch that fixes it without shuffling hundreds
of lines of code.

Thanks a lot.

-- 
Greetings Michael.

  reply	other threads:[~2008-03-18  1:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-18  0:47 [PATCH 1/5] b43: Use the b43_phy_maskset where possible Harvey Harrison
2008-03-18  1:00 ` Michael Buesch [this message]
2008-03-18  1:10   ` Harvey Harrison
2008-03-18  1:20     ` Michael Buesch

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=200803180200.09331.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=harvey.harrison@gmail.com \
    --cc=linux-wireless@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 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.