From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Tilman Schmidt" <tilman@imap.cc>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ISDN: unsafe interaction between isdn_write and isdn_writebuf_stub
Date: Thu, 20 Apr 2006 00:21:33 +0200 [thread overview]
Message-ID: <9a8748490604191521g7e4b49e8mcf01996d3b2c4e21@mail.gmail.com> (raw)
In-Reply-To: <44457350.4040802@imap.cc>
On 4/19/06, Tilman Schmidt <tilman@imap.cc> wrote:
> On 17.04.2006 04:30, Jesper Juhl wrote:
> > No replies to this patch (below) at all, despite lots of people and
> > lists on CC :-(
> > Ohh well, adding akpm to CC so that perhaps the patch can make it into
> > -mm and at least get some testing.
>
> Yeah, apparently nobody wants to put much work into i4l anymore.
So it would seem.
> Everybody's waiting for it to be replaced by CAPI, only we don't quite
> seem to be there yet.
>
I don't know the state of that, but as long as the i4l stuff is in the
kernel I think we should try to fix bugs when we find them, so I'll
just try to push the patch again in a while.
> Anyway, my development machine has been running with your patch for a
> while, with no apparent ill effects. Although this hardly qualifies as
> exhaustive testing, it does seem do indicate that the patch is on the
> right track.
>
Thanks a lot for trying the patch and your feedback, I really appreciate it.
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2006-04-19 22:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <60xlD-5Y2-13@gated-at.bofh.it>
[not found] ` <62rF9-2nN-7@gated-at.bofh.it>
2006-04-18 23:16 ` Tilman Schmidt
2006-04-19 22:21 ` Jesper Juhl [this message]
2006-04-11 20:05 Jesper Juhl
2006-04-17 2:22 ` Jesper Juhl
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=9a8748490604191521g7e4b49e8mcf01996d3b2c4e21@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tilman@imap.cc \
/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®