linux-kernel - Linux v3.7-rc2 DVB breaks user space compilation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <201211152113.59057@leon.remlab.net>
Date:	Thu, 15 Nov 2012 21:13:58 +0200
From:	"Rémi Denis-Courmont" <remi@...lab.net>
To:	linux-kernel@...r.kernel.org
Subject: Linux v3.7-rc2 DVB breaks user space compilation

	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@....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@...hat.com: joined the va1j5jf007s patch, in order to
     avoid compilation breakage]
    Signed-off-by: Evgeny Plehov <EvgenyPlehov@....net>
    Signed-off-by: Mauro Carvalho Chehab <mchehab@...hat.com>

-- 
Rémi Denis-Courmont
http://www.remlab.net/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/