From: Michal Simek <michal.simek@xilinx.com>
To: Palmer Dabbelt <palmer@sifive.com>,
Christoph Hellwig <hch@infradead.org>,
michal.simek@xilinx.com, helgaas@kernel.org
Cc: tony.luck@intel.com, fenghua.yu@intel.com,
heiko.carstens@de.ibm.com, gor@linux.ibm.com,
borntraeger@de.ibm.com, bhelgaas@google.com, will@kernel.org,
Greg KH <gregkh@linuxfoundation.org>,
kstewart@linuxfoundation.org, pbonzini@redhat.com,
firoz.khan@linaro.org, yamada.masahiro@socionext.com,
longman@redhat.com, mingo@kernel.org, peterz@infradead.org,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-s390@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: PCI/MSI: Remove the PCI_MSI_IRQ_DOMAIN architecture whitelist
Date: Fri, 18 Oct 2019 08:20:09 +0200 [thread overview]
Message-ID: <995f625b-1f56-6d97-ba99-9a4298e9dd37@xilinx.com> (raw)
In-Reply-To: <20191017181937.7004-1-palmer@sifive.com>
Hi,
On 17. 10. 19 20:19, Palmer Dabbelt wrote:
> This came up in the context of the microblaze port, where a patch was
> recently posted to extend the whitelist.
I hoped you were aware about this discussion we have with Christoph.
https://lkml.org/lkml/2019/10/8/682
It means 1/3 and 2/3 should be replaced by mandatory-y and I expect
msi.h can be removed from architecture Kbuild too.
Thanks,
Michal
next prev parent reply other threads:[~2019-10-18 6:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 18:19 PCI/MSI: Remove the PCI_MSI_IRQ_DOMAIN architecture whitelist Palmer Dabbelt
2019-10-17 18:19 ` [PATCH 1/3] ia64: Use the generic msi.h Palmer Dabbelt
2019-10-17 18:19 ` [PATCH 2/3] s390: " Palmer Dabbelt
2019-10-17 18:19 ` [PATCH 3/3] pci: Default to PCI_MSI_IRQ_DOMAIN Palmer Dabbelt
2019-10-17 19:11 ` Waiman Long
2019-10-18 6:20 ` Michal Simek [this message]
2019-10-22 15:10 ` PCI/MSI: Remove the PCI_MSI_IRQ_DOMAIN architecture whitelist Palmer Dabbelt
2019-10-24 10:14 ` Michal Simek
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=995f625b-1f56-6d97-ba99-9a4298e9dd37@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=bhelgaas@google.com \
--cc=borntraeger@de.ibm.com \
--cc=fenghua.yu@intel.com \
--cc=firoz.khan@linaro.org \
--cc=gor@linux.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=heiko.carstens@de.ibm.com \
--cc=helgaas@kernel.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@kernel.org \
--cc=palmer@sifive.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=tony.luck@intel.com \
--cc=will@kernel.org \
--cc=yamada.masahiro@socionext.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;
as well as URLs for NNTP newsgroup(s).