Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/assimp: remove redundant ':' sign
Date: Mon, 7 May 2018 16:42:12 +0200	[thread overview]
Message-ID: <20180507164212.52eac52b@windsurf> (raw)
In-Reply-To: <1525551191-7113-1-git-send-email-jerzy.m.grzegorek@gmail.com>

Hello,

On Sat,  5 May 2018 22:13:10 +0200, Jerzy Grzegorek wrote:
> Signed-off-by: Jerzy Grzegorek <jerzy.m.grzegorek@gmail.com>
> ---
>  package/assimp/assimp.mk | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/package/assimp/assimp.mk b/package/assimp/assimp.mk
> index 4d44748..e391145 100644
> --- a/package/assimp/assimp.mk
> +++ b/package/assimp/assimp.mk
> @@ -20,7 +20,7 @@ endif
>  # not passed) in gcc versions 5.x or older. The -Os optimization level
>  # causes a "unable to find a register to spill in class
>  # ?GENERAL_REGS?" error. -O2 works fine.
> -ifeq ($(BR2_sh):$(BR2_STATIC_LIBS):$(BR2_TOOLCHAIN_GCC_AT_LEAST_6),y:y:)
> +ifeq ($(BR2_sh)$(BR2_STATIC_LIBS):$(BR2_TOOLCHAIN_GCC_AT_LEAST_6),yy:)

I don't find the ":" to be really redundant. Yes, this ":" is not
technically needed, but it makes the construct very clear and avoids
any possible confusion.

So I think my preference would be to keep things as-is. I know in other
places we don't put a ":" when we need both options to be "y". But when
we have a case where some options need to be "y", some options need to
be empty, I find having a ":" between each to be clearer.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

      parent reply	other threads:[~2018-05-07 14:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-05 20:13 [Buildroot] [PATCH 1/2] package/assimp: remove redundant ':' sign Jerzy Grzegorek
2018-05-05 20:13 ` [Buildroot] [PATCH 2/2] package/aufs: " Jerzy Grzegorek
2018-05-07 14:42 ` 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=20180507164212.52eac52b@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