All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Andrea Claudi <aclaudi@redhat.com>
Cc: netdev@vger.kernel.org, stephen@networkplumber.org, dsahern@gmail.com
Subject: Re: [PATCH iproute2-next] Makefile: move HAVE_MLN check to top-level Makefile
Date: Sat, 12 Mar 2022 16:10:11 +0000	[thread overview]
Message-ID: <164710141175.15431.5685294809613073920.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <814bc876484374530642f61f999a0c136a6a492c.1646845304.git.aclaudi@redhat.com>

Hello:

This patch was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:

On Wed,  9 Mar 2022 18:03:26 +0100 you wrote:
> dcb, devlink, rdma, tipc and vdpa rely on libmnl to compile, so they
> check for libmnl to be installed on their Makefiles.
> 
> This moves HAVE_MNL check from the tools to top-level Makefile, thus
> avoiding to call their Makefiles if libmnl is not present.
> 
> Signed-off-by: Andrea Claudi <aclaudi@redhat.com>
> 
> [...]

Here is the summary with links:
  - [iproute2-next] Makefile: move HAVE_MLN check to top-level Makefile
    https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=93fb6810e146

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2022-03-12 16:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09 17:03 [PATCH iproute2-next] Makefile: move HAVE_MLN check to top-level Makefile Andrea Claudi
2022-03-12 16:10 ` patchwork-bot+netdevbpf [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=164710141175.15431.5685294809613073920.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=aclaudi@redhat.com \
    --cc=dsahern@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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 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.