Linux Media Controller development
 help / color / mirror / Atom feed
From: Jarod Wilson <jarod@redhat.com>
To: Corinna Vinschen <vinschen@redhat.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH] imon: don't wedge hardware after early callbacks
Date: Wed, 25 Jan 2012 17:11:55 -0500	[thread overview]
Message-ID: <4F207E2B.7060307@redhat.com> (raw)
In-Reply-To: <20120125221136.GX2456@calimero.vinschen.de>

Corinna Vinschen wrote:
> Hi Jarod,
>
> On Jan 25 15:56, Jarod Wilson wrote:
>> This patch is just a minor update to one titled "imon: Input from ffdc
>> device type ignored" from Corinna Vinschen. An earlier patch to prevent
>> an oops when we got early callbacks also has the nasty side-effect of
>> wedging imon hardware, as we don't acknowledge the urb. Rework the check
>> slightly here to bypass processing the packet, as the driver isn't yet
>> fully initialized, but still acknowlege the urb and submit a new rx_urb.
>> Do this for both interfaces -- irrelevant for ffdc hardware, but
>> relevant for newer hardware, though newer hardware doesn't spew the
>> constant stream of data as soon as the hardware is initialized like the
>> older ffdc devices, so they'd be less likely to trigger this anyway...
>
> just a question, wouldn't it make sense to bump the version number of the
> module to 0.9.4?  Or do you do that for functional changes only?

I've not been terribly consistent with it, but it does seem the last 
time I bumped the version number *was* to have an easy way to tell if a 
particular fix was included or not. We can bump it here too, doesn't 
really matter to me.

-- 
Jarod Wilson
jarod@redhat.com



  reply	other threads:[~2012-01-25 22:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-24 20:36 [PATCH] imon: Input from ffdc device type ignored Corinna Vinschen
2012-01-25 20:56 ` [PATCH] imon: don't wedge hardware after early callbacks Jarod Wilson
2012-01-25 22:11   ` Corinna Vinschen
2012-01-25 22:11     ` Jarod Wilson [this message]
2012-01-25 22:24       ` Corinna Vinschen
2012-01-26 15:33   ` [PATCH v2] " Jarod Wilson
2012-01-26 16:04     ` [PATCH] " Jarod Wilson

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=4F207E2B.7060307@redhat.com \
    --to=jarod@redhat.com \
    --cc=linux-media@vger.kernel.org \
    --cc=vinschen@redhat.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