All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rémi Denis-Courmont" <remi@remlab.net>
To: linux-kernel@vger.kernel.org
Subject: Linux v3.7-rc2 DVB breaks user space compilation
Date: Thu, 15 Nov 2012 21:13:58 +0200	[thread overview]
Message-ID: <201211152113.59057@leon.remlab.net> (raw)

	Hello,

The following patch broke our userspace software builds. While it does 
preserve BINARY compatibility, it breaks SOURCE compatibility as the parameter 
names have changed. I don't see the rationale for breaking compatibility in 
the patch description.

Please consider reverting to the old names. In other words, please remove that 
_LEGACY suffix non-sense or at least define aliases. Thank you.

commit 287cefd096b124874dc4d6d155f53547c0654860
Author: Evgeny Plehov <EvgenyPlehov@ukr.net>
Date:   Thu Sep 13 10:13:30 2012 -0300

    [media] dvb_frontend: add multistream support
    
    Unify multistream support at the DVBAPI: several delivery systems
    allow it. Yet, each one had its own name. So, instead of adding
    a third version of this field, remove the per-standard naming,
    unifying it into a common name.
    
    The legacy code number can still be used by old applications.
    
    Version increased to 5.8.
    
    [mchehab@redhat.com: joined the va1j5jf007s patch, in order to
     avoid compilation breakage]
    Signed-off-by: Evgeny Plehov <EvgenyPlehov@ukr.net>
    Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>

-- 
Rémi Denis-Courmont
http://www.remlab.net/

             reply	other threads:[~2012-11-15 19:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-15 19:13 Rémi Denis-Courmont [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-11-15 19:03 Linux v3.7-rc2 DVB breaks user space compilation Rémi Denis-Courmont

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=201211152113.59057@leon.remlab.net \
    --to=remi@remlab.net \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.