public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@bytesex.org>
To: linux-kernel@vger.kernel.org
Subject: Re: reducing stack usage in v4l?
Date: 05 Mar 2003 13:28:30 +0100	[thread overview]
Message-ID: <87llzugfpt.fsf@bytesex.org> (raw)
In-Reply-To: 1046865047.2310.33.camel@nirvana.flat

mdew <mdew@mdew.dyndns.org> writes:

> On the topic of v4l, Ive had complete lockups on recent 2.5.x kernels
> when loading a v4l application Zapping.

There are a few known issues, pushing updates to Linus is on my todo list.
If it still happens with the latest bits from http://bytesex.org/snapshot/
I'd like to know.

  Gerd

-- 
/join #zonenkinder

      reply	other threads:[~2003-03-05 12:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-05  5:25 reducing stack usage in v4l? Randy.Dunlap
2003-03-05  5:43 ` Andrew Morton
2003-03-05  9:15 ` Gerd Knorr
2003-03-05  9:35   ` Russell King
2003-03-05 15:34     ` Randy.Dunlap
2003-03-05 21:40       ` Jörn Engel
2003-03-11  4:27       ` Randy.Dunlap
2003-03-11  9:19         ` Gerd Knorr
2003-03-11 16:29           ` Alan Cox
2003-03-11 15:36             ` Daniel Jacobowitz
2003-03-05 11:50   ` mdew
2003-03-05 12:28     ` Gerd Knorr [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=87llzugfpt.fsf@bytesex.org \
    --to=kraxel@bytesex.org \
    --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