All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: Tom Rini <trini@konsulko.com>, u-boot@lists.denx.de
Cc: Tim Harvey <tharvey@gateworks.com>
Subject: Re: [PATCH] cmd: mvebu/bubt: Correct usage of IS_ENABLED() macro
Date: Thu, 27 Feb 2025 10:25:32 +0100	[thread overview]
Message-ID: <a154ee92-ba2d-49b7-b128-2fcabd084bf5@denx.de> (raw)
In-Reply-To: <20250226203118.3831940-1-trini@konsulko.com>

On 26.02.25 21:31, Tom Rini wrote:
> This file was using IS_ENABLED() to test for CONFIG flags but omitted
> the CONFIG_ prefix and so did not work as expected.
> 
> Signed-off-by: Tom Rini <trini@konsulko.com>
> ---
> Cc: Tim Harvey <tharvey@gateworks.com>
> Cc: Stefan Roese <sr@denx.de>
> 
> This does change how some platforms are built.

Reviewed-by: Stefan Roese <sr@denx.de>

Thanks,
Stefan

> ---
>   cmd/mvebu/bubt.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/cmd/mvebu/bubt.c b/cmd/mvebu/bubt.c
> index 5e4ffc40d729..6b7d9ee061d5 100644
> --- a/cmd/mvebu/bubt.c
> +++ b/cmd/mvebu/bubt.c
> @@ -931,7 +931,7 @@ static int check_image_header(void)
>   	size = le32_to_cpu(hdr->blocksize);
>   
>   	if (hdr->blockid == 0x78) { /* SATA id */
> -		struct blk_desc *blk_dev = IS_ENABLED(BLK) ? blk_get_devnum_by_uclass_id(UCLASS_SCSI, 0) : NULL;
> +		struct blk_desc *blk_dev = IS_ENABLED(CONFIG_BLK) ? blk_get_devnum_by_uclass_id(UCLASS_SCSI, 0) : NULL;
>   		unsigned long blksz = blk_dev ? blk_dev->blksz : 512;
>   		offset *= blksz;
>   	}

Viele Grüße,
Stefan Roese

-- 
DENX Software Engineering GmbH,      Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-51 Fax: (+49)-8142-66989-80 Email: sr@denx.de


  reply	other threads:[~2025-02-27  9:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-26 20:31 [PATCH] cmd: mvebu/bubt: Correct usage of IS_ENABLED() macro Tom Rini
2025-02-27  9:25 ` Stefan Roese [this message]
2025-04-16 13:31 ` Stefan Roese

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=a154ee92-ba2d-49b7-b128-2fcabd084bf5@denx.de \
    --to=sr@denx.de \
    --cc=tharvey@gateworks.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.