From: Paul Walmsley <paul.walmsley@sifive.com>
To: Wesley Terpstra <wesley@sifive.com>,
Christoph Hellwig <hch@infradead.org>
Cc: linux-riscv@lists.infradead.org, Paul Walmsley <paul@pwsan.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: include generic support for MSI irqdomains
Date: Tue, 21 May 2019 01:11:27 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1905210110220.24268@viisi.sifive.com> (raw)
In-Reply-To: <20190521063551.GA5959@infradead.org>
On Mon, 20 May 2019, Christoph Hellwig wrote:
> On Mon, May 20, 2019 at 11:25:28AM -0700, Paul Walmsley wrote:
> > Some RISC-V systems include PCIe host controllers that support PCIe
> > message-signaled interrupts. For this to work on Linux, we need to
> > enable PCI_MSI_IRQ_DOMAIN and define struct msi_alloc_info. Support
> > for the latter is enabled by including the architecture-generic msi.h
> > include.
> >
> > Based on a patch from Wesley Terpstra <wesley@sifive.com>:
> >
> > https://github.com/riscv/riscv-linux/commit/7d55f38fb79f459d2e88bcee7e147796400cafa8
> >
> > Signed-off-by: Paul Walmsley <paul.walmsley@sifive.com>
> > Signed-off-by: Paul Walmsley <paul@pwsan.com>
> > Cc: Wesley Terpstra <wesley@sifive.com>
>
> Well, this is very much Wes' patch as-is. It should probably be
> attributed to him and you should ask for his signoff.
Yeah. There aren't many other ways to do it.
Wes, care to reply with your Signed-off-by: ?
- Paul
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-05-21 8:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 18:25 [PATCH] riscv: include generic support for MSI irqdomains Paul Walmsley
2019-05-21 6:35 ` Christoph Hellwig
2019-05-21 8:11 ` Paul Walmsley [this message]
2019-05-21 18:25 ` Wesley Terpstra
2019-05-21 19:01 ` Paul Walmsley
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=alpine.DEB.2.21.9999.1905210110220.24268@viisi.sifive.com \
--to=paul.walmsley@sifive.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=paul@pwsan.com \
--cc=wesley@sifive.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).