From: Thomas Gleixner <tglx@linutronix.de>
To: John Garry <john.garry@huawei.com>,
jejb@linux.ibm.com, martin.petersen@oracle.com, lenb@kernel.org,
rjw@rjwysocki.net, gregkh@linuxfoundation.org, maz@kernel.org
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxarm@huawei.com, linux-acpi@vger.kernel.org, dwagner@suse.de
Subject: Re: [PATCH v4 1/5] genirq/affinity: Add irq_update_affinity_desc()
Date: Tue, 01 Dec 2020 18:28:10 +0100 [thread overview]
Message-ID: <87pn3tfnbp.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <22315d74-0696-85ef-882c-85961cfb4f32@huawei.com>
On Tue, Dec 01 2020 at 15:22, John Garry wrote:
> /*
> * There are certain limitations on when it may be used - attempts to
> use it for when the kernel is configured for generic IRQ reservation
> mode (in config GENERIC_IRQ_RESERVATION_MODE) will fail, as it may
> conflict with managed/non-managed interrupt accounting. In addition,
> attempts to use it on an interrupt which is already started or which has
> already been configured as managed will also fail, as these mean invalid
> init state or double init.
>
> ...
>
> Let me know if not good, if not I'll post again soon.
LGTM
next prev parent reply other threads:[~2020-12-01 17:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 17:35 [PATCH v4 0/5] Support managed interrupts for platform devices John Garry
2020-11-30 17:35 ` [PATCH v4 1/5] genirq/affinity: Add irq_update_affinity_desc() John Garry
2020-11-30 23:19 ` Thomas Gleixner
2020-12-01 15:22 ` John Garry
2020-12-01 17:28 ` Thomas Gleixner [this message]
2020-11-30 17:35 ` [PATCH v4 2/5] resource: Add irqresource_disabled() John Garry
2020-12-01 19:02 ` Rafael J. Wysocki
2020-11-30 17:35 ` [PATCH v4 3/5] ACPI: Drop acpi_dev_irqresource_disabled() John Garry
2020-12-01 19:01 ` Rafael J. Wysocki
2020-11-30 17:35 ` [PATCH v4 4/5] Driver core: platform: Add devm_platform_get_irqs_affinity() John Garry
2020-11-30 17:35 ` [PATCH v4 5/5] scsi: hisi_sas: Expose HW queues for v2 hw John Garry
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=87pn3tfnbp.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=dwagner@suse.de \
--cc=gregkh@linuxfoundation.org \
--cc=jejb@linux.ibm.com \
--cc=john.garry@huawei.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=martin.petersen@oracle.com \
--cc=maz@kernel.org \
--cc=rjw@rjwysocki.net \
/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;
as well as URLs for NNTP newsgroup(s).