Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Thu, 7 Jul 2022 18:50:00 +0200
From:   Andrew Lunn <andrew@lunn.ch>
To:     Marek =?iso-8859-1?Q?Beh=FAn?= <kabel@kernel.org>
Cc:     Pali =?iso-8859-1?Q?Roh=E1r?= <pali@kernel.org>,
        Gregory Clement <gregory.clement@bootlin.com>,
        Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
        Rob Herring <robh+dt@kernel.org>,
        linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/11] ARM: dts: mvebu: Add definitions for PCIe legacy
 INTx interrupts
Message-ID: <YscOuEUws9E9nnmm@lunn.ch>
References: <20220706183114.30783-1-pali@kernel.org>
 <YsX2Wvtz7hEpJ6X+@lunn.ch>
 <20220707163818.620ccb95@dellmb>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20220707163818.620ccb95@dellmb>
Precedence: bulk

On Thu, Jul 07, 2022 at 04:38:18PM +0200, Marek Beh?n wrote:
> On Wed, 6 Jul 2022 22:53:46 +0200
> Andrew Lunn <andrew@lunn.ch> wrote:
> 
> > On Wed, Jul 06, 2022 at 08:31:03PM +0200, Pali Roh?r wrote:
> > > This patch series add definitions for PCIe legacy INTx interrupts into
> > > every DTS file used by the pci-mvebu.c controller driver.  
> > 
> > What you fail to explain in the commit message is Why?
> > 
> >      Andrew
> 
> Hi Andrew,
> 
> this is required for example in a scenario where a driver requests only
> one of the legacy interrupts (INTA). Without this change, the driver
> would be notified on events on all 4 (INTA, INTB, INTC, INTD), even if
> it requested only one of them.

O.K, so please add that to the commit message.

Is this purely theoretical, or are there known broken platforms out
there?  Should a subset of these patches be added to stable?

	Andrew