From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: IrDA patches on the way for 2.5.55...
Date: Wed, 8 Jan 2003 18:51:03 -0800 [thread overview]
Message-ID: <20030109025103.GA19178@bougret.hpl.hp.com> (raw)
Hi Jeff,
Now that I can again test IrDA on 2.5.X, this is time to send
you my next set of IrDA patches. I've picked the most important one in
my queue, the rest will come later. Those one have been on my web page
for more than 2 months, tested on 2.5.54 and are fairly important.
Would you mind passing that to Linus ?
Regards,
Jean
P.S. : Happy new year...
P.S.2 : 16bit Pcmcia still doesn't seem to be happy on 2.5.54
-------------------------------------------------------------------
[FEATURE] : Add a new feature to the IrDA stack
[CORRECT] : Fix to have the correct/expected behaviour
[CRITICA] : Fix potential kernel crash
ir254_discovery_locking-2.diff :
------------------------------
o [CRITICA] Fix remaining locking problem with discovery log
o [CRITICA] Don't call expiry callback under spinlock
o [FEATURE] Simplify/cleanup/optimise discovery/expiry code
ir254_driver_module_fixes-2.diff :
--------------------------------
o [CORRECT] Use SET_MODULE_OWNER() in various IrDA drivers
ir254_new_wrapper-3.diff :
------------------------
o [FEATURE] Properly inline in wrapper Tx path
o [FEATURE] Rewrite/simplify/optimise wrapper Rx path
Lower CPU overhead *and* kernel image size
o [FEATURE] Add ZeroCopy in wrapper Rx path for drivers that support it
I'll update drivers later on...
ir254_secondary_rr.diff :
-----------------------
o [CORRECT] fix the secondary function to send RR and frames without
the poll bit when it detect packet losses
ir254_ircomm_dce.diff :
---------------------
<Patch from Jan Kiszka>
o [CORRECT] Properly initialise IrCOMM status line (DCE settings)
reply other threads:[~2003-01-09 2:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030109025103.GA19178@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.