From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] qemu/riscv32-virt: Fix missing linux-headers patch
Date: Fri, 21 Jun 2019 07:36:44 +0200 [thread overview]
Message-ID: <20190621073644.4560aece@windsurf> (raw)
In-Reply-To: <20190620204314.GL2216@scaer>
On Thu, 20 Jun 2019 22:43:14 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> > So what I would propose instead is this:
> >
> > diff --git a/package/linux-headers/linux-headers.mk b/package/linux-headers/linux-headers.mk
> > index 95432ade83..46f270a0e1 100644
> > --- a/package/linux-headers/linux-headers.mk
> > +++ b/package/linux-headers/linux-headers.mk
> > @@ -60,7 +60,8 @@ endif # LINUX_HEADERS_CUSTOM_TARBALL
> > # Apply any necessary patches if we are using the headers from a kernel
> > # build.
> > ifeq ($(BR2_KERNEL_HEADERS_AS_KERNEL),y)
> > -LINUX_HEADERS_PATCHES = $(call qstrip,$(BR2_LINUX_KERNEL_PATCH))
> > +LINUX_HEADERS_PATCHES = $(call qstrip,$(BR2_LINUX_KERNEL_PATCH)) \
> > + $(wildcard $(addsuffix /linux,$(call qstrip,$(BR2_GLOBAL_PATCH_DIR))))
> >
> > # We rely on the generic package infrastructure to download and apply
> > # remote patches (downloaded from ftp, http or https). For local
> >
> > Yann, what do you think of this ?
>
> Acked-by: Yann E. MORIN <yann.morin.1998@free.fr>
Thanks. One thing I'm sure of is the order in which patches will be
applied between the patches in BR2_GLOBAL_PATCH_DIR and
BR2_LINUX_KERNEL_PATCH. We need to make sure that what happens for the
linux package happens in the same order for the linux-headers package.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-06-21 5:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 17:56 [Buildroot] [PATCH] qemu/riscv32-virt: Fix missing linux-headers patch Alistair Francis
2019-06-20 18:54 ` Thomas Petazzoni
2019-06-20 20:07 ` Alistair Francis
2019-06-20 20:43 ` Yann E. MORIN
2019-06-20 22:58 ` Alistair Francis
2019-06-21 5:36 ` Thomas Petazzoni [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=20190621073644.4560aece@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