From: John Garry <john.garry@huawei.com>
To: Greg KH <gregkh@linuxfoundation.org>,
Marc Zyngier <maz@kernel.org>, <tglx@linutronix.de>
Cc: <jejb@linux.ibm.com>, <martin.petersen@oracle.com>,
<lenb@kernel.org>, <rjw@rjwysocki.net>,
<linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linuxarm@huawei.com>, <linux-acpi@vger.kernel.org>,
<dwagner@suse.de>
Subject: Re: [PATCH v5 4/5] Driver core: platform: Add devm_platform_get_irqs_affinity()
Date: Thu, 10 Dec 2020 16:37:13 +0000 [thread overview]
Message-ID: <2cce8111-37b9-e29b-6f9a-4866891f7a7c@huawei.com> (raw)
In-Reply-To: <X9I+2ydy8VDOaiec@kroah.com>
Hi Greg,
> {sigh} why do hardware engineers ignore sane busses...
The next HW version is an integrated PCI endpoint, so there is hope.
>
> Anyway, if you all are going to maintain this, no objection from me, it
> should go through the irq tree.
OK, thanks. So this is getting quite late for 5.11, and none of it has
seen -next obviously. However, the changes are additive and should only
affect a single driver now. I'm talking about this series now, not
Marc's companion series.
I just need to hear from Thomas on any merge preference.
Thanks,
John
next prev parent reply other threads:[~2020-12-10 16:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 10:36 [PATCH v5 0/5] Support managed interrupts for platform devices John Garry
2020-12-02 10:36 ` [PATCH v5 1/5] genirq/affinity: Add irq_update_affinity_desc() John Garry
2020-12-02 10:36 ` [PATCH v5 2/5] resource: Add irqresource_disabled() John Garry
2020-12-02 10:36 ` [PATCH v5 3/5] ACPI: Drop acpi_dev_irqresource_disabled() John Garry
2020-12-02 10:36 ` [PATCH v5 4/5] Driver core: platform: Add devm_platform_get_irqs_affinity() John Garry
2020-12-09 18:32 ` Greg KH
2020-12-09 19:04 ` John Garry
2020-12-09 19:13 ` Greg KH
2020-12-09 19:36 ` John Garry
2020-12-09 19:39 ` Marc Zyngier
2020-12-10 10:10 ` John Garry
2020-12-10 15:29 ` Greg KH
2020-12-10 16:37 ` John Garry [this message]
2020-12-02 10:36 ` [PATCH v5 5/5] scsi: hisi_sas: Expose HW queues for v2 hw John Garry
2020-12-11 16:56 ` John Garry
2020-12-11 17:20 ` Martin K. Petersen
2020-12-11 17:33 ` John Garry
2020-12-11 15:01 ` [PATCH v5 0/5] Support managed interrupts for platform devices Marc Zyngier
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=2cce8111-37b9-e29b-6f9a-4866891f7a7c@huawei.com \
--to=john.garry@huawei.com \
--cc=dwagner@suse.de \
--cc=gregkh@linuxfoundation.org \
--cc=jejb@linux.ibm.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 \
--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: 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).