All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Norris <briannorris@chromium.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: David Gow <davidgow@google.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Guenter Roeck <linux@roeck-us.net>,
	linux-kernel@vger.kernel.org, kunit-dev@googlegroups.com
Subject: Re: [PATCH 0/6] genirq/test: Platform/architecture fixes
Date: Thu, 21 Aug 2025 08:32:27 -0700	[thread overview]
Message-ID: <aKc8Cz4hgMoJ1v-C@google.com> (raw)
In-Reply-To: <CAMuHMdVichNH4VKGEfDJWB5MTBZMFdh4HXtusb2N_-97RARrbA@mail.gmail.com>

Hi Geert,

On Thu, Aug 21, 2025 at 09:05:03AM +0200, Geert Uytterhoeven wrote:
> So probably the test should depend on SPARSE_IRQ?  Increasing NR_IRQS
> everywhere when IRQ_KUNIT_TEST is enabled sounds rather invasive to me.

Yeah, I was leaning to 'depends on SPARSE_IRQ'

> BTW, given the test calls irq_domain_alloc_descs(), I think it should
> also depend on IRQ_DOMAIN.

Right, that's in patch 1.

I'll resend the series with a 'depends on SPARSE_IRQ'.

Thanks,
Brian

  reply	other threads:[~2025-08-21 15:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18 19:27 [PATCH 0/6] genirq/test: Platform/architecture fixes Brian Norris
2025-08-18 19:27 ` [PATCH 1/6] genirq/test: Select IRQ_DOMAIN Brian Norris
2025-08-18 19:27 ` [PATCH 2/6] genirq/test: Factor out fake-virq setup Brian Norris
2025-08-18 19:27 ` [PATCH 3/6] genirq/test: Fail early if we can't request an IRQ Brian Norris
2025-08-18 19:27 ` [PATCH 4/6] genirq/test: Skip managed-affinity tests with !SPARSE_IRQ Brian Norris
2025-08-18 19:27 ` [PATCH 5/6] genirq/test: Drop CONFIG_GENERIC_IRQ_MIGRATION assumptions Brian Norris
2025-08-18 19:27 ` [PATCH 6/6] genirq/test: Ensure CPU 1 is online for hotplug test Brian Norris
2025-08-20  7:00 ` [PATCH 0/6] genirq/test: Platform/architecture fixes David Gow
2025-08-20 17:22   ` Brian Norris
2025-08-20 21:37     ` Guenter Roeck
2025-08-21  3:45     ` David Gow
2025-08-21  7:05       ` Geert Uytterhoeven
2025-08-21 15:32         ` Brian Norris [this message]
2025-08-21 17:02 ` Guenter Roeck
2025-08-21 19:06   ` Brian Norris
2025-08-22 18:34     ` Guenter Roeck
2025-08-22 19:01       ` Brian Norris

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=aKc8Cz4hgMoJ1v-C@google.com \
    --to=briannorris@chromium.org \
    --cc=davidgow@google.com \
    --cc=geert@linux-m68k.org \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=tglx@linutronix.de \
    /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.