All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Alan Mikhak <alan.mikhak@sifive.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	linux-riscv@lists.infradead.org,
	Palmer Dabbelt <palmer@sifive.com>,
	Paul Walmsley <paul.walmsley@sifive.com>
Subject: Re: [PATCH v2] PCI: endpoint: Set endpoint controller pointer to null
Date: Sat, 25 May 2019 01:23:24 -0700	[thread overview]
Message-ID: <20190525082324.GB18854@infradead.org> (raw)
In-Reply-To: <CABEDWGxUDkNOcpT1K+Ez2i47TKi8bHRn-32NaVNkCQgkbPbvmw@mail.gmail.com>

On Fri, May 24, 2019 at 11:23:04AM -0700, Alan Mikhak wrote:
> Chrisoph,
> 
> These changes were implemented in Linux PCI Endpoint framework to
> exercise PCIe endpoint mode on RISCV.

Well, arch/riscv isn't involved in this patch (which having an interest
in the PCIe EP stuff I really like).  I still don't see how it relates
to riscv except that you apparently have been able to use it on a
RISCV SOC somehow.


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2019-05-25  8:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-23 21:45 [PATCH v2] PCI: endpoint: Set endpoint controller pointer to null Alan Mikhak
2019-05-23 21:45 ` Alan Mikhak
2019-05-23 23:57 ` Alan Mikhak
2019-05-23 23:57   ` Alan Mikhak
2019-05-24  8:41   ` Kishon Vijay Abraham I
2019-05-24  8:41     ` Kishon Vijay Abraham I
2019-05-24  6:38 ` Christoph Hellwig
2019-05-24 18:23   ` Alan Mikhak
2019-05-25  8:23     ` Christoph Hellwig [this message]
2019-05-24 19:04   ` Paul Walmsley
2019-05-24 19:05     ` Alan Mikhak
2019-05-25  8:24       ` Christoph Hellwig
2019-05-28 16:20         ` Alan Mikhak
2019-05-30  2:24           ` Palmer Dabbelt
2019-06-11 10:07 ` Lorenzo Pieralisi
2019-06-11 10:07   ` Lorenzo Pieralisi

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=20190525082324.GB18854@infradead.org \
    --to=hch@infradead.org \
    --cc=alan.mikhak@sifive.com \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@sifive.com \
    --cc=paul.walmsley@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 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.