mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@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: Tue, 4 Mar 2025 18:39:56 +0100	[thread overview]
Message-ID: <9f921a53-df29-4e7c-93e1-444b1068dd35@pengutronix.de> (raw)
In-Reply-To: <QH1MSS.NEOFAGTU4XUA1@gmail.com>

On 04.03.25 18:49, Stefano Manni wrote:
> 
> 
> Hello Ahmad,
> 
> On lun, mar 3 2025 at 09:41:53 +01:00:00, Ahmad Fatoum <a.fatoum@pengutronix.de> wrote:
>> On 24.02.25 16:49, Stefano Manni wrote:
>>>  Hello Ahmad,
>>>
>>>  On ven, feb 21 2025 at 18:33:04 +01:00:00, Ahmad Fatoum <a.fatoum@pengutronix.de> wrote:
>>>>  Hello Stefano,
>>>>
>>>>  On 21.02.25 19:01, Stefano Manni wrote:
>>>>>   Device file was hardcoded to "nand0.barebox".
>>>>>   This patch harmonize the signature of
>>>>>
>>>>>   imx6_bbu_nand_register_handler()
>>>>>   imx7_bbu_nand_register_handler()
>>>>>   imx28_bbu_nand_register_handler()
>>>>>
>>>>>   with the other bbu register functions in order to take
>>>>>   the devicefile as parameter.
>>>>
>>>>  Is this this the sole motivation behind the patch or do you
>>>>  intend to actually make use of the ability of varying
>>>>  the devicefile?
>>>
>>>  my purpose is to let people use a device/partition different from the hardcoded one.
>>
>> Can you have multiple NANDs? But yes, customizing partition name can
>> be useful.
>>
> 
> for sure I cannot have multiple NANDs but I can have a different partition name.
> 
> Anyway drop the patch if you consider it not necessary.

I think the patch is ok.

Cheers,
Ahmad

> 
> Best,
> Stefano
> 
>> Thanks,
>> Ahmad
> 
> 
> 


-- 
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 |



  reply	other threads:[~2025-03-04 20:15 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 [this message]
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
  -- 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=9f921a53-df29-4e7c-93e1-444b1068dd35@pengutronix.de \
    --to=a.fatoum@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