From: Simon Horman <horms@kernel.org>
To: Bui Quang Minh <minhquangbui99@gmail.com>
Cc: netdev@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
Philip Li <philip.li@intel.com>,
oliver.sang@intel.com, Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] selftests: net: build net/lib dependency in all target
Date: Thu, 29 May 2025 14:34:24 +0100 [thread overview]
Message-ID: <20250529133424.GP1484967@horms.kernel.org> (raw)
In-Reply-To: <da0339d6-b6a3-44d8-8ed4-b99249fa0fd1@gmail.com>
On Thu, May 29, 2025 at 06:04:17PM +0700, Bui Quang Minh wrote:
> On 5/29/25 17:32, Simon Horman wrote:
> > On Thu, May 29, 2025 at 02:05:36PM +0700, Bui Quang Minh wrote:
> > > Currently, we only build net/lib dependency in install target. This
> > > commit moves that to all target so that net/lib is included in in-tree
> > > build and run_tests.
> > Hi,
> >
> > The above describes what is being done.
> > I think it would be good to also describe why.
>
> Hi,
>
> Currently, when building net related selftests, we need to
>
> make install
>
> so that the net/lib is compiled. In case we do
>
> make
>
> or
>
> make run_tests
>
> the net/lib is not compiled. So I move the INSTALL_DEP_TARGETS which is
> net/lib if the selftests is net related to all. As a result, all make/make
> install/make run_tests will have the net/lib compiled.
Thanks for the explanation, it is much appreciated.
I think it would be good to include something along those lines
in the commit message of the patch.
Please note, that if you post a v2, before doing so you should allow 24h to
elapse since the posting of v1.
https://docs.kernel.org/process/maintainer-netdev.html
next prev parent reply other threads:[~2025-05-29 13:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 7:05 [PATCH net] selftests: net: build net/lib dependency in all target Bui Quang Minh
2025-05-29 10:32 ` Simon Horman
2025-05-29 11:04 ` Bui Quang Minh
2025-05-29 13:34 ` Simon Horman [this message]
2025-05-29 14:18 ` Bui Quang Minh
2025-05-29 23:39 ` Jakub Kicinski
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=20250529133424.GP1484967@horms.kernel.org \
--to=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=minhquangbui99@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=oliver.sang@intel.com \
--cc=philip.li@intel.com \
--cc=shuah@kernel.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).