From: Will Deacon <will@kernel.org>
To: bjorn.andersson@linaro.org, mark.rutland@arm.com,
agross@kernel.org, Tian Tao <tiantao6@hisilicon.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] move to use request_irq by IRQF_NO_AUTOEN flag
Date: Wed, 2 Jun 2021 18:06:24 +0100 [thread overview]
Message-ID: <162263448864.1277252.10521905851426548574.b4-ty@kernel.org> (raw)
In-Reply-To: <1622595642-61678-1-git-send-email-tiantao6@hisilicon.com>
On Wed, 2 Jun 2021 09:00:40 +0800, Tian Tao wrote:
> patch #1 and #2 both use IRQF_NO_AUTOEN instead of
> irq_set_status_flags(irq, IRQ_NOAUTOEN). this change is just to simplify
> the code, no actual functional changes.
>
> Tian Tao (2):
> arm_pmu: move to use request_irq by IRQF_NO_AUTOEN flag
> perf: qcom_l2_pmu: move to use request_irq by IRQF_NO_AUTOEN flag
>
> [...]
Applied to will (for-next/perf), thanks!
[1/2] arm_pmu: move to use request_irq by IRQF_NO_AUTOEN flag
https://git.kernel.org/will/c/3c1f2eb5475a
[2/2] perf: qcom_l2_pmu: move to use request_irq by IRQF_NO_AUTOEN flag
https://git.kernel.org/will/c/0d0f144a8f5f
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-06-02 17:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 1:00 [PATCH 0/2] move to use request_irq by IRQF_NO_AUTOEN flag Tian Tao
2021-06-02 1:00 ` [PATCH 1/2] arm_pmu: " Tian Tao
2021-06-02 10:14 ` Mark Rutland
2021-06-02 1:00 ` [PATCH 2/2] perf: qcom_l2_pmu: " Tian Tao
2021-06-02 10:16 ` Mark Rutland
2021-06-02 17:06 ` Will Deacon [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=162263448864.1277252.10521905851426548574.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=tiantao6@hisilicon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox