buildroot.buildroot.org archive mirror
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 4/4] linux: remove dirs dependency
Date: Thu, 06 Mar 2014 18:37:43 +0100	[thread overview]
Message-ID: <5318B267.2020301@mind.be> (raw)
In-Reply-To: <1394098949-31981-5-git-send-email-fabio.porcedda@gmail.com>

On 06/03/14 10:42, Fabio Porcedda wrote:
> The "dirs" dependency is redundant because now the "generic-package"
> infrastructure add automatically the "dirs" dependency so just remove
> the redundant references.
> 
> Signed-off-by: Fabio Porcedda <fabio.porcedda@gmail.com>

Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>


 There are also redundant dependencies on dirs in Makefile and in
package/uclibc/uclibc.mk - that can be done in a separate patch, but if
you get around to fixing the other places before this one gets committed
please do include it.


 Regards,
 Arnout


> ---
>  linux/linux.mk | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/linux/linux.mk b/linux/linux.mk
> index 3d52e69..e270705 100644
> --- a/linux/linux.mk
> +++ b/linux/linux.mk
> @@ -302,12 +302,12 @@ include $(sort $(wildcard linux/linux-ext-*.mk))
>  $(eval $(generic-package))
>  
>  ifeq ($(BR2_LINUX_KERNEL),y)
> -linux-menuconfig linux-xconfig linux-gconfig linux-nconfig linux26-menuconfig linux26-xconfig linux26-gconfig linux26-nconfig: dirs linux-configure
> +linux-menuconfig linux-xconfig linux-gconfig linux-nconfig linux26-menuconfig linux26-xconfig linux26-gconfig linux26-nconfig: linux-configure
>  	$(MAKE) $(LINUX_MAKE_FLAGS) -C $(LINUX_DIR) \
>  		$(subst linux-,,$(subst linux26-,,$@))
>  	rm -f $(LINUX_DIR)/.stamp_{built,target_installed,images_installed}
>  
> -linux-savedefconfig linux26-savedefconfig: dirs linux-configure
> +linux-savedefconfig linux26-savedefconfig: linux-configure
>  	$(MAKE) $(LINUX_MAKE_FLAGS) -C $(LINUX_DIR) \
>  		$(subst linux-,,$(subst linux26-,,$@))
>  
> 


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2014-03-06 17:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06  9:42 [Buildroot] [PATCH v2 0/4] Misc patches Fabio Porcedda
2014-03-06  9:42 ` [Buildroot] [PATCH v2 1/4] webkit: fix mmu reverse dependency moving it to %_ARCH_SUPPORTS Fabio Porcedda
2014-03-06 17:27   ` Arnout Vandecappelle
2014-03-06  9:42 ` [Buildroot] [PATCH v2 2/4] Makefile: remove BASE_TARGETS variable Fabio Porcedda
2014-03-06 17:30   ` Arnout Vandecappelle
2014-03-06  9:42 ` [Buildroot] [PATCH v2 3/4] linux: fix coding style Fabio Porcedda
2014-03-06 17:34   ` Arnout Vandecappelle
2014-03-06  9:42 ` [Buildroot] [PATCH v2 4/4] linux: remove dirs dependency Fabio Porcedda
2014-03-06 17:37   ` Arnout Vandecappelle [this message]
2014-03-07  8:41     ` Fabio Porcedda
2014-03-06 21:52 ` [Buildroot] [PATCH v2 0/4] Misc patches Thomas Petazzoni

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=5318B267.2020301@mind.be \
    --to=arnout@mind.be \
    --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;
as well as URLs for NNTP newsgroup(s).