From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/rauc: needs kernel headers >= 3.0
Date: Fri, 24 Aug 2018 13:49:00 +0200 [thread overview]
Message-ID: <20180824134900.1ccc9c2c@windsurf> (raw)
In-Reply-To: <20180824080217.16181-1-yann.morin.1998@free.fr>
Hello,
On Fri, 24 Aug 2018 10:02:17 +0200, Yann E. MORIN wrote:
> rauc includes <linux/mmc/ioctl.h> which was introduced only in
> linux 3.0.
>
> Also change order to have arch dependencies first.
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Andrey Yurovsky <yurovsky@gmail.com>
As discussed separately, this only solves the problem for the target
build, and not for the host build. So, I would prefer a solution that
adjusts the RAUC code to build with headers < 3.0, so that we solve
both the host and the target problem@the same time.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-24 11:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 8:02 [Buildroot] [PATCH] package/rauc: needs kernel headers >= 3.0 Yann E. MORIN
2018-08-24 11:49 ` Thomas Petazzoni [this message]
2018-08-24 12:01 ` Yann E. MORIN
2018-08-24 12:37 ` Thomas Petazzoni
2018-08-24 15:40 ` Yann E. MORIN
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=20180824134900.1ccc9c2c@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