All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lorenzo Pieralisi <lpieralisi@kernel.org>
To: Marc Zyngier <maz@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Sascha Bischoff <sascha.bischoff@arm.com>,
	Timothy Hayes <timothy.hayes@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH 0/3] irqchip/gic-v5: Minor clean-ups/fixes
Date: Tue, 5 Aug 2025 11:30:11 +0200	[thread overview]
Message-ID: <aJHPI8xRtleEx+3r@lpieralisi> (raw)
In-Reply-To: <20250801-gic-v5-fixes-6-17-v1-0-4fcedaccf9e6@kernel.org>

On Fri, Aug 01, 2025 at 09:58:17AM +0200, Lorenzo Pieralisi wrote:
> A trivial fix for a kbot reported issue and two clean-ups
> discovered after the initial series was queued for v6.17;
> now that the driver code is merged I am sharing them.
> 
> Only patch (1) is a fix, the two others are cleaning the code up
> and removing useless constructs.
> 
> The series apply cleanly on top of this three-patch series [1] fixing
> some exit path issues with the gic-v5 driver that should also
> be considered for merging please (I reviewed it and tested it [2]):

Hi Thomas, Marc,

thank you for reviewing and pulling these fixes, please also consider
fixes in [1] below that are still current, Dan sent them before the
series was queued for -next and I reviewed/tested them (in particular
patch (3) - others are obvious).

Thanks,
Lorenzo

> 
> [1] https://lore.kernel.org/lkml/670bb1dc-7827-4916-84f3-bb46ee408b20@sabinyo.mountain/
> [2] https://lore.kernel.org/lkml/aHoU8sKPuyzEFRIn@lpieralisi/
> 
> Signed-off-by: Lorenzo Pieralisi <lpieralisi@kernel.org>
> ---
> Lorenzo Pieralisi (3):
>       irqchip/gic-v5: iwb: Fix iounmap probe failure path
>       irqchip/gic-v5: iwb: Remove module boilerplate
>       irqchip/gic-v5: Remove IRQD_RESEND_WHEN_IN_PROGRESS for ITS IRQs
> 
>  drivers/irqchip/irq-gic-v5-its.c |  1 -
>  drivers/irqchip/irq-gic-v5-iwb.c | 14 +++-----------
>  2 files changed, 3 insertions(+), 12 deletions(-)
> ---
> base-commit: 260f6f4fda93c8485c8037865c941b42b9cba5d2
> change-id: 20250731-gic-v5-fixes-6-17-949eae3c5594
> 
> Best regards,
> -- 
> Lorenzo Pieralisi <lpieralisi@kernel.org>
> 


      parent reply	other threads:[~2025-08-05  9:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-01  7:58 [PATCH 0/3] irqchip/gic-v5: Minor clean-ups/fixes Lorenzo Pieralisi
2025-08-01  7:58 ` [PATCH 1/3] irqchip/gic-v5: iwb: Fix iounmap probe failure path Lorenzo Pieralisi
2025-08-01 12:26   ` Marc Zyngier
2025-08-05  8:48   ` [tip: irq/urgent] " tip-bot2 for Lorenzo Pieralisi
2025-08-01  7:58 ` [PATCH 2/3] irqchip/gic-v5: iwb: Remove module boilerplate Lorenzo Pieralisi
2025-08-01 12:24   ` Marc Zyngier
2025-08-01 14:04     ` Lorenzo Pieralisi
2025-08-01  7:58 ` [PATCH 3/3] irqchip/gic-v5: Remove IRQD_RESEND_WHEN_IN_PROGRESS for ITS IRQs Lorenzo Pieralisi
2025-08-01 12:30   ` Marc Zyngier
2025-08-01 14:01     ` Lorenzo Pieralisi
2025-08-05  8:48   ` [tip: irq/urgent] " tip-bot2 for Lorenzo Pieralisi
2025-08-05  9:30 ` Lorenzo Pieralisi [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=aJHPI8xRtleEx+3r@lpieralisi \
    --to=lpieralisi@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=maz@kernel.org \
    --cc=sascha.bischoff@arm.com \
    --cc=tglx@linutronix.de \
    --cc=timothy.hayes@arm.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 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.