mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Elder <elder@riscstar.com>
To: Arnd Bergmann <arnd@arndb.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: daniel@riscstar.com, bhelgaas@google.com,
	linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] misc: Kconfig: tc9564: fix a circular dependency
Date: Fri, 2 Oct 2026 09:07:42 -0500	[thread overview]
Message-ID: <ff8ef0da-180c-4ebf-b9b7-0bb029c56cc9@riscstar.com> (raw)
In-Reply-To: <2582b0a0-009f-40f6-9b5f-85d4c8b2fe84@app.fastmail.com>

On 10/2/26 7:55 AM, Arnd Bergmann wrote:
> On Fri, Oct 2, 2026, at 14:50, Alex Elder wrote:
>> On 10/2/26 1:02 AM, Arnd Bergmann wrote:
>>> On Fri, Oct 2, 2026, at 03:33, Alex Elder wrote:
>>> config TC9564_PCI
>>>    	tristate "Toshiba TC9564 PCI function support"
>>>           depends on PCI && PCI_DYNAMIC_OF_NODES && PCI_QUIRKS
>>>
>>> (in either one or three lines)
>>
>> If I do one, I'll combine OF and OF_IRQ similarly into one.
> 
> If you have a dependency on PCI_DYNAMIC_OF_NODES, you don't
> need the extra dependency on OF_IRQ or OF.
> 
> I guess you don't need the dependency on PCI either, unless
> we ever want to make PCI a tristate option have that in
> a loadable module.
> 
>        Arnd

I'm partly influenced by something comparable to "include
what you use", where my instinct here would be to explicitly
indicate dependencies even if other depended-on config
options satisfy them.  But I'll do what you're suggesting.

I will omit the dependency on PCI.  This is the same situation
as the OF dependency, where OF_IRQ is only available if OF is
enabled.

I'm adding "Suggested-by" you in the commit, because the final
(much simpler) form derives directly from what you've said here.

Thank you.

					-Alex

      reply	other threads:[~2026-10-02 14:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02  1:33 Alex Elder
2026-10-02  6:02 ` Arnd Bergmann
2026-10-02 12:50   ` Alex Elder
2026-10-02 12:55     ` Arnd Bergmann
2026-10-02 14:07       ` Alex Elder [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=ff8ef0da-180c-4ebf-b9b7-0bb029c56cc9@riscstar.com \
    --to=elder@riscstar.com \
    --cc=arnd@arndb.de \
    --cc=bhelgaas@google.com \
    --cc=daniel@riscstar.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.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 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®