mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Martin Diehl <lists@mdiehl.de>
Cc: Andrew Morton <akpm@osdl.org>,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.0
Date: Thu, 18 Dec 2003 17:01:42 -0800	[thread overview]
Message-ID: <20031219010142.GA1907@bougret.hpl.hp.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0312190113030.30804-100000@notebook.home.mdiehl.de>

On Fri, Dec 19, 2003 at 01:31:01AM +0100, Martin Diehl wrote:
> 
> I have converted dongle drivers on disk here. So far I was holding back 
> basically due to:
> * 2.6.0 freeze
> * neither hardware nor testers to do even basic validation
> * wait for tx-lock and rawmode fixes to get applied first so we would 
>   hopefully get some more feedback and trust in the infrastructure.

	Yep. Hopefully this will change as more user migrate to 2.6.X.

> If you would like to accept it now I'd sent patches this weekend.

	I'm flying tommorow, and when I'm away, I never read my e-mail.

> > 	o IrCOMM disconnect race condition Oops ; todo
> 
> After some user provided helpful information off-list I found out it gets 
> triggered when the app doesn't close the ircomm-fd before exiting.
> Just do "cat /dev/ircomm0" and kill -9 the cat to see.
> 
> Below my current experimental patch. It works for me and I've got an user
> confirmation meanwhile. It's definedly an improvement and I do think it is 
> as safe as we can get without reworking the whole ircomm-locking...

	Yes, that is more or less what I had suggested.
	Note that I'm unhappy about (self->flags & ASYNC_INITIALIZED),
either it goes under spinlock or use test_bit().

> Martin

	Jean

  reply	other threads:[~2003-12-19  1:01 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-18 23:16 Jean Tourrilhes
2003-12-19  0:31 ` Martin Diehl
2003-12-19  1:01   ` Jean Tourrilhes [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-18 18:12 (->surya<-) 
2003-12-18  5:24 Shawn Starr
2003-12-18  4:14 Linus Torvalds
2003-12-18  4:50 ` Jonathan Brown
2003-12-18  5:00 ` Gerardo Exequiel Pozzi
2003-12-18  5:05 ` Joshua Kwan
2003-12-18  5:07 ` Norberto Bensa
2003-12-18  5:15 ` Andrew Morton
2003-12-18  5:31   ` Jeff Garzik
2003-12-18  5:50   ` Trond Myklebust
2003-12-18  6:14     ` Andrew Morton
2003-12-18  6:41       ` Trond Myklebust
2003-12-18  9:12   ` ismail 'cartman' dönmez
2003-12-18  9:34     ` Greg KH
2003-12-18  9:48     ` Maciej Soltysiak
2003-12-18  9:59       ` Matt H.
2003-12-18 10:19         ` Jens Axboe
2003-12-18 11:00           ` Maciej Soltysiak
2003-12-18 10:43       ` Hans Reiser
2003-12-18 16:17       ` bill davidsen
2003-12-18 19:31         ` Hans Reiser
2003-12-18 19:42           ` Jens Axboe
2003-12-18 22:48             ` Ed Tomlinson
2003-12-19  3:42             ` Hans Reiser
2003-12-19  6:57               ` Jens Axboe
2003-12-18  9:17   ` Marcel Holtmann
2003-12-18 13:43     ` Joseph Pingenot
2003-12-18 16:22       ` Andrew Morton
2003-12-18 14:21   ` Michael Hunold
2003-12-18  5:48 ` Krishna Akella
2003-12-18  7:16 ` Gabor MICSKO
2003-12-18  7:25 ` Clemens Schwaighofer
2003-12-18  9:56 ` Andrew Walrond
2003-12-18 10:20   ` Carlos Jiménez
2003-12-18 12:34 ` iain d broadfoot

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=20031219010142.GA1907@bougret.hpl.hp.com \
    --to=jt@bougret.hpl.hp.com \
    --cc=akpm@osdl.org \
    --cc=jt@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@mdiehl.de \
    /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®