From: Thomas Monjalon <thomas@monjalon.net>
To: Tanzeel Ahmed <tanzeelahmed713@gmail.com>
Cc: Ori Kam <orika@nvidia.com>,
dev@dpdk.org, Shani Peretz <shperetz@nvidia.com>
Subject: Re: [PATCH] examples/flow_filtering: fix make clean
Date: Wed, 09 Jul 2025 17:56:49 +0200 [thread overview]
Message-ID: <6926478.STdkYbjpsp@thomas> (raw)
In-Reply-To: <SA1PR12MB94916D6069CBED1D815FA460BFAE2@SA1PR12MB9491.namprd12.prod.outlook.com>
> > make clean is unable to delete build directory because *.o files are not
> > removed.
> >
> > The other way to fix this would be to add all the c files into SRCS-y.
> >
> > Signed-off-by: Tanzeel Ahmed <tanzeelahmed713@gmail.com>
>
> I checked and looks good on my side
Applied with fixes line, thanks.
prev parent reply other threads:[~2025-07-09 15:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-29 19:53 Tanzeel Ahmed
2025-03-31 8:45 ` Thomas Monjalon
2025-03-31 21:56 ` Tanzeel Ahmed
2025-04-03 7:01 ` Shani Peretz
2025-07-09 15:56 ` 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=6926478.STdkYbjpsp@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=orika@nvidia.com \
--cc=shperetz@nvidia.com \
--cc=tanzeelahmed713@gmail.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).