From: Tanzeel Ahmed <tanzeelahmed713@gmail.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: orika@nvidia.com, dev@dpdk.org, Shani Peretz <shperetz@nvidia.com>
Subject: Re: [PATCH] examples/flow_filtering: fix make clean
Date: Tue, 1 Apr 2025 02:56:25 +0500 [thread overview]
Message-ID: <CAPDzQQ5GKePRVgzxPotBvjpzXrrCPjgfGo1mRxnwLX_U55Ezhw@mail.gmail.com> (raw)
In-Reply-To: <5791577.oiGErgHkdL@thomas>
On Mon, 31 Mar 2025 at 13:45, Thomas Monjalon:
>
> 29/03/2025 20:53, Tanzeel Ahmed:
> > make clean is unable to delete build directory
> > because *.o files are not removed.
Removing .o files is a simpler fix, as in the patch.
> > The other way to fix this would be to add all the
> > c files into SRCS-y.
>
> How adding all C files into SRCS-y would help?
We can bypass the obj files generation and use the current clean as it is
next prev parent reply other threads:[~2025-04-01 8:07 UTC|newest]
Thread overview: 4+ 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 [this message]
2025-04-03 7:01 ` Shani Peretz
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=CAPDzQQ5GKePRVgzxPotBvjpzXrrCPjgfGo1mRxnwLX_U55Ezhw@mail.gmail.com \
--to=tanzeelahmed713@gmail.com \
--cc=dev@dpdk.org \
--cc=orika@nvidia.com \
--cc=shperetz@nvidia.com \
--cc=thomas@monjalon.net \
/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).