From: Sascha Hauer <s.hauer@pengutronix.de>
To: Stefano Manni <stefano.manni@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/2] imx-bbu-nand-fcb: do not use hardcoded devicefile
Date: Wed, 5 Mar 2025 12:14:47 +0100 [thread overview]
Message-ID: <Z8gyJ2_jXp12dhz1@pengutronix.de> (raw)
In-Reply-To: <20250221180109.14129-1-stefano.manni@gmail.com>
Hi Stefano,
I merged both patches into one to avoid intermediate breakage.
On Fri, Feb 21, 2025 at 07:01:08PM +0100, Stefano Manni wrote:
> @@ -1599,7 +1607,8 @@ static int imx7_fcb_write(struct mtd_info *mtd, int block, struct fcb_block *fcb
> return mxs_nand_write_fcb_bch62(block, fcb, sizeof(*fcb));
> }
>
> -int imx7_bbu_nand_register_handler(const char *name, unsigned long flags)
> +int imx7_bbu_nand_register_handler(const char *name
> + const char *devicefile, unsigned long flags)
> {
Also added the missing comma after *name
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 |
next prev parent reply other threads:[~2025-03-05 12:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 18:01 Stefano Manni
2025-02-21 17:33 ` Ahmad Fatoum
2025-02-24 15:49 ` Stefano Manni
2025-03-03 8:41 ` Ahmad Fatoum
2025-03-04 17:49 ` Stefano Manni
2025-03-04 17:39 ` Ahmad Fatoum
2025-02-21 18:01 ` [PATCH 2/2] ARM: boards: fix nand bbu_handler device paths Stefano Manni
2025-03-05 11:13 ` [PATCH 1/2] imx-bbu-nand-fcb: do not use hardcoded devicefile Sascha Hauer
2025-03-05 11:14 ` Sascha Hauer [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-20 17:39 Stefano Manni
2025-02-21 10:38 ` Sascha Hauer
2025-02-21 17:47 ` Stefano Manni
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=Z8gyJ2_jXp12dhz1@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=stefano.manni@gmail.com \
/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