From: Stephen Hemminger <stephen@networkplumber.org>
To: Przemek Kitszel <przemyslaw.kitszel@intel.com>
Cc: David Ahern <dsahern@kernel.org>,
netdev@vger.kernel.org, Tony Nguyen <anthony.l.nguyen@intel.com>,
Lukasz Czapnik <lukasz.czapnik@intel.com>
Subject: Re: [PATCH iproute2-next 3/3] Makefile: support building from subdirectories
Date: Wed, 3 Jul 2024 08:16:48 -0700 [thread overview]
Message-ID: <20240703081648.3109da55@hermes.local> (raw)
In-Reply-To: <20240703131521.60284-4-przemyslaw.kitszel@intel.com>
On Wed, 3 Jul 2024 15:15:21 +0200
Przemek Kitszel <przemyslaw.kitszel@intel.com> wrote:
> Support building also from subdirectories, like: `make -C devlink` or
> `cd devlink; make`.
>
> Extract common defines and include flags to a new file (common.mk) which
> will be included from subdir makefiles via the generated config.mk file.
>
> Note that the current, toplevel-issued, `make` still works as before.
> Note that `./configure && make` is still required once after the fresh
> checkout.
>
> Signed-off-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
Not sure if this really needed, it impacts more than devlink.
next prev parent reply other threads:[~2024-07-03 15:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 13:15 [PATCH iproute2-next 0/3] minor improvements to makefile, devlink Przemek Kitszel
2024-07-03 13:15 ` [PATCH iproute2-next 1/3] man: devlink-resource: add missing words in the example Przemek Kitszel
2024-07-04 13:31 ` Michal Kubiak
2024-07-03 13:15 ` [PATCH iproute2-next 2/3] devlink: print missing params even if an unknown one is present Przemek Kitszel
2024-07-04 13:33 ` Michal Kubiak
2024-07-03 13:15 ` [PATCH iproute2-next 3/3] Makefile: support building from subdirectories Przemek Kitszel
2024-07-03 15:16 ` Stephen Hemminger [this message]
2024-07-03 15:28 ` Przemek Kitszel
2024-07-07 16:48 ` David Ahern
2024-07-07 16:50 ` [PATCH iproute2-next 0/3] minor improvements to makefile, devlink patchwork-bot+netdevbpf
2024-07-08 22:30 ` patchwork-bot+netdevbpf
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=20240703081648.3109da55@hermes.local \
--to=stephen@networkplumber.org \
--cc=anthony.l.nguyen@intel.com \
--cc=dsahern@kernel.org \
--cc=lukasz.czapnik@intel.com \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.