mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil+cisco@kernel.org>
To: Sean Young <sean@mess.org>,
	linux-media@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: kernel test robot <lkp@intel.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: rc: Fix build failure with CONFIG_LIRC disabled
Date: Wed, 23 Sep 2026 13:03:00 +0200	[thread overview]
Message-ID: <c55b028e-8d88-4843-b29f-f8dfc35653ba@kernel.org> (raw)
In-Reply-To: <20260923085948.312798-1-sean@mess.org>

On 23/09/2026 10:59, Sean Young wrote:
> commit 37efd09ba2c6 ("media: rc: Ensure registered is cleared in error
> path") broke the build if CONFIG_LIRC was not enabled.
> 
> Fixes: 37efd09ba2c6 ("media: rc: Ensure registered is cleared in error path")
> Reported-by: kernel test robot <lkp@intel.com>
> Link: https://lore.kernel.org/oe-kbuild-all/202609230511.Em5Osw74-lkp@intel.com
> Signed-off-by: Sean Young <sean@mess.org>

Reviewed-by: Hans Verkuil <hverkuil+cisco@kernel.org>

Regards,

	Hans

> ---
>  drivers/media/rc/lirc_dev.c | 3 +++
>  drivers/media/rc/rc-main.c  | 3 +--
>  2 files changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/media/rc/lirc_dev.c b/drivers/media/rc/lirc_dev.c
> index d9b6ecca563f..f7b8f1f66d9b 100644
> --- a/drivers/media/rc/lirc_dev.c
> +++ b/drivers/media/rc/lirc_dev.c
> @@ -777,6 +777,9 @@ void lirc_unregister(struct rc_dev *dev)
>  	unsigned long flags;
>  	struct lirc_fh *fh;
>  
> +	if (!device_is_registered(&dev->lirc_dev))
> +		return;
> +
>  	dev_dbg(&dev->dev, "lirc_dev: driver %s unregistered from minor = %d\n",
>  		dev->driver_name, MINOR(dev->lirc_dev.devt));
>  
> diff --git a/drivers/media/rc/rc-main.c b/drivers/media/rc/rc-main.c
> index 1c07bdd3b42b..a867bf9e8416 100644
> --- a/drivers/media/rc/rc-main.c
> +++ b/drivers/media/rc/rc-main.c
> @@ -2018,8 +2018,7 @@ int rc_register_device(struct rc_dev *dev)
>  	scoped_guard(mutex, &dev->lock)
>  		dev->registered = false;
>  
> -	if (device_is_registered(&dev->lirc_dev))
> -		lirc_unregister(dev);
> +	lirc_unregister(dev);
>  	device_del(&dev->dev);
>  	/* registered already cleared above */
>  	goto out_free_table;


      reply	other threads:[~2026-09-23 11:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-23  8:59 Sean Young
2026-09-23 11:03 ` Hans Verkuil [this message]

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=c55b028e-8d88-4843-b29f-f8dfc35653ba@kernel.org \
    --to=hverkuil+cisco@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mchehab@kernel.org \
    --cc=sean@mess.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®