Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Wed, 25 May 2022 10:10:20 +0100
From:   Sean Young <sean@mess.org>
To:     Jiri Slaby <jirislaby@kernel.org>
Cc:     Mauro Carvalho Chehab <mchehab@kernel.org>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Andrew Morton <akpm@linux-foundation.org>,
        Linux Media Mailing List <linux-media@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL for v5.18-rc1] media updates
Message-ID: <Yo3yfIim58IWf64z@gofer.mess.org>
References: <20220322101406.459e2950@coco.lan>
 <a0470450-ecfd-2918-e04a-7b57c1fd7694@kernel.org>
 <Yo3ddVHgBBlvJEdh@gofer.mess.org>
 <8093277c-5098-e5e3-f606-486de5b2f67b@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8093277c-5098-e5e3-f606-486de5b2f67b@kernel.org>
Precedence: bulk

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