From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>,
irda-users@lists.sourceforge.net,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: IrDA patches on the way...
Date: Fri, 10 May 2002 15:40:26 -0700 [thread overview]
Message-ID: <20020510154026.A14407@bougret.hpl.hp.com> (raw)
Hi Jeff,
Time to dump my current batch of IrDA patches in the
kernel. That will help the current "warning message" squashing
party. Tested on 2.5.15.
Regards,
Jean
-----------------------------------------------------------
[FEATURE] : Add a new feature to the IrDA stack
[CORRECT] : Fix to have the correct/expected behaviour
[CRITICA] : Fix potential kernel crash
ir253_smc_msg.diff :
------------------
<Following patch from Jeff Snyder>
o [CRITICA] Release the proper region and not NULL pointer
o [FEATURE] Fix messages
ir253_long_set_bit.diff :
-----------------------
<Following patch from Paul Mackerras>
o [CORRECT] Argument of set_bit and friends should be unsigned long
Should fix all compile warnings ;-)
ir253_lsap_cache_fix.diff :
-------------------------
<Following patch from Christoph Bartelmus, mangled by me>
o [CORRECT] replace the global LSAP cache with LSAP caches private
to each LAP.
Fix a bug where two simultaneous connections from two devices
using the same LSAPs would get mixed up.
Should also improve performance in similar cases.
next reply other threads:[~2002-05-10 22:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 22:40 Jean Tourrilhes [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-02 23:36 Jean Tourrilhes
2002-08-06 20:48 Jean Tourrilhes
2002-07-16 20:53 Jean Tourrilhes
2002-06-11 0:51 Jean Tourrilhes
2002-04-19 2:27 Jean Tourrilhes
2002-04-03 2:17 Jean Tourrilhes
2002-03-05 22:32 Jean Tourrilhes
2002-01-09 20:00 Jean Tourrilhes
2001-11-30 20:54 Jean Tourrilhes
2001-11-08 3:11 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=20020510154026.A14407@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=irda-users@lists.sourceforge.net \
--cc=jgarzik@mandrakesoft.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®