From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] aufs: added 'fs' dir to $(LINUX_DIR)
Date: Thu, 31 Jul 2014 19:54:08 +0200 [thread overview]
Message-ID: <20140731195408.29cdee0b@free-electrons.com> (raw)
In-Reply-To: <1406827250-11821-1-git-send-email-s.hoenig@openthinclient.com>
Dear Steffen Hoenig,
On Thu, 31 Jul 2014 19:20:50 +0200, Steffen Hoenig wrote:
> For later calls of linux-menuconfig, you need the Kconfig of aufs
>
> Signed-off-by: Steffen Hoenig <s.hoenig@openthinclient.com>
> ---
> package/aufs/aufs.mk | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/package/aufs/aufs.mk b/package/aufs/aufs.mk
> index c1b21c4..5d072bb 100644
> --- a/package/aufs/aufs.mk
> +++ b/package/aufs/aufs.mk
> @@ -27,6 +27,7 @@ define AUFS_INSTALL_STAGING_CMDS
> $(MAKE) -C $(@D) $(LINUX_MAKE_FLAGS) KDIR=$(LINUX_DIR) usr/include/linux/aufs_type.h
> $(INSTALL) -p -m 0644 $(@D)/usr/include/linux/aufs_type.h \
> $(STAGING_DIR)/usr/include/linux
> + tar cf - -C $(@D) fs | (cd $(LINUX_DIR) && tar xf -)
> endef
>
> define AUFS_INSTALL_TARGET_CMDS
Your original patches have not been applied (yet). So if you have
changes to do, please resend a new version of your original patches
with whatever fixes are needed. When you do so, please include a
changelog that describes the changes between the previous version.
See
http://buildroot.org/downloads/manual/manual.html#submitting-patches
for more details.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-07-31 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 17:20 [Buildroot] [PATCH 3/3] aufs: added 'fs' dir to $(LINUX_DIR) Steffen Hoenig
2014-07-31 17:54 ` 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=20140731195408.29cdee0b@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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