From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Gregor Jasny <gjasny@googlemail.com>
Cc: linux-media@vger.kernel.org, Hans Verkuil <hverkuil@xs4all.nl>,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: v4l-utils stable release 1.6.1
Date: Thu, 20 Nov 2014 14:15:54 -0200 [thread overview]
Message-ID: <20141120141554.4a2e36e8@recife.lan> (raw)
In-Reply-To: <546E093D.4030203@googlemail.com>
Em Thu, 20 Nov 2014 16:31:09 +0100
Gregor Jasny <gjasny@googlemail.com> escreveu:
> Hello,
>
> do you consider something from these commits as important enough for a
> bugfix release?
>From my side, those are bug fixes that affect two RC6 tables:
ir-keytable: fix a regression introduced by fe2aa5f767eba
rc: Update the protocol name at RC6 tables
Applying just the first is enough. Basically, RC6 tables are described
as RC6_MCE. The first patch makes the ir-keytable to accept both syntaxes;
the second one fixes the two existing RC6_MCE tables.
This one is an important bug fixes for DVB-S/S2 frequency storage:
libdvbv5: properly represent Satellite frequencies
This is not properly a bug fix, but I would also add it, as it fixes the
documentation:
README: better document the package
This is a bug fix, but it affects only the keymap sync from Kernel,
so probably not worth backporting, except if you also intend to run
make sync-with-kernel at the fix tree:
gen_keytables.pl: Fix a regression at RC map file generation
In such case, I also suggest to backport those patches:
rc_maps.cfg: reorder entries alphabetically
rc: sync with Kernel
rc: copy userspace-only maps to a separate dir
This one also seems to be a backport fix:
rc_keymaps: allwinner: S/KEY_HOME/KEY_HOMEPAGE/
That's all from remote controllers and libdvbv5 API side.
Regards,
Mauro
next prev parent reply other threads:[~2014-11-20 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 15:31 v4l-utils stable release 1.6.1 Gregor Jasny
2014-11-20 16:15 ` Mauro Carvalho Chehab [this message]
2014-11-20 20:22 ` Hans de Goede
2014-11-21 19:37 ` Hans Verkuil
2014-11-21 20:03 ` v4l-utils stable release 1.6.2 Gregor Jasny
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=20141120141554.4a2e36e8@recife.lan \
--to=mchehab@osg.samsung.com \
--cc=gjasny@googlemail.com \
--cc=hdegoede@redhat.com \
--cc=hverkuil@xs4all.nl \
--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).