All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, Michael Buesch <mb@bu3sch.de>,
	bcm43xx-dev@lists.berlios.de
Subject: Re: [PATCH] b43: Fix Bluetooth coexistence SPROM coding error for Motorola 7010 variant of BCM4306
Date: Sat, 20 Sep 2008 16:53:52 -0500	[thread overview]
Message-ID: <48D570F0.3070500@lwfinger.net> (raw)
In-Reply-To: <1221945189.3023.17.camel@johannes.berg>

Johannes Berg wrote:
> Yeah, I still wonder where you get the patience to deal with support
> forums, but I think everybody very much appreciates that :)

For the past month, we have been providing day care for our 22-month
old grandson. That pretty much precludes any project that requires
large chunks of time to think a problem through. The support forums
only take a few minutes in each instance. Yes, it gets frustrating at
times. The worst has been when it took 4 tries for a user to get the
command '/sbin/lspci -nnv' entered correctly, and he got it only when
someone else gave him every character that had to be typed.

Larry

      reply	other threads:[~2008-09-20 21:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-19 19:47 [PATCH] b43: Fix Bluetooth coexistence SPROM coding error for Motorola 7010 variant of BCM4306 Larry Finger
2008-09-20 15:44 ` Michael Buesch
2008-09-20 20:51   ` Johannes Berg
2008-09-20 20:59     ` Luis R. Rodriguez
2008-09-20 21:02       ` Johannes Berg
2008-09-20 21:05         ` Luis R. Rodriguez
2008-09-20 21:11           ` Johannes Berg
2008-09-21  0:19             ` Dan Williams
2008-09-21 13:07         ` Michael Buesch
2008-09-20 21:08     ` Larry Finger
2008-09-20 21:13       ` Johannes Berg
2008-09-20 21:53         ` Larry Finger [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=48D570F0.3070500@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mb@bu3sch.de \
    /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.