diff options
| author | Simon Glass <sjg@chromium.org> | 2023-07-30 20:15:14 +0300 |
|---|---|---|
| committer | Bin Meng <bmeng.cn@gmail.com> | 2023-08-09 18:31:11 +0300 |
| commit | d7d78576bbfddd52b258771c9e926bd51b50d91e (patch) | |
| tree | cd0573b8fd3aba0c05d9a2e509716029740dee4b /doc | |
| parent | 3a3543db519478cd174e4554691f3d4828902c79 (diff) | |
| download | u-boot-d7d78576bbfddd52b258771c9e926bd51b50d91e.tar.xz | |
bootstd: Rename bootdev_setup_sibling_blk()
This name is a little confusing since it suggests that it sets up the
sibling block device. In fact it sets up a bootdev for it. Rename the
function to make this clearer.
Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/develop/bootstd.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/develop/bootstd.rst b/doc/develop/bootstd.rst index 7a2a69fdfc..ec31365357 100644 --- a/doc/develop/bootstd.rst +++ b/doc/develop/bootstd.rst @@ -306,7 +306,7 @@ media device:: The bootdev device is typically created automatically in the media uclass' `post_bind()` method by calling `bootdev_setup_for_dev()` or -`bootdev_setup_sibling_blk()`. The code typically something like this:: +`bootdev_setup_for_sibling_blk()`. The code typically something like this:: /* dev is the Ethernet device */ ret = bootdev_setup_for_dev(dev, "eth_bootdev"); @@ -316,7 +316,7 @@ The bootdev device is typically created automatically in the media uclass' or:: /* blk is the block device (child of MMC device) - ret = bootdev_setup_sibling_blk(blk, "mmc_bootdev"); + ret = bootdev_setup_for_sibling_blk(blk, "mmc_bootdev"); if (ret) return log_msg_ret("bootdev", ret); |