Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Sergey Bobrenok via buildroot <buildroot@buildroot.org>
Cc: Sergey Bobrenok <SIBobrenok@sberdevices.ru>,
	Alexey Romanov <avromanov@sberdevices.ru>,
	Sergey Bobrenok <sibobrenok@salutedevices.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/pkg-kernel-module: add BR2_MAKE_HOST_DEPENDENCY
Date: Mon, 30 Oct 2023 11:13:37 +0100	[thread overview]
Message-ID: <87o7gg5sfi.fsf@48ers.dk> (raw)
In-Reply-To: <20231024153023.19173-1-sibobrenok@salutedevices.com> (Sergey Bobrenok via buildroot's message of "Tue, 24 Oct 2023 18:30:23 +0300")

>>>>> "Sergey" == Sergey Bobrenok via buildroot <buildroot@buildroot.org> writes:

 > From: Alexey Romanov <avromanov@sberdevices.ru>
 > Commit 0b9efc991f ("linux: use BR2_MAKE") switched LINUX_MAKE to
 > $(BR2_MAKE) to avoid build issue with kernel version >= 6.2 and GNU
 > Make version < 3.82. However, the same issue is actual for kernel
 > modules as well.

 > Using $(BR2_MAKE) should guarantee a consistent behavior between
 > kernel and kernel-modules builds.

 > Signed-off-by: Alexey Romanov <avromanov@sberdevices.ru>
 > Signed-off-by: Sergey Bobrenok <SIBobrenok@sberdevices.ru>

Committed to 2023.08.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2023-10-30 10:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-24 15:30 [Buildroot] [PATCH 1/1] package/pkg-kernel-module: add BR2_MAKE_HOST_DEPENDENCY Sergey Bobrenok via buildroot
2023-10-24 19:23 ` Yann E. MORIN
2023-10-30 10:13 ` Peter Korsgaard [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=87o7gg5sfi.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=SIBobrenok@sberdevices.ru \
    --cc=avromanov@sberdevices.ru \
    --cc=buildroot@buildroot.org \
    --cc=sibobrenok@salutedevices.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox