From: David Marchand <david.marchand@redhat.com>
To: Akhil Goyal <gakhil@marvell.com>
Cc: Sunil Uttarwar <sunilprakashrao.uttarwar@amd.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"selwin.sebastian@amd.com" <selwin.sebastian@amd.com>
Subject: Re: [EXT] [PATCH v1] crypto/ccp: bug fixes for ccp device probe flow
Date: Thu, 2 Mar 2023 12:53:48 +0100 [thread overview]
Message-ID: <CAJFAV8x=6ZvHA9+1psPHtERYj3V+EUc1xVVTC7pGeGa-X-axpw@mail.gmail.com> (raw)
In-Reply-To: <CO6PR18MB4484E980D34F36AE36CFA605D8AF9@CO6PR18MB4484.namprd18.prod.outlook.com>
On Mon, Feb 27, 2023 at 7:29 PM Akhil Goyal <gakhil@marvell.com> wrote:
>
> > - Fixed flow for probe and initialization of requested ccp devices
> > - Removed unnecessary code enumerating for all the PCI devices
> > available in the system.
> > - Removed ccp_pmd_init_done flag controlling probe and initialization
> > of only one CCP device even if other CCP devices available
> >
> > Signed-off-by: Sunil Uttarwar <sunilprakashrao.uttarwar@amd.com>
> Hi Sunil,
>
> Kindly work with David for the patch that was not merged and rebase this patch as needed.
>
> Marking this patch as changes requested.
Sorry, I kept on postponing work on this patch of mine... thanks for
keeping on pinging me Akhil :-).
I sent a v3 which should address Sunil comment.
--
David Marchand
next prev parent reply other threads:[~2023-03-02 11:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 13:56 Sunil Uttarwar
2023-02-27 18:29 ` [EXT] " Akhil Goyal
2023-03-02 11:53 ` David Marchand [this message]
2023-03-06 12:58 ` [PATCH v2] " Sunil Uttarwar
2023-03-11 18:47 ` [EXT] " Akhil Goyal
2023-03-14 10:49 ` Akhil Goyal
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='CAJFAV8x=6ZvHA9+1psPHtERYj3V+EUc1xVVTC7pGeGa-X-axpw@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=selwin.sebastian@amd.com \
--cc=sunilprakashrao.uttarwar@amd.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).