From: "Marek Behún" <kabel@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "Gregory Clement" <gregory.clement@bootlin.com>,
"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Pali Rohár" <pali@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 00/10] ARM: dts: mvebu: Add definitions for PCIe legacy INTx interrupts
Date: Wed, 13 Jul 2022 00:23:37 +0200 [thread overview]
Message-ID: <20220713002337.26bffcd9@thinkpad> (raw)
In-Reply-To: <Ys2oaL7U7Ue5syU4@lunn.ch>
On Tue, 12 Jul 2022 18:59:20 +0200
Andrew Lunn <andrew@lunn.ch> wrote:
> On Tue, Jul 12, 2022 at 06:40:58PM +0200, Marek Behún wrote:
> > As suggested by Gregory [1] (although he suggested it only for armada
> > 380), add definitions for PCIe legacy INTx interrupts into every DTS
> > file used by the pci-mvebu.c controller driver.
> >
> > It was tested on 88F6820 (A385) and 88F6281 (Kirkwood) SoCs.
> >
> > [1] https://lore.kernel.org/linux-arm-kernel/87wnhxjxlq.fsf@BL-laptop/
> >
> > Changes since v1:
> > - dropped armada-385 patch, which was already applied
> > - added commit messages
>
> Thanks for updating the commit message.
>
> I don't see any Fixes: tags here. So from that, can i assume that
> there are no known broken devices? We don't need to involve stable.
I don't think so. If it turns out we do, we can just send it to stable
afterwards.
Marek
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: "Marek Behún" <kabel@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "Gregory Clement" <gregory.clement@bootlin.com>,
"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Pali Rohár" <pali@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 00/10] ARM: dts: mvebu: Add definitions for PCIe legacy INTx interrupts
Date: Wed, 13 Jul 2022 00:23:37 +0200 [thread overview]
Message-ID: <20220713002337.26bffcd9@thinkpad> (raw)
In-Reply-To: <Ys2oaL7U7Ue5syU4@lunn.ch>
On Tue, 12 Jul 2022 18:59:20 +0200
Andrew Lunn <andrew@lunn.ch> wrote:
> On Tue, Jul 12, 2022 at 06:40:58PM +0200, Marek Behún wrote:
> > As suggested by Gregory [1] (although he suggested it only for armada
> > 380), add definitions for PCIe legacy INTx interrupts into every DTS
> > file used by the pci-mvebu.c controller driver.
> >
> > It was tested on 88F6820 (A385) and 88F6281 (Kirkwood) SoCs.
> >
> > [1] https://lore.kernel.org/linux-arm-kernel/87wnhxjxlq.fsf@BL-laptop/
> >
> > Changes since v1:
> > - dropped armada-385 patch, which was already applied
> > - added commit messages
>
> Thanks for updating the commit message.
>
> I don't see any Fixes: tags here. So from that, can i assume that
> there are no known broken devices? We don't need to involve stable.
I don't think so. If it turns out we do, we can just send it to stable
afterwards.
Marek
next prev parent reply other threads:[~2022-07-12 22:25 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 16:40 [PATCH v2 00/10] ARM: dts: mvebu: Add definitions for PCIe legacy INTx interrupts Marek Behún
2022-07-12 16:40 ` Marek Behún
2022-07-12 16:40 ` [PATCH v2 01/10] ARM: dts: kirkwood: " Marek Behún
2022-07-12 16:40 ` Marek Behún
2022-07-12 16:41 ` [PATCH v2 02/10] ARM: dts: dove: " Marek Behún
2022-07-12 16:41 ` Marek Behún
2022-07-12 16:41 ` [PATCH v2 03/10] ARM: dts: armada-370.dtsi: " Marek Behún
2022-07-12 16:41 ` Marek Behún
2022-07-12 16:41 ` [PATCH v2 04/10] ARM: dts: armada-xp-98dx3236.dtsi: " Marek Behún
2022-07-12 16:41 ` Marek Behún
2022-07-12 16:41 ` [PATCH v2 05/10] ARM: dts: armada-xp-mv78230.dtsi: " Marek Behún
2022-07-12 16:41 ` Marek Behún
2022-07-12 16:41 ` [PATCH v2 06/10] ARM: dts: armada-xp-mv78260.dtsi: " Marek Behún
2022-07-12 16:41 ` Marek Behún
2022-07-12 16:41 ` [PATCH v2 07/10] ARM: dts: armada-xp-mv78460.dtsi: " Marek Behún
2022-07-12 16:41 ` Marek Behún
2022-07-12 16:41 ` [PATCH v2 08/10] ARM: dts: armada-375.dtsi: " Marek Behún
2022-07-12 16:41 ` Marek Behún
2022-07-12 16:41 ` [PATCH v2 09/10] ARM: dts: armada-380.dtsi: " Marek Behún
2022-07-12 16:41 ` Marek Behún
2022-07-12 16:41 ` [PATCH v2 10/10] ARM: dts: armada-39x.dtsi: " Marek Behún
2022-07-12 16:41 ` Marek Behún
2022-07-12 16:59 ` [PATCH v2 00/10] ARM: dts: mvebu: " Andrew Lunn
2022-07-12 16:59 ` Andrew Lunn
2022-07-12 22:23 ` Marek Behún [this message]
2022-07-12 22:23 ` Marek Behún
2022-08-17 16:50 ` Pali Rohár
2022-08-17 16:50 ` Pali Rohár
2022-09-02 14:51 ` Gregory CLEMENT
2022-09-02 14:51 ` Gregory CLEMENT
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=20220713002337.26bffcd9@thinkpad \
--to=kabel@kernel.org \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pali@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.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.