public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: jt@hpl.hp.com
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.5 IrDA] vlsi driver update
Date: Sun, 17 Aug 2003 12:43:48 -0400	[thread overview]
Message-ID: <3F3FB0C4.3000004@pobox.com> (raw)
In-Reply-To: <20030811210354.GD21178@bougret.hpl.hp.com>

Jean Tourrilhes wrote:
> ir2603_vlsi-05.diff :
> ~~~~~~~~~~~~~~~~~~~
> 		<Patch from Martin Diehl>
> * correct endianess conversion of hardware exposed fields
> * we need to check crc16 of rx frames in SIR-mode
>   (hardware does this in MIR/FIR modes). Use irda_calc_crc16.
> * get rid of BUG'gers - having them in interrupt path isn't fun.
> * don't return NET_XMIT_DROP when we drop (dev_kfree_skb_any)
>   frames. This value is meant to ask for retransmit so we would
>   corrupt the skb slab.
> * locking review, corrections and improvements: particularly focus 
>   on speed setting and start_xmit paths, but also reducing time
>   we are staying with interrupts disabled.
> * printk-cleanup: less/better syslog msgs, use IRDA_DEBUG and friends.
> * default qos_mtt_bits should be 1ms or longer (0x07), not exactly 1ms
> * rename IRENABLE_IREN -> IRENABLE_PHYANDCLOCK
> * few minor improvements 
> * compatibility stuff to preserve 2.4 backport path
> * it's a pci controller, so we should depend on CONFIG_PCI
> * DRIVER_VERSION 0.5

this patch needs splitting up


  reply	other threads:[~2003-08-17 16:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-11 21:03 [PATCH 2.5 IrDA] vlsi driver update Jean Tourrilhes
2003-08-17 16:43 ` Jeff Garzik [this message]
2003-08-17 19:14   ` Martin Diehl
2003-08-17 19:38     ` Jeff Garzik
2003-08-18  8:55       ` Martin Diehl
  -- strict thread matches above, loose matches on Subject: below --
2003-08-08 18:54 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=3F3FB0C4.3000004@pobox.com \
    --to=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