From: Thomas Monjalon <thomas@monjalon.net>
To: Abhijit Gangurde <abhijit.gangurde@amd.com>
Cc: nikhil.agarwal@amd.com, dev@dpdk.org, david.marchand@redhat.com,
ferruh.yigit@amd.com, Nipun Gupta <nipun.gupta@amd.com>
Subject: Re: [PATCH v2 0/3] bus/cdx: fix coverity issue
Date: Tue, 27 Jun 2023 23:22:56 +0200 [thread overview]
Message-ID: <5742860.1B3tZ46Xf9@thomas> (raw)
In-Reply-To: <de6a4336-4003-c6f6-602c-4a15712f1996@amd.com>
19/06/2023 05:58, Nipun Gupta:
>
> Please use in-reply-to while sending subsequent version of patches.
>
> On 6/16/2023 6:09 PM, Abhijit Gangurde wrote:
> > This series fixes coverity issues 385379, 385381, 385377
> >
> > v2:
> > - Merged coverity fix patches into series
> > - Updated commit message
>
> Series Acked-by: Nipun Gupta <nipun.gupta@amd.com>
Applied, thanks.
prev parent reply other threads:[~2023-06-27 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 12:39 Abhijit Gangurde
2023-06-16 12:39 ` [PATCH v2 1/3] bus/cdx: remove ineffective code statement Abhijit Gangurde
2023-06-16 12:39 ` [PATCH v2 2/3] bus/cdx: move debug print before unmapping resource Abhijit Gangurde
2023-06-16 12:39 ` [PATCH v2 3/3] bus/cdx: fix resource leak Abhijit Gangurde
2023-06-19 3:58 ` [PATCH v2 0/3] bus/cdx: fix coverity issue Nipun Gupta
2023-06-27 21:22 ` Thomas Monjalon [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=5742860.1B3tZ46Xf9@thomas \
--to=thomas@monjalon.net \
--cc=abhijit.gangurde@amd.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=nikhil.agarwal@amd.com \
--cc=nipun.gupta@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).