From: William Lee Irwin III <wli@holomorphy.com>
To: Jean Tourrilhes <jt@bougret.hpl.hp.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [3/12] remove irda usage of isa_virt_to_bus()
Date: Tue, 15 Jun 2004 10:35:43 -0700 [thread overview]
Message-ID: <20040615173543.GB1444@holomorphy.com> (raw)
In-Reply-To: <20040615170158.GE11105@bougret.hpl.hp.com>
On Tue, Jun 15, 2004 at 02:12:19AM -0700, William Lee Irwin III wrote:
>> OTOH, it was easier to find than buried in
>> a distro BTS and/or cvs, not that that makes it ideal.
On Tue, Jun 15, 2004 at 10:01:58AM -0700, Jean Tourrilhes wrote:
> Debian is usually very good sending me bug reports (especiall
> on wireless tools), so I'm a bit surprised that it did not work this
> time. But I've seen a recent trend by Debian to do more Debian
> specific stuff for system level config, which I find disturbing.
These seem to be the ones that have leaked through the cracks. Apart
from this (and the posting is helping to find all the concerned parties)
things should go largely through normal channels in general.
Also, thanks for doing the footwork to get this thing properly
evaluated, as it was unclear to me the risks involved. I don't want
bogus code going in.
-- wli
next prev parent reply other threads:[~2004-06-15 17:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 1:43 [3/12] remove irda usage of isa_virt_to_bus() Jean Tourrilhes
2004-06-15 9:12 ` William Lee Irwin III
2004-06-15 17:01 ` Jean Tourrilhes
2004-06-15 17:35 ` William Lee Irwin III [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-14 0:31 [0/12] Debian bugfixes William Lee Irwin III
2004-06-14 0:33 ` [1/12] don't dereference netdev->name before register_netdev() William Lee Irwin III
2004-06-14 0:34 ` [2/12] lower priority of "too many keys" msg in atkbd.c William Lee Irwin III
2004-06-14 0:36 ` [3/12] remove irda usage of isa_virt_to_bus() William Lee Irwin III
2004-06-14 8:11 ` Christoph Hellwig
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=20040615173543.GB1444@holomorphy.com \
--to=wli@holomorphy.com \
--cc=jt@bougret.hpl.hp.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