All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mattijs Korpershoek <mkorpershoek@kernel.org>
To: Mehmet Fide <mehmet.fide@gmail.com>,
	Francesco Dolcini <francesco.dolcini@toradex.com>
Cc: Tom Rini <trini@konsulko.com>,
	Lukasz Majewski <lukma@nabladev.com>,
	u-boot@lists.u-boot-project.org, mehmet.fide@screeningeagle.com
Subject: Re: [PATCH] colibri_vf: separate the partition numbers in dfu_alt_info with a space
Date: Mon, 26 Oct 2026 10:48:52 +0100	[thread overview]
Message-ID: <xhkdbecdc3i7v.fsf@mkorpers-koolstof.csb> (raw)
In-Reply-To: <20261024113459.3259910-1-mehmet.fide@gmail.com>

Hi Mehmet,

Thank you for the patch.

On Sat, Oct 24, 2026 at 13:34, Mehmet Fide <mehmet.fide@gmail.com> wrote:

> From: Mehmet Fide <mehmet.fide@screeningeagle.com>
>
> Since commit 53b406369e9d ("DFU: Check the number of arguments and
> argument string strictly") the NAND backend takes an entry as
> "<name> part <dev> <part>", three arguments. The default dfu_alt_info
> of colibri_vf still uses the older "part 0,1" form, two arguments, so
> its first entry already fails with -EINVAL and "dfu 0 nand 0" returns
> at once, before the gadget starts.
>
> Separate the device and the partition number with a space. The
> partitions stay the same: vf-bcb, u-boot and ubi.
>
> Fixes: 53b406369e9d ("DFU: Check the number of arguments and argument string strictly")
> Signed-off-by: Mehmet Fide <mehmet.fide@screeningeagle.com>

Reviewed-by: Mattijs Korpershoek <mkorpershoek@kernel.org>


      parent reply	other threads:[~2026-10-26  9:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-24 11:34 [PATCH] colibri_vf: separate the partition numbers in dfu_alt_info with a space Mehmet Fide
2026-10-25 18:33 ` Francesco Dolcini
2026-10-26  9:48 ` Mattijs Korpershoek [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=xhkdbecdc3i7v.fsf@mkorpers-koolstof.csb \
    --to=mkorpershoek@kernel.org \
    --cc=francesco.dolcini@toradex.com \
    --cc=lukma@nabladev.com \
    --cc=mehmet.fide@gmail.com \
    --cc=mehmet.fide@screeningeagle.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.u-boot-project.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 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.