linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: mb@bu3sch.de
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: pull request: wireless-2.6 2009-10-08
Date: Thu, 08 Oct 2009 18:01:19 -0700 (PDT)	[thread overview]
Message-ID: <20091008.180119.242402327.davem@davemloft.net> (raw)
In-Reply-To: <200910090108.08838.mb@bu3sch.de>

From: Michael Buesch <mb@bu3sch.de>
Date: Fri, 9 Oct 2009 01:08:06 +0200

> I was planning to do a better solution, but I didn't have the time, yet.

The change is harmless while we're twiddling our thumbs waiting
for you to implement the fix "properly."

Not having the fix in is a developer burdon because people turn
on the DMA API debugger and are going to keep reporting it's
complaints here and elsewhere.

Get over your Napoleon complex, and let reasonable working fixes
get into the tree even if you don't find them optimal.  You can
always improve them later, "when you get around to it."

People put fixes in without my ACK in my areas of expertiece all
the time.  I got over it a long time ago, it's OK, and not worth
stressing out over.

Thanks.

  parent reply	other threads:[~2009-10-09  1:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-08 22:34 pull request: wireless-2.6 2009-10-08 John W. Linville
2009-10-08 23:08 ` Michael Buesch
2009-10-08 23:16   ` Michael Buesch
2009-10-09  0:55     ` David Miller
2009-10-09  1:01   ` David Miller [this message]
2009-10-09  8:57     ` Michael Buesch
2009-10-09  9:18       ` David Miller
2009-10-09 13:23   ` John W. Linville
2009-10-09 13:49     ` Michael Buesch
2009-10-09  0:52 ` David Miller

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=20091008.180119.242402327.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --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).