public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: "Steinar H. Gunderson" <sesse@samfundet.no>
Cc: Manu Abraham <abraham.manu@gmail.com>,
	LMML <linux-media@vger.kernel.org>
Subject: Re: Status of the patches under review at LMML (35 patches)
Date: Thu, 24 Jan 2013 18:39:57 -0200	[thread overview]
Message-ID: <20130124183957.2e81cac4@redhat.com> (raw)
In-Reply-To: <CAHFNz9JjP1ZjLM67SA-01raNKcoUjVmD8-2JfkDe=hHAB61Lig@mail.gmail.com>

Steinar,

Please see the comments below.

Regards,
Mauro

Em Tue, 15 Jan 2013 16:57:26 +0530
Manu Abraham <abraham.manu@gmail.com> escreveu:

> > Apr, 1 2012: [05/11] Slightly more friendly debugging output.                       http://patchwork.linuxtv.org/patch/10520  "Steinar H. Gunderson" <sesse@samfundet.no>
> 
> Simply a cosmetic patch. Doesn't bring any advantage. Knowing what
>  MMIO address failed doesn't help at all. If you have failures, then you
> will have failures with the entire mapped addresses. So AFAICT, this
> patch doesn't bring any advantage to help in additional debugging either.
> 
> 
> > Apr, 1 2012: [06/11] Replace ca_lock by a slightly more general int_stat_lock.      http://patchwork.linuxtv.org/patch/10521  "Steinar H. Gunderson" <sesse@samfundet.no>
> 
> 
> This is actually sleeping in interrupt context. All it does is a cosmetic
> name change and adding a mutex across the IRQ handler, which is
>  not a valid thing to do.
> 
> > Apr, 1 2012: [07/11] Fix a ton of SMP-unsafe accesses.                              http://patchwork.linuxtv.org/patch/10523  "Steinar H. Gunderson" <sesse@samfundet.no>
> 
> 
> Use of volatile .. I am not sure. It does need a lock someplace, but I am
> not sure whether this patch is doing correctly at all.

True.

Steinar, volatile generally doesn't work in kernel. You should either use
RCU, atomic_t or some locking to protect the data access instead.

> 
> 
> > Apr, 1 2012: [08/11] Remove some unused structure members.                          http://patchwork.linuxtv.org/patch/10525  "Steinar H. Gunderson" <sesse@samfundet.no>
> 
> 
> The enumeration holds the status of the SmartBuffer, currently it is not
> being checked against. Deleting it might not be a useful thing.. ? Though
> the gpif_status in the mantis_dev structure could be removed, thus
> removing a dereference.
> 
> 
> > Apr, 1 2012: [09/11] Correct wait_event_timeout error return check.                 http://patchwork.linuxtv.org/patch/10526  "Steinar H. Gunderson" <sesse@samfundet.no>
> 
> Patch is correct, but likely needs to be regenerated, being dependant on
> another patch
> 
> 
> > Apr, 1 2012: [10/11] Ignore timeouts waiting for the IRQ0 flag.                     http://patchwork.linuxtv.org/patch/10527  "Steinar H. Gunderson" <sesse@samfundet.no>
> 
> There is something really wrong going on. The CPU went into a loop and
> hence reads do not return. Ignoring timeouts doesn't seem the proper way
> to me.
> 
> 
> > Apr, 1 2012: [11/11] Enable Mantis CA support.                                      http://patchwork.linuxtv.org/patch/10524  "Steinar H. Gunderson" <sesse@samfundet.no>
> 
> Not yet there.


-- 

Cheers,
Mauro

  parent reply	other threads:[~2013-01-24 20:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-06 13:34 Status of the patches under review at LMML (35 patches) Mauro Carvalho Chehab
2013-01-07  5:56 ` Prabhakar Lad
2013-01-07 12:13   ` Laurent Pinchart
2013-01-07 12:34     ` Prabhakar Lad
2013-01-07  9:51 ` Sylwester Nawrocki
2013-01-07 12:22 ` Laurent Pinchart
2013-01-07 12:29 ` Guennadi Liakhovetski
2013-01-07 16:31 ` Manu Abraham
2013-01-15 11:27 ` Manu Abraham
2013-01-24 20:33   ` Mauro Carvalho Chehab
2013-01-24 20:35   ` Mauro Carvalho Chehab
2013-01-24 20:39   ` Mauro Carvalho Chehab [this message]
2013-01-24 20:57     ` Steinar H. Gunderson

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=20130124183957.2e81cac4@redhat.com \
    --to=mchehab@redhat.com \
    --cc=abraham.manu@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sesse@samfundet.no \
    /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