From: Thomas Gleixner <tglx@linutronix.de>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Russell King <linux@armlinux.org.uk>,
linux-kernel@vger.kernel.org,
Bart Van Assche <bvanassche@acm.org>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: [PATCH v2 06/22] x86/acpi: Switch to irq_get_nr_irqs() and irq_set_nr_irqs()
Date: Wed, 09 Oct 2024 11:07:09 +0200 [thread overview]
Message-ID: <87zfndr6f6.ffs@tglx> (raw)
In-Reply-To: <20241008202601.3737326-7-bvanassche@acm.org>
On Tue, Oct 08 2024 at 13:25, Bart Van Assche wrote:
> Use the irq_get_nr_irqs() and irq_set_nr_irqs() functions instead of the
> global variable 'nr_irqs'. This patch prepares for changing 'nr_irqs' from
> an exported global variable into a variable with file scope.
I asked you this before:
git grep 'This patch' Documentation/process/
Please fix this up all over the place.
Thanks,
tglx
next prev parent reply other threads:[~2024-10-09 9:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 20:25 [PATCH v2 00/21] Reduce the scope of 'nr_irqs' Bart Van Assche
2024-10-08 20:25 ` [PATCH v2 01/22] genirq: Introduce irq_get_nr_irqs() and irq_set_nr_irqs() Bart Van Assche
2024-10-08 20:25 ` [PATCH v2 02/22] ARM: Switch to irq_get_nr_irqs() / irq_set_nr_irqs() Bart Van Assche
2024-10-08 20:25 ` [PATCH v2 03/22] LoongArch: Switch to irq_set_nr_irqs() Bart Van Assche
2024-10-08 20:25 ` [PATCH v2 04/22] powerpc/cell: Switch to irq_get_nr_irqs() Bart Van Assche
2024-10-08 20:25 ` [PATCH v2 05/22] s390/irq: " Bart Van Assche
2024-10-08 20:25 ` [PATCH v2 06/22] x86/acpi: Switch to irq_get_nr_irqs() and irq_set_nr_irqs() Bart Van Assche
2024-10-09 9:07 ` Thomas Gleixner [this message]
2024-10-08 20:25 ` [PATCH v2 07/22] hpet: Switch to irq_get_nr_irqs() Bart Van Assche
2024-10-08 20:25 ` [PATCH v2 08/22] net: 3com: 3c59x: " Bart Van Assche
2024-10-08 20:25 ` [PATCH v2 09/22] net: hamradio: baycom_ser_fdx: " Bart Van Assche
2024-10-08 20:25 ` [PATCH v2 10/22] net: hamradio: scc: " Bart Van Assche
2024-10-08 20:25 ` [PATCH v2 11/22] scsi: aha152x: " Bart Van Assche
2024-10-08 20:25 ` [PATCH v2 12/22] serial: core: " Bart Van Assche
2024-10-08 20:25 ` [PATCH v2 13/22] serial: 8250: " Bart Van Assche
2024-10-08 20:25 ` [PATCH v2 14/22] serial: amba-pl010: " Bart Van Assche
2024-10-08 20:25 ` [PATCH v2 15/22] serial: amba-pl011: " Bart Van Assche
2024-10-08 20:25 ` [PATCH v2 16/22] serial: cpm_uart: " Bart Van Assche
2024-10-08 20:25 ` [PATCH v2 17/22] serial: ucc_uart: " Bart Van Assche
2024-10-08 20:25 ` [PATCH v2 18/22] sh: intc: " Bart Van Assche
2024-10-08 20:25 ` [PATCH v2 19/22] xen/events: " Bart Van Assche
2024-10-08 20:25 ` [PATCH v2 20/22] fs/procfs: " Bart Van Assche
2024-10-08 20:26 ` [PATCH v2 21/22] genirq: " Bart Van Assche
2024-10-08 20:26 ` [PATCH v2 22/22] genirq: Unexport nr_irqs Bart Van Assche
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=87zfndr6f6.ffs@tglx \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=bvanassche@acm.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mingo@redhat.com \
--cc=rafael@kernel.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