From: "Xu, Rosen" <rosen.xu@intel.com>
To: David Marchand <david.marchand@redhat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [Bug 1094] Add FPGA bus cleanup
Date: Tue, 14 Mar 2023 08:53:20 +0000 [thread overview]
Message-ID: <DM6PR11MB4252F624EDC6F9AE3C1A999889BE9@DM6PR11MB4252.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8z8iidrtfT1y3GWkq38q8rsPCDPy9za2BDf9v-c+UEo8Q@mail.gmail.com>
Hi David,
Sorry I miss that email, I will try to fix it ASAP.
Thanks,
Rosen
> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Tuesday, March 14, 2023 4:20 PM
> To: Xu, Rosen <rosen.xu@intel.com>
> Cc: dev@dpdk.org
> Subject: Re: [Bug 1094] Add FPGA bus cleanup
>
> Hi Rosen,
>
> I don't think you are subscribed to bugzilla, so pinging here.
>
> On Wed, Oct 5, 2022 at 12:49 PM <bugzilla@dpdk.org> wrote:
> >
> > https://bugs.dpdk.org/show_bug.cgi?id=1094
> >
> > Bug ID: 1094
> > Summary: Add FPGA bus cleanup
> > Product: DPDK
> > Version: unspecified
> > Hardware: All
> > OS: All
> > Status: UNCONFIRMED
> > Severity: normal
> > Priority: Normal
> > Component: other
> > Assignee: dev@dpdk.org
> > Reporter: kevin.laatz@intel.com
> > Target Milestone: future
> >
> > Bus cleanup is now done as part of EAL cleanup [1].
> >
> > A new cleanup function should be implemented and registered to the bus
> > struct to ensure proper cleanup is done for devices on the FPGA bus on
> shutdown.
> >
> > [1]
> >
> https://github.com/DPDK/dpdk/commit/1cab1a40ea9b858821aaf4655486e31
> ca1
> > b52456
>
> Can you register to bugzilla and have a look?
> Thanks.
>
>
> --
> David Marchand
prev parent reply other threads:[~2023-03-14 8:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 10:48 bugzilla
2023-03-14 8:19 ` David Marchand
2023-03-14 8:53 ` Xu, Rosen [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=DM6PR11MB4252F624EDC6F9AE3C1A999889BE9@DM6PR11MB4252.namprd11.prod.outlook.com \
--to=rosen.xu@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.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).