From: Sascha Hauer <sha@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH RFT] blspec: support boot /dev/disk0.rootfs to mean boot disk0.rootfs
Date: Mon, 26 Jun 2023 12:01:38 +0200 [thread overview]
Message-ID: <20230626100138.GX18491@pengutronix.de> (raw)
In-Reply-To: <20230619143742.1698346-1-a.fatoum@pengutronix.de>
On Mon, Jun 19, 2023 at 04:37:42PM +0200, Ahmad Fatoum wrote:
> boot /dev/disk0.rootfs would always fail:
>
> Nothing bootable found on '/dev/disk0.rootfs'
> Nothing bootable found
>
> boot /mnt/disk0.rootfs and boot disk0.rootfs would however work.
> This can be surprising to users, so just skip over /dev if supplied.
>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> I am not sure why this wasn't the case before. Any ambiguity in doing it
> this way? Change still needs to be tested.
> ---
> common/blspec.c | 3 +++
> 1 file changed, 3 insertions(+)
Applied, thanks
Sascha
>
> diff --git a/common/blspec.c b/common/blspec.c
> index 8c7970da8915..b70332a54c28 100644
> --- a/common/blspec.c
> +++ b/common/blspec.c
> @@ -782,6 +782,9 @@ int blspec_scan_devicename(struct bootentries *bootentries, const char *devname)
>
> pr_debug("%s: %s\n", __func__, devname);
>
> + /* Support both boot /dev/disk0.rootfs and boot disk0.rootfs */
> + devname += str_has_prefix(devname, "/dev/");
> +
> device_detect_by_name(devname);
>
> cdev = cdev_by_name(devname);
> --
> 2.39.2
>
>
>
--
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 |
prev parent reply other threads:[~2023-06-26 10:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 14:37 Ahmad Fatoum
2023-06-19 15:08 ` Marco Felsch
2023-06-19 15:14 ` Ahmad Fatoum
2023-06-26 10:01 ` 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=20230626100138.GX18491@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