All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Arnd Bergmann" <arnd@arndb.de>
Cc: "Takashi Iwai" <tiwai@suse.de>, "Arnd Bergmann" <arnd@kernel.org>,
	"Jaroslav Kysela" <perex@perex.cz>,
	"Takashi Iwai" <tiwai@suse.com>,
	"Kailang Yang" <kailang@realtek.com>,
	"Simon Trimmer" <simont@opensource.cirrus.com>,
	"Joshua Grisham" <josh@joshuagrisham.com>,
	linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] snd: hda: realtek: fix incorrect IS_REACHABLE() usage
Date: Tue, 04 Mar 2025 17:03:55 +0100	[thread overview]
Message-ID: <87ikooail0.wl-tiwai@suse.de> (raw)
In-Reply-To: <94b39ea3-bc29-49f0-bd34-eec45d61ff1b@app.fastmail.com>

On Tue, 04 Mar 2025 15:54:33 +0100,
Arnd Bergmann wrote:
> 
> On Tue, Mar 4, 2025, at 15:43, Takashi Iwai wrote:
> > On Tue, 04 Mar 2025 15:25:55 +0100,
> >
> > Thanks for the patch.  Indeed it's a very corner case, but I still
> > hesitate to add a kconfig dependency.  Can we take an alternative fix
> > to define the proper dummy functions like below instead?
> 
> I'm sure that works, and I had considered something like that,
> but I really dislike the IS_REACHABLE() use because I think it
> causes more problems than it solves. (I introduced the macro
> originally but regret that).
> 
> Note that the only way to disable input is to have manually flip
> CONFIG_EXPERT and CONFIG_TTY as well as the major GPU drivers
> that select it:
> 
> config INPUT
>         tristate "Generic input layer (needed for keyboard, mouse, ...)" if EXPERT
>         default y
> 
> so in the end, there is very little difference between
> your patch and mine, as they both fix build testing on
> randconfig.

OK, I don't mind much, so I take your patch now, as this actually
reduces the code size.


thanks,

Takashi

      reply	other threads:[~2025-03-04 16:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-04 14:25 [PATCH] snd: hda: realtek: fix incorrect IS_REACHABLE() usage Arnd Bergmann
2025-03-04 14:43 ` Takashi Iwai
2025-03-04 14:54   ` Arnd Bergmann
2025-03-04 16:03     ` Takashi Iwai [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=87ikooail0.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=josh@joshuagrisham.com \
    --cc=kailang@realtek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=simont@opensource.cirrus.com \
    --cc=tiwai@suse.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.