public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
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 4/5] irqchip: Constify some irq_desc_get_chip() usage
Date: Tue, 03 Dec 2024 12:32:00 +0100	[thread overview]
Message-ID: <87plm9t32n.ffs@tglx> (raw)
In-Reply-To: <a683ada6749705812e9cfc4c36ce36386362d814.1731835733.git.christophe.jaillet@wanadoo.fr>

On Sun, Nov 17 2024 at 10:49, Christophe JAILLET wrote:
> When irq_desc_get_chip() will return a const struct irq_chip, the const
> qualifier will be needed for local variables that store the return value of
> this function.
>
> So start to add some of these const qualifiers.

Can you please create a coccinelle script which does a tree wide
conversion of all irq_desc_get_chip() and irq_data_get_irq_chip()
instances?

That script can be run at the end of the next merge window once instead
of having to chase 240+ places with individual patches.

Thanks,

        tglx

  reply	other threads:[~2024-12-03 11:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-17  9:49 [PATCH 0/5] Initial steps to constify irq_chip Christophe JAILLET
2024-11-17  9:49 ` [PATCH 1/5] irqchip: Constify "struct irq_chip *" parameter in chained_irq_xxx() functions Christophe JAILLET
2024-11-17  9:49 ` [PATCH 2/5] irqchip: Constify "struct irq_chip *" parameter in cond_unmask_eoi_irq() Christophe JAILLET
2024-11-17  9:49 ` [PATCH 3/5] irqchip: Constify some direct access to irq_data->chip Christophe JAILLET
2024-11-17  9:49 ` [PATCH 4/5] irqchip: Constify some irq_desc_get_chip() usage Christophe JAILLET
2024-12-03 11:32   ` Thomas Gleixner [this message]
2024-11-17  9:49 ` [PATCH 5/5] irqchip: Constify some irq_data_get_irq_chip() usage Christophe JAILLET

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=87plm9t32n.ffs@tglx \
    --to=tglx@linutronix.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox