mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: "Uwe Kleine-König" <uwe@kleine-koenig.org>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH master] partition: fix reference to wrong cdev in warning message
Date: Tue, 18 Mar 2025 12:23:19 +0100	[thread overview]
Message-ID: <f66973ec-4516-4dd3-92d3-214fab6c035e@pengutronix.de> (raw)
In-Reply-To: <p6sahp32nei5iesre27rbtdbsatui24ce53f3fx6sovbe2mis7@lkei2stdndjo>

Hello Uwe,

On 3/18/25 12:16, Uwe Kleine-König wrote:
> This improves the error messages on my ts433 from
> 
> 	WARNING: mmc0: Failed to create link from mmc0.primary to mmc0
> 	WARNING: mmc0: Failed to create link from mmc0.primary to mmc0
> 	WARNING: mmc0: Failed to create link from mmc0.primary to mmc0
> 	WARNING: mmc0: Failed to create link from mmc0.primary to mmc0
> 	WARNING: mmc0: Failed to create link from mmc0.primary to mmc0
> 
> to 
> 
> 	WARNING: mmc0: Failed to create link from mmc0.primary to mmc0.2
> 	WARNING: mmc0: Failed to create link from mmc0.primary to mmc0.3
> 	WARNING: mmc0: Failed to create link from mmc0.primary to mmc0.4
> 	WARNING: mmc0: Failed to create link from mmc0.primary to mmc0.5
> 	WARNING: mmc0: Failed to create link from mmc0.primary to mmc0.6
> 
> I still don't understand why barebox intends to create mmc0.primary for
> all these partitions, but still it's an obviously right improvement.

Thanks for testing. I still suspect that you have multiple on-disk
partitions with the same label. What does lsblk -o name,label,partlabel
say?

Cheers,
Ahmad

> 
> Acked-by: Uwe Kleine-König <uwe@kleine-koenig.org>
> 
> Best regards and thanks
> Uwe




  reply	other threads:[~2025-03-18 11:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-18  8:24 Ahmad Fatoum
2025-03-18 10:22 ` Sascha Hauer
2025-03-18 11:16 ` Uwe Kleine-König
2025-03-18 11:23   ` Ahmad Fatoum [this message]
2025-03-18 11:31     ` Uwe Kleine-König

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=f66973ec-4516-4dd3-92d3-214fab6c035e@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=uwe@kleine-koenig.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