public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ravi Gunasekaran <r-gunasekaran@ti.com>
To: MD Danish Anwar <danishanwar@ti.com>,
	Sean Anderson <seanga2@gmail.com>, Qu Wenruo <wqu@suse.com>,
	Michal Simek <michal.simek@amd.com>,
	Simon Glass <sjg@chromium.org>, Stefan Roese <sr@denx.de>,
	Tom Rini <trini@konsulko.com>
Cc: <u-boot@lists.denx.de>, <srk@ti.com>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Roger Quadros <rogerq@kernel.org>
Subject: Re: [PATCH v4] misc: fs-loader: Use fw_storage_interface instead of storage_interface
Date: Fri, 2 Feb 2024 10:20:04 +0530	[thread overview]
Message-ID: <c563a375-7d45-409d-aa4a-3ca770168550@ti.com> (raw)
In-Reply-To: <20240130062627.2344282-1-danishanwar@ti.com>



On 1/30/2024 11:56 AM, MD Danish Anwar wrote:
> The fs-loader driver reads env storage_interface and uses it to load
> firmware file into memory using the medium set by env. Update the driver
> to use env fw_storage_interface as this variable is only used to load
> firmwares. The env storage_interface will act as fallback so that the
> existing implementations do not break.
>
> Also update the FS Loader documentation accordingly.
>
> Signed-off-by: MD Danish Anwar <danishanwar@ti.com>
> ---
> Changes from v3 to v4:
> *) No functional change. Splitted the patch out of the series as suggested
>    by Nishant.
> *) Droppped the RFC tag.
>
> v3: https://lore.kernel.org/all/20240124064930.1787929-3-danishanwar@ti.com/

Acked-by: Ravi Gunasekaran <r-gunasekaran@ti.com>

  reply	other threads:[~2024-02-02  4:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30  6:26 [PATCH v4] misc: fs-loader: Use fw_storage_interface instead of storage_interface MD Danish Anwar
2024-02-02  4:50 ` Ravi Gunasekaran [this message]
2024-02-07 17:44 ` Sean Anderson
2024-02-08  5:19   ` MD Danish Anwar
2024-02-08 11:58     ` Roger Quadros
2024-02-09  9:17       ` MD Danish Anwar

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=c563a375-7d45-409d-aa4a-3ca770168550@ti.com \
    --to=r-gunasekaran@ti.com \
    --cc=danishanwar@ti.com \
    --cc=michal.simek@amd.com \
    --cc=rogerq@kernel.org \
    --cc=seanga2@gmail.com \
    --cc=sjg@chromium.org \
    --cc=sr@denx.de \
    --cc=srk@ti.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=vigneshr@ti.com \
    --cc=wqu@suse.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