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: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: DiBxxxx: fixes for 3.1/3.0
Date: Sat, 03 Sep 2011 21:45:06 -0300	[thread overview]
Message-ID: <4E62CA12.8020805@infradead.org> (raw)
In-Reply-To: <alpine.LRH.2.00.1108031728090.30199@pub2.ifh.de>

Em 03-08-2011 12:33, Patrick Boettcher escreveu:
> Hi Mauro,

Thanks for the patches!

> Would you please pull from
> 
> git://linuxtv.org/pb/media_tree.git for_v3.0
> 
> for the following to changesets:
> 
> [media] dib0700: protect the dib0700 buffer access

> -static uint16_t dib0070_read_reg(struct dib0070_state *state, u8 reg)
> +static u16 dib0070_read_reg(struct dib0070_state *state, u8 reg)
>  {
> +	u16 ret;
> +
> +	if (mutex_lock_interruptible(&state->i2c_buffer_lock) < 0) {
> +		dprintk("could not acquire lock");
> +		return 0;

Returning 0 doesn't seem right for me. IMO, it should be return -EAGAIN
or -EINTR (which is, incidentally, what mutex_lock_interruptible() will 
return).

The same applies to the similar parts of the code, at the read and write
routines.

> [media] DiBcom: protect the I2C bufer access
> 
> ?
> 
> Those two changesets are fixing the remaining problems regarding the dma-on-stack-buffer-fix applied for the first time in 2.6.39, IIRC.
> 
> They should go to stable 3.0 (as they are in my tree) and they can be cherry-picked to 3.1.
> 
> We are preparing the same thing for 2.6.39 as the patches don't apply cleanly.
> 
> Thanks to Javier Marcet for his help during the debug-phase.
> 
> thanks and best regards,
> -- 
> 
> Patrick Boettcher - Kernel Labs
> http://www.kernellabs.com/
> -- 
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  parent reply	other threads:[~2011-09-04  0:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-03 15:33 DiBxxxx: fixes for 3.1/3.0 Patrick Boettcher
2011-08-04 13:01 ` David Waring
2011-08-05  8:46 ` Patrick Boettcher
2011-08-28 18:55   ` Jonathan Nieder
2011-09-04  0:45 ` Mauro Carvalho Chehab [this message]
2011-09-05  8:11   ` Olivier Grenie
2011-09-05 13:16     ` Mauro Carvalho Chehab
2011-09-05 13:48       ` Patrick Boettcher

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=4E62CA12.8020805@infradead.org \
    --to=mchehab@infradead.org \
    --cc=linux-media@vger.kernel.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