From: Thomas Gleixner <tglx@kernel.org>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Subject: Re: [PATCH v2 0/7] Initial steps to constify irq_chip
Date: Tue, 02 Jun 2026 22:36:34 +0200 [thread overview]
Message-ID: <87v7c07k8d.ffs@fw13> (raw)
In-Reply-To: <cover.1780343698.git.christophe.jaillet@wanadoo.fr>
Christophe!
On Mon, Jun 01 2026 at 22:19, Christophe JAILLET wrote:
> This has been 95% build-tested on x86.
> So it is likely that some corner cases will be spotted by build-bots
> on other architectures.
> Sorry about that, but I don't have enough cycles on my personnal
> machine to cross-build the serie on different architecture.
I've applied it to my devel tree, so the robots can chew on it.
git://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git irq/constify
If there is fallout you should get a nice mail from them.
Thanks,
tglx
prev parent reply other threads:[~2026-06-02 20:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 20:19 [PATCH v2 0/7] Initial steps to constify irq_chip Christophe JAILLET
2026-06-01 20:19 ` [PATCH v2 1/7] irqchip: Constify "struct irq_chip *" parameter in chained_irq_xxx() functions Christophe JAILLET
2026-06-01 20:19 ` [PATCH v2 2/7] irqchip: Constify "struct irq_chip *" parameter in cond_xxx_eoi_irq() Christophe JAILLET
2026-06-01 20:19 ` [PATCH v2 3/7] pinctrl: samsung: Constify "struct irq_chip *" parameter in to_exynos_irq_chip() Christophe JAILLET
2026-06-01 20:19 ` [PATCH v2 4/7] irqchip: Constify some struct irq_chip * Christophe JAILLET
2026-06-01 20:19 ` [PATCH v2 5/7] x86/irq: Constify a " Christophe JAILLET
2026-06-01 20:19 ` [PATCH v2 6/7] treewide: Constify some " Christophe JAILLET
2026-06-01 20:19 ` [PATCH v2 7/7] genirq/chip: Constify the 'chip' field in irq_data Christophe JAILLET
2026-06-02 20:36 ` Thomas Gleixner [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=87v7c07k8d.ffs@fw13 \
--to=tglx@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.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 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.