public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Patrick Boettcher <pboettcher@kernellabs.com>
Cc: Florian Mickler <florian@mickler.org>,
	oliver@neukum.org, linux-kernel@vger.kernel.org,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [media] dib0700: get rid of on-stack dma buffers
Date: Sat, 30 Apr 2011 09:50:32 -0300	[thread overview]
Message-ID: <4DBC0598.9060101@infradead.org> (raw)
In-Reply-To: <20110430114609.53103d67@schatten.dmk.lab>

Patrick,

Em 30-04-2011 06:46, Florian Mickler escreveu:
> On Fri, 29 Apr 2011 18:32:34 -0300
> Mauro Carvalho Chehab <mchehab@infradead.org> wrote:
> 
>> As it is a trivial fix, I'll be picking it directly.
> 
> Zdenek reported in the bug that it doesn't fix all instances of the
> warning. 

Could you please take a look on it?

I'll apply the patch anyway, as at least it will reduce the stack size
and partially fix the issue, but, as Florian and Zdenek pointed, there
are still some cases were stack pointers are used to pass data to URB's,
and this is forbidden (and don't even work on some architectures).

Mauro.

      reply	other threads:[~2011-04-30 12:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-03 17:23 [media] dib0700: get rid of on-stack dma buffers Florian Mickler
2011-04-03 17:23 ` [PATCH 1/2] " Florian Mickler
2011-04-03 17:23 ` [PATCH 2/2] [media] dib0700: remove unused variable Florian Mickler
2011-04-04  7:42 ` [media] dib0700: get rid of on-stack dma buffers Patrick Boettcher
2011-04-04 16:20   ` Florian Mickler
2011-04-04 19:34   ` Florian Mickler
2011-04-29 21:32   ` Mauro Carvalho Chehab
2011-04-30  9:46     ` Florian Mickler
2011-04-30 12:50       ` Mauro Carvalho Chehab [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=4DBC0598.9060101@infradead.org \
    --to=mchehab@infradead.org \
    --cc=florian@mickler.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=oliver@neukum.org \
    --cc=pboettcher@kernellabs.com \
    /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