Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 2/3] core/pkg-kconfig: Do not use $(call ...) without parameters
Date: Mon, 18 Apr 2016 23:17:48 +0200	[thread overview]
Message-ID: <20160418231748.6f93d48f@free-electrons.com> (raw)
In-Reply-To: <1460971383-10595-3-git-send-email-romain.izard.pro@gmail.com>

Hello,

On Mon, 18 Apr 2016 11:23:02 +0200, Romain Izard wrote:
> When there are no parameters, simply use $(var) instead of $(call var)
> 
> Signed-off-by: Romain Izard <romain.izard.pro@gmail.com>
> ---
> Changelog:
> v3: new
> v4: no change

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2016-04-18 21:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-18  9:23 [Buildroot] [PATCH v4 0/3] core/pkg-kconfig: Fix .config generation Romain Izard
2016-04-18  9:23 ` [Buildroot] [PATCH v4 1/3] core/pkg-kconfig: Factorize make commands Romain Izard
2016-04-18 20:32   ` Yann E. MORIN
2016-04-18 21:17   ` Thomas Petazzoni
2016-04-18  9:23 ` [Buildroot] [PATCH v4 2/3] core/pkg-kconfig: Do not use $(call ...) without parameters Romain Izard
2016-04-18 20:33   ` Yann E. MORIN
2016-04-18 21:17   ` Thomas Petazzoni [this message]
2016-04-18  9:23 ` [Buildroot] [PATCH v4 3/3] core/pkg-kconfig: Use oldnoconfig when possible Romain Izard
2016-04-18 21:08   ` Yann E. MORIN
2016-04-18 21:16     ` Yann E. MORIN
2016-04-19  9:11     ` Romain Izard
2016-04-19 17:40       ` Yann E. MORIN
2016-04-19 17:58         ` Yann E. MORIN
2016-04-20  7:14           ` Romain Izard

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=20160418231748.6f93d48f@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