From: Bjorn Helgaas <bhelgaas@google.com>
To: Michal Simek <michal.simek@xilinx.com>
Cc: Bjorn Helgaas <bjorn@helgaas.com>,
Linux PCI <linux-pci@vger.kernel.org>,
dtyree@newagemicro.com, Vinod Koul <vkoul@kernel.org>,
dmaengine@vger.kernel.org
Subject: Re: [Bug 203435] New: Xilinx pcie endpoint DMA not functional for ZynqMP PS AXI-PXI DMA endpoint
Date: Fri, 26 Apr 2019 11:14:28 -0500 [thread overview]
Message-ID: <CAErSpo5Xs1XP4i206YKgyubDtZbhY9gqoyruLr6Q9o2dVP4iFw@mail.gmail.com> (raw)
In-Reply-To: <38d59480-3057-9352-677e-a365ad526990@xilinx.com>
On Fri, Apr 26, 2019 at 11:11 AM Michal Simek <michal.simek@xilinx.com> wrote:
>
> Hi Bjorn,
>
> On 26. 04. 19 6:21, Bjorn Helgaas wrote:
> > [+cc linux-pci, Xilinx and DMA engine folks]
> >
> > I'm not sure what to do with this report. It mentions "vivado" and
> > xilinx_ps_pcie_platform.c, neither of which seems to be in mainline or
> > linux-next. A Google search suggests that Vivado is a Xilinx product;
> > maybe this bug report should be directed there?
>
> vivado is xilinx design tool for programmable logic and soc setup.
>
> And this driver is not in mainline but just in xilinx git tree.
> It means you can simply close this.
> And author should contact Xilinx via forums or via git@xilinx.com if
> there is any issue with this driver.
Great, thanks! I've closed the upstream bugzilla.
prev parent reply other threads:[~2019-04-26 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-203435-193951@https.bugzilla.kernel.org/>
2019-04-26 13:21 ` [Bug 203435] New: Xilinx pcie endpoint DMA not functional for ZynqMP PS AXI-PXI DMA endpoint Bjorn Helgaas
2019-04-26 16:11 ` Michal Simek
2019-04-26 16:14 ` Bjorn Helgaas [this message]
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=CAErSpo5Xs1XP4i206YKgyubDtZbhY9gqoyruLr6Q9o2dVP4iFw@mail.gmail.com \
--to=bhelgaas@google.com \
--cc=bjorn@helgaas.com \
--cc=dmaengine@vger.kernel.org \
--cc=dtyree@newagemicro.com \
--cc=linux-pci@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=vkoul@kernel.org \
/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).