From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: "tip-bot2 for Thomas Gleixner" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: John Keeping <john@metanate.com>
Cc: stable@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [tip: irq/urgent] genirq/affinity: Make affinity setting if activated opt-in
Date: Thu, 30 Jul 2020 13:48:12 +0000 [thread overview]
Message-ID: <20200730134813.0D02C21D95@mail.kernel.org> (raw)
In-Reply-To: <159585991142.4006.928637752238313572.tip-bot2@tip-bot2>
Hi
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: baedb87d1b53 ("genirq/affinity: Handle affinity setting on inactive interrupts correctly").
The bot has tested the following trees: v5.7.11, v5.4.54, v4.19.135.
v5.7.11: Build OK!
v5.4.54: Failed to apply! Possible dependencies:
008f1d60fe25 ("x86/apic/vector: Force interupt handler invocation to irq context")
c16816acd086 ("genirq: Add protection against unsafe usage of generic_handle_irq()")
v4.19.135: Failed to apply! Possible dependencies:
008f1d60fe25 ("x86/apic/vector: Force interupt handler invocation to irq context")
35ae7df21be0 ("irqchip/gic-v3-its: Don't map the MSI page in its_irq_compose_msi_msg()")
c16816acd086 ("genirq: Add protection against unsafe usage of generic_handle_irq()")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
next prev parent reply other threads:[~2020-07-30 13:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 13:14 [PATCH] genirq/affinity: Handle affinity setting on inactive interrupts correctly Thomas Gleixner
2020-07-17 13:14 ` Thomas Gleixner
2020-07-17 15:25 ` kernel test robot
2020-07-17 15:25 ` kernel test robot
2020-07-17 15:25 ` kernel test robot
2020-07-17 16:00 ` [PATCH V2] " Thomas Gleixner
2020-07-17 16:00 ` Thomas Gleixner
2020-07-24 17:24 ` John Keeping
2020-07-24 17:24 ` John Keeping
2020-07-24 20:03 ` Thomas Gleixner
2020-07-24 20:03 ` Thomas Gleixner
2020-07-24 20:44 ` Thomas Gleixner
2020-07-24 20:44 ` Thomas Gleixner
2020-07-25 12:30 ` Marc Zyngier
2020-07-25 12:30 ` Marc Zyngier
2020-07-27 14:25 ` [tip: irq/urgent] genirq/debugfs: Add missing irqchip flags tip-bot2 for Marc Zyngier
2020-07-27 14:25 ` [tip: irq/urgent] genirq/affinity: Make affinity setting if activated opt-in tip-bot2 for Thomas Gleixner
2020-07-30 13:48 ` Sasha Levin [this message]
2020-07-25 12:08 ` [PATCH V2] genirq/affinity: Handle affinity setting on inactive interrupts correctly Marc Zyngier
2020-07-25 12:08 ` Marc Zyngier
2020-07-27 13:35 ` Thomas Gleixner
2020-07-27 13:35 ` Thomas Gleixner
2020-07-17 18:04 ` [PATCH] " kernel test robot
2020-07-17 18:04 ` kernel test robot
2020-07-17 18:04 ` kernel test robot
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=20200730134813.0D02C21D95@mail.kernel.org \
--to=sashal@kernel.org \
--cc=john@metanate.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.