linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Jacek Anaszewski <j.anaszewski@samsung.com>, linux-media@vger.kernel.org
Subject: Re: [v4l-utils RFC 0/2] libmediatext library
Date: Thu, 23 Oct 2014 15:13:52 +0200	[thread overview]
Message-ID: <5448FF10.5080204@redhat.com> (raw)
In-Reply-To: <4925721.xPZdUSiM3q@avalon>

Hi,

On 10/23/2014 12:01 PM, Laurent Pinchart wrote:
> On Thursday 23 October 2014 12:40:12 Sakari Ailus wrote:
>> Hi Hans,
>>
>> Hans de Goede wrote:
>>> Maybe we should merge libmediactl into v4l-utils then ? Rather then
>>> v4l-utils growing an external dependency on it. Sakari ?
>>
>> libmediactl is already a part of v4l-utils, but it's under utils rather
>> than lib directory. Cc Laurent.

Ah.

> I'm fine with moving the libraries to lib, but I'm still not 100% sure the ABI 
> can be considered stable.

As long as the ABI is not stable lets keep it in utils and statically link it
into the plugin Jacek is working on for now.

Regards,

Hans

      reply	other threads:[~2014-10-23 13:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21 10:40 [v4l-utils RFC 0/2] libmediatext library Sakari Ailus
2014-10-21 10:40 ` [v4l-utils RFC 1/2] mediactl: Separate entity and pad parsing Sakari Ailus
2014-10-21 10:40 ` [v4l-utils RFC 2/2] mediatext: Add library Sakari Ailus
2014-10-21 13:21 ` [v4l-utils RFC 0/2] libmediatext library Hans de Goede
2014-10-22  9:47   ` Sakari Ailus
2014-10-23  8:19     ` Hans de Goede
2014-10-23  8:54       ` Jacek Anaszewski
2014-10-23  9:31         ` Hans de Goede
2014-10-23  9:40           ` Sakari Ailus
2014-10-23 10:01             ` Laurent Pinchart
2014-10-23 13:13               ` Hans de Goede [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=5448FF10.5080204@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=j.anaszewski@samsung.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@linux.intel.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).