linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gregor Jasny <gjasny@googlemail.com>
To: unlisted-recipients:; (no To-header on input)@casper.infradead.org
Cc: Wojciech Myrda <vojcek@tlen.pl>, linux-media@vger.kernel.org
Subject: Re: [segfault] running ir-keytable with v4l-utils 0.8.9
Date: Sun, 04 Nov 2012 12:51:01 +0100	[thread overview]
Message-ID: <509656A5.6000902@googlemail.com> (raw)
In-Reply-To: <508BC4F9.303@googlemail.com>

Hello,

On 10/27/12 1:26 PM, Gregor Jasny wrote:
> I looked at the crash and it seems that the rc_dev structure is not
> initialized when a device name is set on the command line. Could you
> please take a look?

I filed this as a Fedora bug report so that it does not get lost:
https://bugzilla.redhat.com/show_bug.cgi?id=872927

Thanks,
Gregor

      reply	other threads:[~2012-11-04 11:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-14 19:54 [segfault] running ir-keytable with v4l-utils 0.8.9 Wojciech Myrda
2012-10-16  7:20 ` Gregor Jasny
2012-10-16  9:08   ` Wojciech Myrda
2012-10-27 11:26 ` Gregor Jasny
2012-11-04 11:51   ` Gregor Jasny [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=509656A5.6000902@googlemail.com \
    --to=gjasny@googlemail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=vojcek@tlen.pl \
    /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;
as well as URLs for NNTP newsgroup(s).