linux-kernel - Re: [GIT PULL for v5.18-rc1] media updates

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 for Android: free password hash cracker in your pocket

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

Date:   Wed, 25 May 2022 10:10:20 +0100
From:   Sean Young <sean@...s.org>
To:     Jiri Slaby <jirislaby@...nel.org>
Cc:     Mauro Carvalho Chehab <mchehab@...nel.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Linux Media Mailing List <linux-media@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL for v5.18-rc1] media updates

On Wed, May 25, 2022 at 10:09:38AM +0200, Jiri Slaby wrote:
> I don't understand how inability to build software is not an uapi breakage
> -- care to elaborate?

So here is a good compromise suggested by Mauro. 

1. We add the following to the lirc.h uapi header.

#define LIRC_CAN_NOTIFY_DECODE 0 
#define LIRC_CAN_SET_REC_FILTER 0 

2. Since lirc daemon is unmaintained, I am happy to take on maintainership.

This may require forking, depending on what the maintainer says.

How does that sound?


Sean