mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH master 1/3] resource: return NULL for error in request_barebox_region
Date: Wed, 24 Jul 2024 10:08:39 +0200	[thread overview]
Message-ID: <172180851924.1897195.927465653425893407.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20240722170606.3866957-1-a.fatoum@pengutronix.de>


On Mon, 22 Jul 2024 19:06:04 +0200, Ahmad Fatoum wrote:
> The function currently returns NULL for error if the range is in SDRAM
> and couldn't be requested or an error pointer if the range is outside.
> 
> Reduce the confusion by using only one way to indicate error. As
> request_barebox_region is used to replace request_sdram_region calls and
> that returns NULL on error, follow suit.
> 
> [...]

Applied, thanks!

[1/3] resource: return NULL for error in request_barebox_region
      https://git.pengutronix.de/cgit/barebox/commit/?id=43b22bac73b7 (link may not be stable)
[2/3] ARM: i.MX8M: scratch: fix initcall return code on request_barebox_region error
      https://git.pengutronix.de/cgit/barebox/commit/?id=302d824e27f3 (link may not be stable)
[3/3] RISC-V: cpu: fix initcall return code on request_barebox_region error
      https://git.pengutronix.de/cgit/barebox/commit/?id=9f09e687430f (link may not be stable)

Best regards,
-- 
Sascha Hauer <s.hauer@pengutronix.de>




      parent reply	other threads:[~2024-07-24  8:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-22 17:06 Ahmad Fatoum
2024-07-22 17:06 ` [PATCH master 2/3] ARM: i.MX8M: scratch: fix initcall return code on request_barebox_region error Ahmad Fatoum
2024-07-22 17:06 ` [PATCH master 3/3] RISC-V: cpu: " Ahmad Fatoum
2024-07-22 17:49 ` [PATCH master 1/3] resource: return NULL for error in request_barebox_region Marco Felsch
2024-07-23  6:07   ` Ahmad Fatoum
2024-07-24  8:08 ` Sascha Hauer [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=172180851924.1897195.927465653425893407.b4-ty@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --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