From: Florian Fainelli <f.fainelli@gmail.com> To: linux-kernel@vger.kernel.org, Marc Zyngier <maz@kernel.org> Cc: Broadcom internal kernel review list <bcm-kernel-feedback-list@broadcom.com>, Thomas Gleixner <tglx@linutronix.de>, Rob Herring <robh@kernel.org>, Doug Berger <opendmb@gmail.com>, Jason Cooper <jason@lakedaemon.net>, "open list:BROADCOM BMIPS MIPS ARCHITECTURE" <linux-mips@vger.kernel.org>, "moderated list:BROADCOM BCM7XXX ARM ARCHITECTURE" <linux-arm-kernel@lists.infradead.org> Subject: Re: [PATCH 0/2] Couple of Broadcom L2 driver fixes Date: Wed, 25 Jan 2023 16:10:04 -0800 [thread overview] Message-ID: <dfe3b3db-88e5-4d18-e8d1-7d1dfe752a9d@gmail.com> (raw) In-Reply-To: <20221216230934.2478345-1-f.fainelli@gmail.com> On 12/16/2022 3:09 PM, Florian Fainelli wrote: > This small patch series ensures that IRQ_LEVEL is set for level > triggered interupts in both the irq-bcm7120-l2 and the irq-brcmstb-l2 > driver. > > Thanks Ping? > > Florian Fainelli (2): > irqchip/irq-brcmstb-l2: Set IRQ_LEVEL for level triggered interrupts > irqchip/irq-bcm7120-l2: Set IRQ_LEVEL for level triggered interrupts > > drivers/irqchip/irq-bcm7120-l2.c | 3 ++- > drivers/irqchip/irq-brcmstb-l2.c | 6 +++++- > 2 files changed, 7 insertions(+), 2 deletions(-) > -- Florian
WARNING: multiple messages have this Message-ID (diff)
From: Florian Fainelli <f.fainelli@gmail.com> To: linux-kernel@vger.kernel.org, Marc Zyngier <maz@kernel.org> Cc: Broadcom internal kernel review list <bcm-kernel-feedback-list@broadcom.com>, Thomas Gleixner <tglx@linutronix.de>, Rob Herring <robh@kernel.org>, Doug Berger <opendmb@gmail.com>, Jason Cooper <jason@lakedaemon.net>, "open list:BROADCOM BMIPS MIPS ARCHITECTURE" <linux-mips@vger.kernel.org>, "moderated list:BROADCOM BCM7XXX ARM ARCHITECTURE" <linux-arm-kernel@lists.infradead.org> Subject: Re: [PATCH 0/2] Couple of Broadcom L2 driver fixes Date: Wed, 25 Jan 2023 16:10:04 -0800 [thread overview] Message-ID: <dfe3b3db-88e5-4d18-e8d1-7d1dfe752a9d@gmail.com> (raw) In-Reply-To: <20221216230934.2478345-1-f.fainelli@gmail.com> On 12/16/2022 3:09 PM, Florian Fainelli wrote: > This small patch series ensures that IRQ_LEVEL is set for level > triggered interupts in both the irq-bcm7120-l2 and the irq-brcmstb-l2 > driver. > > Thanks Ping? > > Florian Fainelli (2): > irqchip/irq-brcmstb-l2: Set IRQ_LEVEL for level triggered interrupts > irqchip/irq-bcm7120-l2: Set IRQ_LEVEL for level triggered interrupts > > drivers/irqchip/irq-bcm7120-l2.c | 3 ++- > drivers/irqchip/irq-brcmstb-l2.c | 6 +++++- > 2 files changed, 7 insertions(+), 2 deletions(-) > -- Florian _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-01-26 0:10 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-16 23:09 [PATCH 0/2] Couple of Broadcom L2 driver fixes Florian Fainelli 2022-12-16 23:09 ` Florian Fainelli 2022-12-16 23:09 ` [PATCH 1/2] irqchip/irq-brcmstb-l2: Set IRQ_LEVEL for level triggered interrupts Florian Fainelli 2022-12-16 23:09 ` Florian Fainelli 2023-02-18 14:28 ` [irqchip: irq/irqchip-next] " irqchip-bot for Florian Fainelli 2022-12-16 23:09 ` [PATCH 2/2] irqchip/irq-bcm7120-l2: " Florian Fainelli 2022-12-16 23:09 ` Florian Fainelli 2023-02-18 14:28 ` [irqchip: irq/irqchip-next] " irqchip-bot for Florian Fainelli 2022-12-17 18:25 ` [PATCH 0/2] Couple of Broadcom L2 driver fixes Philippe Mathieu-Daudé 2022-12-17 18:25 ` Philippe Mathieu-Daudé 2023-01-26 0:10 ` Florian Fainelli [this message] 2023-01-26 0:10 ` Florian Fainelli 2023-02-14 23:23 ` Florian Fainelli 2023-02-14 23:23 ` Florian Fainelli
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=dfe3b3db-88e5-4d18-e8d1-7d1dfe752a9d@gmail.com \ --to=f.fainelli@gmail.com \ --cc=bcm-kernel-feedback-list@broadcom.com \ --cc=jason@lakedaemon.net \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mips@vger.kernel.org \ --cc=maz@kernel.org \ --cc=opendmb@gmail.com \ --cc=robh@kernel.org \ --cc=tglx@linutronix.de \ /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: linkBe 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.