mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <sha@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] fixup! fastboot: scale default sparse max_download_size with available memory
Date: Mon, 28 Aug 2023 09:57:32 +0200	[thread overview]
Message-ID: <20230828075732.GJ16522@pengutronix.de> (raw)
In-Reply-To: <20230825172939.2857999-1-a.fatoum@pengutronix.de>

On Fri, Aug 25, 2023 at 07:29:39PM +0200, Ahmad Fatoum wrote:
> mem_malloc_end is the end address, so we need to add one to get the size
> out.
> 
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> Forgot to squash
> ---
>  include/memory.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Could you resend the whole patch instead of sending a fixup?

This is one of the cases where b4 only recognizes the fixup patch mail
as a patch, but not the one with the original patch:

Looking up https://lore.barebox.org/20230825172250.2857448-1-a.fatoum@pengutronix.de
Grabbing thread from lore.barebox.org/barebox/20230825172250.2857448-1-a.fatoum@pengutronix.de/t.mbox.gz
Checking for newer revisions
Grabbing search results from lore.kernel.org
Nothing matching that query.
Analyzing 3 messages in the thread
Checking attestation on all messages, may take a moment...
---
  ✓ [PATCH] fixup! fastboot: scale default sparse max_download_size with available memory
  ---
  ✓ Signed: DKIM/lists.infradead.org (From: a.fatoum@pengutronix.de)
---
Total patches: 1
---
Applying: fixup! fastboot: scale default sparse max_download_size with available memory
Patch failed at 0001 fixup! fastboot: scale default sparse max_download_size with available memory
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
error: patch failed: include/memory.h:12
error: include/memory.h: patch does not apply
hint: Use 'git am --show-current-patch=diff' to see the failed patch

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:[~2023-08-28  7:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 17:22 [PATCH] " Ahmad Fatoum
2023-08-25 17:29 ` [PATCH] fixup! " Ahmad Fatoum
2023-08-28  7:57   ` Sascha Hauer [this message]
2023-08-28  6:19 ` [PATCH] " Johannes Zink

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=20230828075732.GJ16522@pengutronix.de \
    --to=sha@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