All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Alexander Egorenkov <egorenar-dev@posteo.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/multipath-tools: fix path to kernel headers
Date: Tue, 21 Feb 2023 09:37:56 +0100	[thread overview]
Message-ID: <20230221093756.06a8f7c5@windsurf> (raw)
In-Reply-To: <20230218092943.2598-1-egorenar-dev@posteo.net>

On Sat, 18 Feb 2023 09:29:43 +0000
Alexander Egorenkov <egorenar-dev@posteo.net> wrote:

> With change 6b7d47be3b23 ("multipath-tools: Makefiles: simplify code for
> include dirs") the Makefile variable 'LINUX_HEADERS_INCDIR' has been replaced
> with 'kernel_incdir'.
> 
> fpin_handlers.c:355:32: note: each undeclared identifier is reported only once for each function it appears in
> fpin_handlers.c:360:37: error: ‘ELS_DTAG_LNK_INTEGRITY’ undeclared (first use in this function)
>   360 |                         if (dtag == ELS_DTAG_LNK_INTEGRITY) {
>       |                                     ^~~~~~~~~~~~~~~~~~~~~~
> make[2]: *** [../Makefile.inc:116: fpin_handlers.o] Error 1
> 
> Fixes: http://autobuild.buildroot.net/results/e0f56ef924c13d6b1535fdc350ad8ecc06ea0a58
> Signed-off-by: Alexander Egorenkov <egorenar-dev@posteo.net>
> ---
>  package/multipath-tools/multipath-tools.mk | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-02-21  8:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-18  9:29 [Buildroot] [PATCH 1/1] package/multipath-tools: fix path to kernel headers Alexander Egorenkov
2023-02-21  8:37 ` Thomas Petazzoni via buildroot [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=20230221093756.06a8f7c5@windsurf \
    --to=buildroot@buildroot.org \
    --cc=egorenar-dev@posteo.net \
    --cc=thomas.petazzoni@bootlin.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.