From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Chris Pockele <chris.pockele.f1@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH] v4l-utils: ir-keytable file parsing errors
Date: Mon, 23 Jan 2012 16:27:21 -0200 [thread overview]
Message-ID: <4F1DA689.9090502@redhat.com> (raw)
In-Reply-To: <CADotOjP-3+CCN+mOaEHFiUUfsyr33zNW0Av8uXSzz0CF0BX1SA@mail.gmail.com>
Em 08-01-2012 21:31, Chris Pockele escreveu:
> Hello,
>
> While configuring a remote control I noticed that the ir-keytable
> utility would throw the message "Invalid parameter on line 1" if the
> first line following the "table ... type: ..." line is a comment.
> Also, if a configuration line is invalid, the line number indication
> of the error message is sometimes incorrect, because the comments
> before it are not counted.
> This happens because of the "continue" statement when processing
> comments (or the table/type line), thus skipping the line counter
> increase at the end of the loop. The included patch fixes both
> problems by making sure the counter is always increased.
> The parse_cfgfile() function had a similar problem.
Applied, thanks.
> For the "table ... type: ..." configuration line at the beginning of a
> keyfile, I suggest replacing the marker character by something
> different from '#'. That way, it can be commented out by the user,
> and it doesn't have to be on the first line. However, that's
> something for another patch and probably up to someone else to decide
> :-). If desirable, I can generate such a patch.
Such patch is welcome, provided that it will keep working with the
old format, in order to not mangle configs with the old format.
Regards,
Mauro
prev parent reply other threads:[~2012-01-23 18:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-08 23:31 [PATCH] v4l-utils: ir-keytable file parsing errors Chris Pockele
2012-01-23 18:27 ` Mauro Carvalho Chehab [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=4F1DA689.9090502@redhat.com \
--to=mchehab@redhat.com \
--cc=chris.pockele.f1@gmail.com \
--cc=linux-media@vger.kernel.org \
/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).