From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: "David S. Miller" <davem@davemloft.net>,
Jeff Garzik <jgarzik@pobox.com>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
irda-users@lists.sourceforge.net
Subject: IrDA patches for 2.6.10-rc3
Date: Wed, 8 Dec 2004 17:50:54 -0800 [thread overview]
Message-ID: <20041209015054.GA2298@bougret.hpl.hp.com> (raw)
Hi David,
There is some trivial fixes for some serious driver bug that
did show up in my mailbox. Because the fixes are trivial and the bug
serious, I would like to push that into 2.6.10 final.
I tested the irda-usb patch, and Stephen tested the stir4200
patch. The VIA driver case is messy : I did the minimal fix that I
could get away with, because I don't have the hardware to test and the
proper fix will require much more work.
Just push that up ;-)
Jean
-------------------------------------------------------------
ir260_via_pci_hack.diff :
~~~~~~~~~~~~~~~~~~~~~~~
<Bugfix suggested by Arkadiusz Miskiewicz>
o [CORRECT] Try to fix the worse abuse of the pci init code in via_ircc
Signed-off-by: Jean Tourrilhes <jt@hpl.hp.com>
irXXX_stir4200-kill-1.diff :
~~~~~~~~~~~~~~~~~~~~~~~~~~
<Original patch from Stephen Hemminger>
USB changed behaviour of unlink_urb so that it gives warning and backtrace when
being used synchronously. The correct current behaviour is to us kill_urb
in that case.
Signed-off-by: Stephen Hemminger <shemminger@osdl.org>
Signed-off-by: Jean Tourrilhes <jt@hpl.hp.com>
ir260_irda-usb-kill-2.diff :
~~~~~~~~~~~~~~~~~~~~~~~~~~
<Original patch from Stephen Hemminger>
Updates for irda-usb.
* change comment about Sigmatel now that there is a driver
* convert to new module_param
* places where urb is unlinked synchronously, use usb_kill_urb
because that is now a runtime warning.
Signed-off-by: Stephen Hemminger <shemminger@osdl.org>
Signed-off-by: Jean Tourrilhes <jt@hpl.hp.com>
next reply other threads:[~2004-12-09 1:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 1:50 Jean Tourrilhes [this message]
2004-12-09 4:56 ` David S. 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=20041209015054.GA2298@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=davem@davemloft.net \
--cc=irda-users@lists.sourceforge.net \
--cc=jgarzik@pobox.com \
--cc=jt@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
all inboxes | Powered by JetHome®