U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: E Shattow <e@freeshell.de>
To: Martin Herren <sputnik@on-the-web.ch>,
	"u-boot@lists.denx.de" <u-boot@lists.denx.de>
Subject: Re: Looking for mentoring submitting my patch for SYS_BOOTM_LEN adjustement for riscv
Date: Fri, 11 Jul 2025 20:03:40 -0700	[thread overview]
Message-ID: <417acdec-67e7-4aca-9942-de34b19c4fe6@freeshell.de> (raw)
In-Reply-To: <ZuEBDA2GKTZJzMfYunZN62OM1OpnpKwMbwVlOleqz1CUxcyor7Hpb0FivfZzPJQxk36MFaqr9-ut_SbeSHmh8XwvkEdeWtTVLVQTLqq-Om4=@on-the-web.ch>

Hi Martin,

On 7/10/25 14:50, Martin Herren wrote:
> Hello all,
> 
> My first post here. Is there someone willing to mentor me to submit my first patch ?
> 
> The patch is the following 3 commits:
> https://github.com/u-boot/u-boot/compare/master...MartinHerren:u-boot:set_default_sys_bootm_len_for_riscv
> 
> It adjusts the SYS_BOOTM_LEN for RISCV to the most commonly used value.
> 
> For context, working on rebasing the Allwinner D1 branch on some u-boot fork to up-to-date U-Boot I saw that the strange way in which SYS_BOOTM_LEN was patched in Yocto's meta-riscv layer was not working anymore, so I tried a clean fix and thought an adjustment of the SYS_BOOTM_LEN's default for riscv might make sense.
> 
> So if anyone is willing to mentor me in submitting this patch this would be welcome !
> It is mostly the patman part that is still a big unknown for me and i'm afraid of spamming far too many people trying by myself otherwise.
> 
> Or does this patch not make sense at all ?
> 
> Thanks !
> 
> Martin

Without comment to the content of your patch series I think such review
happens on the mailing list and in that way patchwork [1] can track it
and it's just how things seem to be done for U-Boot upstream. Please do
format-patch and send-email your series with a cover letter to the
mailing list.

1: https://patchwork.ozlabs.org/project/uboot/list/

Best regards,

-E Shattow

      reply	other threads:[~2025-07-12  3:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-10 21:50 Looking for mentoring submitting my patch for SYS_BOOTM_LEN adjustement for riscv Martin Herren
2025-07-12  3:03 ` E Shattow [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=417acdec-67e7-4aca-9942-de34b19c4fe6@freeshell.de \
    --to=e@freeshell.de \
    --cc=sputnik@on-the-web.ch \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox