From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: "David S. Miller" <davem@redhat.com>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
irda-users@lists.sourceforge.net
Subject: Bunch of janitor IrDA patches
Date: Wed, 25 Feb 2004 19:10:54 -0800 [thread overview]
Message-ID: <20040226031054.GA32263@bougret.hpl.hp.com> (raw)
Hi Dave,
Stephen and Martin are still working on the stir4200 driver
and will send you a patch later (we are not forgetting about
it). Meanwhile, a problem did show up in smsc-ircc2 driver that need
fixing. I'm also taking this opportunity to send you the vast majority
of janitorial patches that Stephen sent me. There's many of them, but
most are really trivial.
Tested here on 2.6.3. Please send upwards.
Thanks...
Jean
-----------------------------------------------------------------
[FEATURE] : Add a new feature to the IrDA stack
[CORRECT] : Fix to have the correct/expected behaviour
[CRITICA] : Fix potential kernel crash
irXXX_irq_retval_smsc2-fix.diff :
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<Patch from Stephen Hemminger>
o [CORRECT] Fix the handling of shared IRQs in smsc-ircc2 driver.
irXXX_usb_alloc.diff :
~~~~~~~~~~~~~~~~~~~~
<Patch from Stephen Hemminger>
o [FEATURE] Convert irda-usb to dynamic device allocation
irXXX_setup_dma.diff :
~~~~~~~~~~~~~~~~~~~~
<Patch from Stephen Hemminger>
o [FEATURE] Rename setup_dma to irda_setup_dma
=> reduce namepace pollution
irXXX_static_w83977af.diff :
~~~~~~~~~~~~~~~~~~~~~~~~~~
<Patch from Stephen Hemminger>
o [FEATURE] make more symbol static (namespace pollution)
irXXX_static_irtty-sir.diff :
~~~~~~~~~~~~~~~~~~~~~~~~~~~
<Patch from Stephen Hemminger>
o [FEATURE] make more symbol static (namespace pollution)
irXXX_static_via.diff :
~~~~~~~~~~~~~~~~~~~~~
<Patch from Stephen Hemminger>
o [FEATURE] make more symbol static (namespace pollution)
o [FEATURE] remove unused code
irXXX_static_taskkick.diff :
~~~~~~~~~~~~~~~~~~~~~~~~~~
<Patch from Stephen Hemminger>
o [FEATURE] make more symbol static (namespace pollution)
irXXX_ircomm_flags.diff :
~~~~~~~~~~~~~~~~~~~~~~~
<Patch from Stephen Hemminger>
o [FEATURE] volatile not needed, always use set/test_bit
irXXX_infrared_mode.diff :
~~~~~~~~~~~~~~~~~~~~~~~~
<Patch from Stephen Hemminger>
o [FEATURE] remove unused code
irXXX_dev_flags.diff :
~~~~~~~~~~~~~~~~~~~~
<Patch from Stephen Hemminger>
o [FEATURE] remove unused code
irXXX_hashbin_cleanup.diff :
~~~~~~~~~~~~~~~~~~~~~~~~~~
<Patch from Stephen Hemminger>
o [FEATURE] remove unused code
o [FEATURE] add const where needed
irXXX_bogus_include.diff :
~~~~~~~~~~~~~~~~~~~~~~~~
<Patch from Stephen Hemminger>
o [FEATURE] include not needed
irXXX_txqueue_empty.diff :
~~~~~~~~~~~~~~~~~~~~~~~~
<Patch from Stephen Hemminger>
o [FEATURE] optimise irda_device_txqueue_empty by making inline
irXXX_broken_smp.diff :
~~~~~~~~~~~~~~~~~~~~~
<Patch from Stephen Hemminger>
o [FEATURE] mark irport driver has having locking issues
ir263_dongles-12_dup_symbols.diff :
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
o [FEATURE] rename dongle entry points for consistency
next reply other threads:[~2004-02-26 3:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-26 3:10 Jean Tourrilhes [this message]
2004-02-26 20:35 ` David S. Miller
2004-02-26 20:45 ` Jean Tourrilhes
2004-02-26 20:55 ` Stephen Hemminger
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=20040226031054.GA32263@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=davem@redhat.com \
--cc=irda-users@lists.sourceforge.net \
--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®