From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 36B76C433F5 for ; Wed, 25 May 2022 10:46:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242700AbiEYKqm (ORCPT ); Wed, 25 May 2022 06:46:42 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53454 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242740AbiEYKqa (ORCPT ); Wed, 25 May 2022 06:46:30 -0400 Received: from mail-wr1-f42.google.com (mail-wr1-f42.google.com [209.85.221.42]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1CE4D3883; Wed, 25 May 2022 03:46:17 -0700 (PDT) Received: by mail-wr1-f42.google.com with SMTP id s28so29406746wrb.7; Wed, 25 May 2022 03:46:17 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=q9O1OGub18poRLHhomCuCLAnpIgun6gCJciHoCwZhXQ=; b=wA/YoIextkItkfmZItfuS7mejwxz8PsmEAKDT4vZx8EpiRHx1TE8gFkLmtX9xheRc3 lK5I0eUiyUKznBvKrM7SH+UgwyXhcoyIB6XIcIUvO/ziJGM2c98Gt+1q+F3U7g3gRgJ8 LVYhMIAUUK4PVtoICjP224JC6a9m+RR3JJPS+DzwQ+2YDdQrTAUWL1tTGDQxh9WTBnVQ vwLTo/ozhziXa95gH/K2rFR21SnYalChKlM3KNvAXoRDKA893YMhTOUiPUwuFRhHNE0M 1+HbRL4weXl26dZWHv2GekwdHogexfuZWuLgxFZayXrPO/OXY+VnjafyXDRPeikKjtFG OMlQ== X-Gm-Message-State: AOAM532XuZTFeb+6kIXgOGq5zzgN1ZyWYcaujBL86lVNcZy0yy5Ufgsf 3X3iaXxPlcGixlH+Q8kDmzg= X-Google-Smtp-Source: ABdhPJwhLX2ksgGaO2ZVtVM7fwP7bpSx5WD8AGN1rT0/bqTlC+CbpGatSQsTaU+IqjT+1iHA5Laoig== X-Received: by 2002:adf:e0c3:0:b0:20c:5672:9577 with SMTP id m3-20020adfe0c3000000b0020c56729577mr26101094wri.466.1653475575536; Wed, 25 May 2022 03:46:15 -0700 (PDT) Received: from ?IPV6:2a0b:e7c0:0:107::70f? ([2a0b:e7c0:0:107::70f]) by smtp.gmail.com with ESMTPSA id u19-20020a05600c19d300b003975c7058bfsm1895136wmq.12.2022.05.25.03.46.14 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 25 May 2022 03:46:15 -0700 (PDT) Message-ID: Date: Wed, 25 May 2022 12:46:14 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0 Subject: Re: [GIT PULL for v5.18-rc1] media updates Content-Language: en-US To: Sean Young Cc: Mauro Carvalho Chehab , Linus Torvalds , Greg Kroah-Hartman , Andrew Morton , Linux Media Mailing List , Linux Kernel Mailing List References: <20220322101406.459e2950@coco.lan> <8093277c-5098-e5e3-f606-486de5b2f67b@kernel.org> From: Jiri Slaby In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 25. 05. 22, 11:10, Sean Young wrote: > 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 The code would do "if (x & 0)" or alike, so I'm not sure this won't result in a warning. But as soon as that thing compiles, I don't really care much. If it produces no warning, in fact, the code could be optimized away out thanks to "& 0". Just looked up those defs in the debian code search, only lirc and v4l-utils care about the defines. ANd the latter seems to define their own copies. > 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? Great. thanks, -- js suse labs