From: Brian Norris <briannorris@chromium.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Richard Weinberger <richard@nod.at>,
Anton Ivanov <anton.ivanov@cambridgegreys.com>,
linux-um@lists.infradead.org, linux-kernel@vger.kernel.org,
David Gow <davidgow@google.com>, Sinan Nalkaya <sardok@gmail.com>
Subject: Re: [PATCH] um: Support SPARSE_IRQ
Date: Wed, 27 Aug 2025 12:41:28 -0700 [thread overview]
Message-ID: <aK9faES_JZYCgyip@google.com> (raw)
In-Reply-To: <155ce30d5fad5a444f72b681eb096418384542b3.camel@sipsolutions.net>
On Wed, Aug 27, 2025 at 09:38:17PM +0200, Johannes Berg wrote:
> On Mon, 2025-08-25 at 14:19 -0700, Brian Norris wrote:
> >
> > +#ifdef CONFIG_SPARSE_IRQ
> > +int __init arch_probe_nr_irqs(void)
> >
>
> Is there much point in the ifdef if it's anyway always going to be
> enabled due to the 'select'?
Oh, good question. No, I don't see much point. I think I was waffling
about the MAY_HAVE_SPARSE_IRQ question, but if we go with 'select
SPARSE_IRQ' as proposed, I should probably drop the #ifdef.
Will send v2 if that's the only question/request.
Brian
prev parent reply other threads:[~2025-08-27 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 21:19 [PATCH] um: Support SPARSE_IRQ Brian Norris
2025-08-26 1:38 ` David Gow
2025-08-27 19:38 ` Johannes Berg
2025-08-27 19:41 ` Brian Norris [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=aK9faES_JZYCgyip@google.com \
--to=briannorris@chromium.org \
--cc=anton.ivanov@cambridgegreys.com \
--cc=davidgow@google.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=richard@nod.at \
--cc=sardok@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).