From: patchwork-bot+netdevbpf@kernel.org
To: Luca Boccassi <luca.boccassi@gmail.com>
Cc: netdev@vger.kernel.org, stephen@networkplumber.org, aclaudi@redhat.com
Subject: Re: [PATCH iproute2] Revert "Makefile: ensure CONF_USR_DIR honours the libdir config"
Date: Mon, 13 Nov 2023 16:40:23 +0000 [thread overview]
Message-ID: <169989362317.31764.14802237194303164325.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231106001410.183542-1-luca.boccassi@gmail.com>
Hello:
This patch was applied to iproute2/iproute2.git (main)
by Stephen Hemminger <stephen@networkplumber.org>:
On Mon, 6 Nov 2023 00:14:10 +0000 you wrote:
> From: Luca Boccassi <bluca@debian.org>
>
> LIBDIR in Debian and derivatives is not /usr/lib/, it's
> /usr/lib/<architecture triplet>/, which is different, and it's the
> wrong location where to install architecture-independent default
> configuration files, which should always go to /usr/lib/ instead.
> Installing these files to the per-architecture directory is not
> the right thing, hence revert the change.
>
> [...]
Here is the summary with links:
- [iproute2] Revert "Makefile: ensure CONF_USR_DIR honours the libdir config"
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=deb66acabe44
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-11-13 16:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 0:14 [PATCH iproute2] Revert "Makefile: ensure CONF_USR_DIR honours the libdir config" luca.boccassi
2023-11-10 13:34 ` Petr Machata
2023-11-10 13:54 ` Petr Machata
2023-11-10 20:31 ` Andrea Claudi
2023-11-10 22:01 ` Luca Boccassi
2023-11-10 13:54 ` Luca Boccassi
2023-11-13 16:40 ` patchwork-bot+netdevbpf [this message]
2023-11-13 18:12 ` Andrea Claudi
2023-11-13 23:38 ` Stephen Hemminger
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=169989362317.31764.14802237194303164325.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aclaudi@redhat.com \
--cc=luca.boccassi@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.