All of lore.kernel.org
 help / color / mirror / Atom feed
From: catchall <catchall@dharty.com>
To: Brendan McGrath <redmcg@redmandi.dyndns.org>,
	Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Steven Toth <stoth@kernellabs.com>
Subject: Re: [PATCHv3] [media] saa7164: use an MSI interrupt when available
Date: Tue, 03 Mar 2015 19:42:54 -0800	[thread overview]
Message-ID: <54F67F3E.4050708@dharty.com> (raw)
In-Reply-To: <1425168893-5251-1-git-send-email-redmcg@redmandi.dyndns.org>

On 02/28/2015 04:14 PM, Brendan McGrath wrote:
> Enhances driver to use an MSI interrupt when available.
>
> Adds the module option 'enable_msi' (type bool) which by default is
> enabled. Can be set to 'N' to disable.
>
> Fixes (or can reduce the occurrence of) a crash which is most commonly
> reported when multiple saa7164 chips are in use. A reported example can
> be found here:
> http://permalink.gmane.org/gmane.linux.drivers.video-input-infrastructure/83948
>
> Reviewed-by: Steven Toth <stoth@kernellabs.com>
> Signed-off-by: Brendan McGrath <redmcg@redmandi.dyndns.org>
>
I wanted to report that I have been running this patch for about a week 
now and I have had no instances of the zero free sequences issue.

Thank you very much!

David


  reply	other threads:[~2015-03-04  3:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-26  3:19 [PATCH] [media] saa7164: use an MSI interrupt when available Brendan McGrath
2015-02-26 15:12 ` Steven Toth
2015-02-26 20:32   ` Kyle Sanderson
2015-02-26 20:45     ` Steven Toth
2015-02-26 23:06       ` Kyle Sanderson
2015-02-26 23:29   ` [PATCHv2] " Brendan McGrath
2015-02-27 16:01     ` Steven Toth
2015-03-01  0:14     ` [PATCHv3] " Brendan McGrath
2015-03-04  3:42       ` catchall [this message]
2015-03-14  3:27       ` [PATCHv4] " Brendan McGrath
2015-04-08 20:43         ` Mauro Carvalho Chehab
2015-04-10  6:39           ` [PATCHv5] " Brendan McGrath
2015-06-05  4:42             ` Kyle Sanderson
2015-06-05  5:09               ` Brendan McGrath

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=54F67F3E.4050708@dharty.com \
    --to=catchall@dharty.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@osg.samsung.com \
    --cc=redmcg@redmandi.dyndns.org \
    --cc=stoth@kernellabs.com \
    --cc=v4l@dharty.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.