From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/keepalived: make suport for Linux headers >= 3.2
Date: Fri, 16 Oct 2020 14:27:57 +0200 [thread overview]
Message-ID: <20201016142757.1849f560@windsurf> (raw)
In-Reply-To: <20201016122240.4235-1-vadim4j@gmail.com>
Hello Vadym,
On Fri, 16 Oct 2020 15:22:40 +0300
Vadym Kochan <vadim4j@gmail.com> wrote:
> From: Vadym Kochan <vadym.kochan@plvision.eu>
>
> There are some toolchains which is compiled with Linux 3.2 heaers, it
> would good to support them too because the package bulds fine with them.
>
> Signed-off-by: Vadym Kochan <vadym.kochan@plvision.eu>
Have you looked at commit d01b0bbad04b97a5e8e1dd3ac3c1026555f793fb,
which added this headers >= 3.4 dependency ?
Was the kernel headers check in keepalived mentioned in the commit log
fixed later on ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-10-16 12:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 12:22 [Buildroot] [PATCH] package/keepalived: make suport for Linux headers >= 3.2 Vadym Kochan
2020-10-16 12:27 ` Thomas Petazzoni [this message]
[not found] ` <20201016135120.GA4852@plvision.eu>
2020-10-16 18:07 ` Thomas Petazzoni
2020-10-25 9:25 ` Thomas Petazzoni
2020-10-25 18:01 ` Vadym Kochan
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=20201016142757.1849f560@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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