[<prev] [next>] [day] [month] [year] [list]
Message-Id: <160769813659.482133.1535871338934448366.b4-ty@kernel.org>
Date: Fri, 11 Dec 2020 15:01:37 +0000
From: Marc Zyngier <maz@...nel.org>
To: shawnguo@...nel.org, linux@...musvillemoes.dk, leoyang.li@....com,
mark.rutland@....com, zhiqiang.hou@....com,
Biwen Li <biwen.li@....nxp.com>, robh+dt@...nel.org,
tglx@...utronix.de, Lokesh Vutla <lokeshvutla@...com>
Cc: xiaobo.xie@....com, Hou Zhiqiang <Zhiqiang.Hou@....com>,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Biwen Li <biwen.li@....com>, linux-kernel@...r.kernel.org,
jiafei.pan@....com, Sekhar Nori <nsekhar@...com>,
Nishanth Menon <nm@...com>
Subject: Re: [PATCH] irqchip/ti-sci-inta: Fix printing of inta id on probe success
On Mon, 2 Nov 2020 17:36:14 +0530, Lokesh Vutla wrote:
> On a successful probe, the driver tries to print a success message with
> INTA device id. It uses pdev->id for printing the id but id is stored in
> inta->ti_sci_id. Fix it by correcting the dev_info parameter.
Applied to irq/irqchip-next, thanks!
[1/1] irqchip/ti-sci-inta: Fix printing of inta id on probe success
commit: b10d5fd489b0c67f59cbdd28d95f4bd9f76a62f2
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists