From: Radu Rendec <radu@rendec.net>
To: Eliav Farber <farbere@amazon.com>,
Thomas Gleixner <tglx@kernel.org>,
Talel Shenhar <talel@amazon.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/8] irqchip/al-fic: fix argument alignment and a repeated word
Date: Sun, 04 Oct 2026 12:15:26 -0400 [thread overview]
Message-ID: <fe5ee287339e8aa99b1e6ec7d9929ffc8c37aad7.camel@rendec.net> (raw)
In-Reply-To: <20260927080637.27285-2-farbere@amazon.com>
On Sun, 2026-09-27 at 08:06 +0000, Eliav Farber wrote:
> The continuation lines of the irq_domain_create_linear() call sit three
> columns short of the open parenthesis. They were aligned for
> irq_domain_add_linear(); commit affdc0d1bdfa ("irqchip: Switch to
> irq_domain_create_*()") renamed the function to one three characters longer
> and left the indentation as it was. checkpatch --strict reports "Alignment
> should match open parenthesis".
>
> al_fic_wire_init()'s kernel-doc reads "the fic hardware to to work in wire
> mode". checkpatch reports "Possible repeated word: 'to'".
>
> No functional change.
>
> Signed-off-by: Eliav Farber <farbere@amazon.com>
> ---
> v2: new patch. checkpatch --strict cleanups (argument alignment and a
> repeated word) split out ahead of the functional changes; the touched
> lines also appear as context in patches 3 and 6.
>
> drivers/irqchip/irq-al-fic.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/irqchip/irq-al-fic.c b/drivers/irqchip/irq-al-fic.c
> index d10ac9b63c99..35581332b40e 100644
> --- a/drivers/irqchip/irq-al-fic.c
> +++ b/drivers/irqchip/irq-al-fic.c
> @@ -132,9 +132,9 @@ static int al_fic_register(struct device_node *node,
> int ret;
>
> fic->domain = irq_domain_create_linear(of_fwnode_handle(node),
> - NR_FIC_IRQS,
> - &irq_generic_chip_ops,
> - fic);
> + NR_FIC_IRQS,
> + &irq_generic_chip_ops,
> + fic);
> if (!fic->domain) {
> pr_err("fail to add irq domain\n");
> return -ENOMEM;
> @@ -180,7 +180,7 @@ static int al_fic_register(struct device_node *node,
> * @name: name of the fic
> * @parent_irq: interrupt of parent
> *
> - * This API will configure the fic hardware to to work in wire mode.
> + * This API will configure the fic hardware to work in wire mode.
> * In wire mode, fic hardware is generating a wire ("wired") interrupt.
> * Interrupt can be generated based on positive edge or level - configuration is
> * to be determined based on connected hardware to this fic.
Reviewed-by: Radu Rendec <radu@rendec.net>
next prev parent reply other threads:[~2026-10-04 16:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-27 8:06 [PATCH v2 0/8] irqchip/al-fic: shared parent IRQ, error/fatal outputs and affinity Eliav Farber
2026-09-27 8:06 ` [PATCH v2 1/8] irqchip/al-fic: fix argument alignment and a repeated word Eliav Farber
2026-10-04 16:15 ` Radu Rendec [this message]
2026-09-27 8:06 ` [PATCH v2 2/8] irqchip/al-fic: use %pOF and raise init log level Eliav Farber
2026-10-04 16:25 ` Radu Rendec
2026-09-27 8:06 ` [PATCH v2 3/8] irqchip/al-fic: keep the device_node instead of a cached name string Eliav Farber
2026-10-04 17:40 ` Radu Rendec
2026-10-05 11:17 ` Farber, Eliav
2026-09-27 8:06 ` [PATCH v2 4/8] irqchip/al-fic: switch to shared parent interrupt Eliav Farber
2026-10-04 19:30 ` Radu Rendec
2026-10-05 11:18 ` Farber, Eliav
2026-09-27 8:06 ` [PATCH v2 5/8] dt-bindings: interrupt-controller: amazon,al-fic: add mask selection Eliav Farber
2026-09-28 16:50 ` Conor Dooley
2026-10-04 21:06 ` Radu Rendec
2026-09-27 8:06 ` [PATCH v2 6/8] irqchip/al-fic: support error and fatal outputs and FIC v2 Eliav Farber
2026-10-05 1:01 ` Radu Rendec
2026-10-05 11:19 ` Farber, Eliav
2026-09-27 8:06 ` [PATCH v2 7/8] irqchip/al-fic: add support for FIC v3 Eliav Farber
2026-10-05 1:04 ` Radu Rendec
2026-09-27 8:06 ` [PATCH v2 8/8] irqchip/al-fic: add irq_set_affinity callback Eliav Farber
2026-10-05 1:25 ` Radu Rendec
2026-10-05 11:20 ` Farber, Eliav
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=fe5ee287339e8aa99b1e6ec7d9929ffc8c37aad7.camel@rendec.net \
--to=radu@rendec.net \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=farbere@amazon.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=talel@amazon.com \
--cc=tglx@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
all inboxes | Powered by JetHome®