From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: William Lee Irwin III <wli@holomorphy.com>,
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:01:58 -0700 [thread overview]
Message-ID: <20040615170158.GE11105@bougret.hpl.hp.com> (raw)
In-Reply-To: <20040615091219.GR1444@holomorphy.com>
On Tue, Jun 15, 2004 at 02:12:19AM -0700, William Lee Irwin III wrote:
> On Mon, Jun 14, 2004 at 06:43:44PM -0700, Jean Tourrilhes wrote:
> > Could you please send this directly to me. I hate scrubbing
> > large patches from the mailing list archive.
> > Note that before even thinking of pushing this patch in the
> > kernel, we need to perform testing with the hardware on i386 and
> > potentially on ARM. The author only tried with irtty that doesn't use
> > this function, so that's not a valid test at all. Finding people test
> > those changes is going to be tough, as usual.
> > I'm also wondering about the validity of those changes, but
> > that's another matter I need to go through. During 2.5.X, some people
> > assured me that using isa_virt_to_bus was safe on all platform with an
> > ISA bus...
>
> Okay, well, I myself didn't produce this, and I couldn't tell offhand
> if it was bogus or not.
I can't either, that's why we need to check it.
> I presumed bugreporter made happy and spraying
> it across the debian userbase was enough to verify it at runtime. From
> what you're telling me, this is not the case.
IrDA is a special case because there are few users and most
are still using 2.4.X.
> Can you recommend people to do this kind of testing?
Me. I'll also post the patch to the linux-irda mailing list.
> Apparently people aren't entirely happy with "dump it on lkml and wait
> for an ack or nak", which I've noted for future reference, but probably
> won't have a need to consider again (it's very rare that I have to deal
> with changes I didn't write myself or are otherwise in areas I don't
> have much knowledge about).
I'm not a full time Linux hacker, I follow lkml from the
archive. No big deal.
> OTOH, it was easier to find than buried in
> a distro BTS and/or cvs, not that that makes it ideal.
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.
> -- wli
Thanks !
Jean
next prev parent reply other threads:[~2004-06-15 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 1:43 Jean Tourrilhes
2004-06-15 9:12 ` William Lee Irwin III
2004-06-15 17:01 ` Jean Tourrilhes [this message]
2004-06-15 17:35 ` William Lee Irwin III
-- 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=20040615170158.GE11105@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.com \
/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
all inboxes | Powered by JetHome®