mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@barebox.org>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2 5/6] resource: supply memory type/attrs on all SDRAM requests
Date: Thu, 5 Jun 2025 09:10:48 +0200	[thread overview]
Message-ID: <aEFC-F_GDuaKQA4k@pengutronix.de> (raw)
In-Reply-To: <20250526141914.185212-6-a.fatoum@barebox.org>

Hi Ahmad,

On Mon, May 26, 2025 at 04:19:13PM +0200, Ahmad Fatoum wrote:
>   * Request a region from the registered sdram
>   */
>  struct resource *__request_sdram_region(const char *name, unsigned flags,
> -					resource_size_t start, resource_size_t size)
> +				      resource_size_t start, resource_size_t size,
> +				      enum resource_memtype memtype, unsigned memattrs)
>  {
>  	struct memory_bank *bank;

This changes the prototype in the definition...

> diff --git a/include/memory.h b/include/memory.h
> index 707c0f13130d..7c5b133b7693 100644
> --- a/include/memory.h
> +++ b/include/memory.h
> @@ -33,14 +33,25 @@ int barebox_add_memory_bank(const char *name, resource_size_t start,
>  	if (((rsv)->flags & IORESOURCE_BUSY))
>  
>  struct resource *__request_sdram_region(const char *name, unsigned flags,
> -					resource_size_t start, resource_size_t size);
> +				      resource_size_t start, resource_size_t size);

...but not in the declaration causing intermediate compile errors.

Not sure what the correct fix is here. Could you fixup and send the
last two patches of this series again?

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2025-06-05  7:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-26 14:19 [PATCH v2 0/6] resource: record memory type/attrs on all SDRAM Ahmad Fatoum
2025-05-26 14:19 ` [PATCH v2 1/6] memory: export inside_barebox_area Ahmad Fatoum
2025-05-26 14:19 ` [PATCH v2 2/6] resource: record EFI memory type and attributes Ahmad Fatoum
2025-05-26 14:19 ` [PATCH v2 3/6] resource: add MEMATTRS_ definitions for common attribute sets Ahmad Fatoum
2025-05-26 14:19 ` [PATCH v2 4/6] drivers: tee: optee: separate local variables for each resource Ahmad Fatoum
2025-05-26 14:19 ` [PATCH v2 5/6] resource: supply memory type/attrs on all SDRAM requests Ahmad Fatoum
2025-06-05  7:10   ` Sascha Hauer [this message]
2025-05-26 14:19 ` [PATCH v2 6/6] resource: retire IORESOURCE_BUSY in favor of resource::type Ahmad Fatoum
2025-06-02 12:39 ` [PATCH v2 0/6] resource: record memory type/attrs on all SDRAM Sascha Hauer

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=aEFC-F_GDuaKQA4k@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.fatoum@barebox.org \
    --cc=barebox@lists.infradead.org \
    /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