From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: 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.X
Date: Fri, 5 Sep 2003 14:40:30 -0700 [thread overview]
Message-ID: <20030905214030.GA14233@bougret.hpl.hp.com> (raw)
Hi Jeff,
Various IrDA patches. Some you have already seen, some
finishing stuff started, and a few nice critical bugs/race conditions
I spent the week tracking for a user.
Patches tested on 2.6.0-test4, please push to Linus...
Thanks...
Jean
----------------------------------------------------------------------
[FEATURE] : Add a new feature to the IrDA stack
[CORRECT] : Fix to have the correct/expected behaviour
[CRITICA] : Fix potential kernel crash
ir2604_ircomm_owner-2.diff :
~~~~~~~~~~~~~~~~~~~~~~~~~~
o [FEATURE] Finish removing traces of old module refcount stuff
ir260_nsc_39x_fixes.diff :
~~~~~~~~~~~~~~~~~~~~~~~~
<Patch from Jan Frey>
o [CORRECT] Make NSC 3839x probe and init *really* work
The new 3839x code was totally broken.
Won't affect code for regular 38108/38338 chips.
ir2604_irtty_cleanup-2.diff :
~~~~~~~~~~~~~~~~~~~~~~~~~~~
o [FEATURE] Finish removing traces of old irtty driver
ir2604_lap_close_race-5.diff :
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
o [CRITICA] Fix a race condition when closing the LAP
prevent the stack to open new LSAPs while we are killing them.
ir2604_connect_watchdog-5.diff :
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
o [CRITICA] In case of connect watchdog, drop reference to the LAP
o [CORRECT] Prevent dumping LSAP after connect watchdog
o [CRITICA] Prevent dumping TSAP if dumping LSAP did fail
o [CORRECT] Only set connected bit on response if LSAP state is correct
ir2604_init_cleanup-6.diff :
~~~~~~~~~~~~~~~~~~~~~~~~~~
<Patch from Guennadi Liakhovetski>
o [FEATURE] Don't leak stuff in various failure paths
o [FEATURE] Properly initialise self->max_header_size in IrIAP
ir2604_modules_aliases.diff :
~~~~~~~~~~~~~~~~~~~~~~~~~~~
<Patch from Rusty Russell>
o [FEATURE] Add module aliases to dongle drivers
next reply other threads:[~2003-09-05 21:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 21:40 Jean Tourrilhes [this message]
2003-09-06 1:18 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2004-01-08 2:31 Jean Tourrilhes
2004-01-09 10:09 ` David S. Miller
2003-11-05 19:39 Jean Tourrilhes
2003-11-05 19:44 ` David S. Miller
2003-08-08 18:50 Jean Tourrilhes
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=20030905214030.GA14233@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--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®