From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Pawel Kot <pkot@linuxnews.pl>
Cc: jt@hpl.hp.com, Martin Diehl <lists@mdiehl.de>,
Dag Brattli <dagb@cs.uit.no>,
linux-kernel@vger.kernel.org, linux-irda@pasta.cs.uit.no
Subject: Re: [BUG()] IrDA in 2.4.16 + preempt
Date: Mon, 17 Dec 2001 17:23:35 -0800 [thread overview]
Message-ID: <20011217172335.A3950@bougret.hpl.hp.com> (raw)
In-Reply-To: <20011217161056.F3699@bougret.hpl.hp.com> <Pine.LNX.4.33.0112180214490.662-100000@urtica.linuxnews.pl>
In-Reply-To: <Pine.LNX.4.33.0112180214490.662-100000@urtica.linuxnews.pl>; from pkot@linuxnews.pl on Tue, Dec 18, 2001 at 02:16:16AM +0100
On Tue, Dec 18, 2001 at 02:16:16AM +0100, Pawel Kot wrote:
> On Mon, 17 Dec 2001, Jean Tourrilhes wrote:
>
> > I'm surprised the fix of Martin didn't work...
>
> It did in fact. My apologiese. I have applied it to the wrong kernel tree
> :/
No comment ;-)
> Thanks Martin.
>
> Any chance to have this patch in 2.4.17?
>
> pkot
You see, I try to be a good citizen (even if sometime I feel
very "emotional" about dropped patches). There is already a good chunk
of IrDA patches in 2.4.17, so this will wait 2.4.18. Moreover, this is
"rc1", and I make a point of always sending my patches at the
beggining of the "pre" series and batched.
I have already another IrDA minor cleanup sent to me by Kai
Germaschewski. I'll batch that together. It's not like it's urgent...
Regards,
Jean
prev parent reply other threads:[~2001-12-18 1:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-14 10:31 Pawel Kot
2001-12-17 9:28 ` Martin Diehl
2001-12-17 22:20 ` Pawel Kot
2001-12-17 23:19 ` Pawel Kot
2001-12-17 22:45 ` Jean Tourrilhes
2001-12-17 23:22 ` Pawel Kot
2001-12-18 0:10 ` Jean Tourrilhes
2001-12-18 0:22 ` Pawel Kot
2001-12-18 1:16 ` Pawel Kot
2001-12-18 1:23 ` Jean Tourrilhes [this message]
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=20011217172335.A3950@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=dagb@cs.uit.no \
--cc=jt@hpl.hp.com \
--cc=linux-irda@pasta.cs.uit.no \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@mdiehl.de \
--cc=pkot@linuxnews.pl \
/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®