From: "Jeff V. Merkey" <jmerkey@wolfmountaingroup.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: hda-intel woes
Date: Wed, 29 Mar 2006 11:18:05 -0700 [thread overview]
Message-ID: <442ACF5D.90805@wolfmountaingroup.com> (raw)
In-Reply-To: <442AC08D.5040800@tmr.com>
Bill Davidsen wrote:
> Jeff V. Merkey wrote:
>
>> I wasn;t trying to be flippant or rude, I was simply pointing this
>> person to a website where they might find answers. Most users are
>> not programmers and expecting them to debug patches and rebuild a
>> kernel (which won't work in most cases because of forking and massive
>> patches by the DISTRO vendors) .
>
>
> Since at least one other person mentioned that your reply was harsh,
> leave it that your intentions were good and you weren't intentionally
> impolitic.
>
>> Linux has grown up. People using laptops with distros will find a
>> lot of answers on these forums.
>> How about wireless drivers? Bcm drivers for example. Written as
>> NDIS and using ndiswrapper. Laptop issues are complicated and not
>> general bugs. LKML isn;t useful to address these issues. I don't
>> even get responses on AMD issues and I do kernel development all day
>> long. And I don't use stock kernel.org releases any longer since
>> the distro's have forked so extensively.
>
>
> Since the issue is/was in the kernel.org release, the question wasn't
> really out of place. As noted ASUS sound hasn't worked forever, and
> last night I was curious about the claims that it was fixed, and lo...
> I have sound in 2.6.16.1. Of course my webcam stopped working, so now
> that I can play back my meeting notes I can't record the meeting :-(
> That's not a trouble report, I have to look at all my config stuff first.
Thanks for the kind response. I will not be so abrupt next time.
Jeff
>
>
next prev parent reply other threads:[~2006-03-29 17:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-27 23:10 hda-intel woes Friedrich Göpel
2006-03-28 0:45 ` Jeff V. Merkey
2006-03-28 0:22 ` Friedrich Göpel
2006-03-28 1:22 ` Kyle Moffett
2006-03-28 1:28 ` Lee Revell
2006-03-28 16:57 ` Friedrich Göpel
2006-03-28 23:10 ` Bill Davidsen
2006-03-29 0:21 ` Jeff V. Merkey
2006-03-29 17:14 ` Bill Davidsen
2006-03-29 18:18 ` Jeff V. Merkey [this message]
2006-03-28 8:29 ` Petri Kaukasoina
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=442ACF5D.90805@wolfmountaingroup.com \
--to=jmerkey@wolfmountaingroup.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@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