From: Gregor Jasny <gjasny@googlemail.com>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Cc: "Linux Media Mailing List" <linux-media@vger.kernel.org>,
"André Roth" <neolynx@gmail.com>
Subject: Re: Upcoming v4l-utils 1.6.0 release
Date: Tue, 30 Sep 2014 17:20:18 +0200 [thread overview]
Message-ID: <542ACA32.3050403@googlemail.com> (raw)
In-Reply-To: <20140927085455.5b0baf89@recife.lan>
Hello,
On 27/09/14 13:54, Mauro Carvalho Chehab wrote:
> Em Sat, 27 Sep 2014 12:57:11 +0200
> Gregor Jasny <gjasny@googlemail.com> escreveu:
>> As far as I understand the service_location feature should work but is
>> an extension to the standard. Does it harm if we keep it until we have
>> something better in place to handle extensions?
>>
>> The service list descriptor feature is unimplemented (and thus broken).
>> Would it help if we return -1 from dvb_desc_service_list_init to reflect
>> that fact or does it break something else? But I'd keep the symbol in
>> the library to maintain ABI compatibility.
> I would actually prefer if we could get rid of those two broken
> descriptors on some release, and to re-add them only when they're
> actually working.
I have sent a patch series to remove the public headers of this two
descriptors and provide stubs to maintain SONAME compatibility.
Could you please ACK it?
Thanks,
Gregor
next prev parent reply other threads:[~2014-09-30 15:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140925213820.1bbf43c2@recife.lan>
2014-09-27 10:57 ` Upcoming v4l-utils 1.6.0 release Gregor Jasny
2014-09-27 11:54 ` Mauro Carvalho Chehab
2014-09-30 15:20 ` Gregor Jasny [this message]
2014-09-30 16:29 ` Hans de Goede
2014-10-04 14:22 ` Mauro Carvalho Chehab
2014-10-05 19:38 ` Gregor Jasny
2014-10-06 0:25 ` Mauro Carvalho Chehab
2014-10-10 20:34 ` Mauro Carvalho Chehab
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=542ACA32.3050403@googlemail.com \
--to=gjasny@googlemail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=neolynx@gmail.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;
as well as URLs for NNTP newsgroup(s).