mirror of
https://mirrors.bfsu.edu.cn/git/linux.git
synced 2024-11-11 21:38:32 +08:00
UBI: add few more comments
Add few comments above ubi_scan_add_used() to explain why it is so complex. Requested by Satyam Sharma <satyam.sharma@gmail.com>. Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
This commit is contained in:
parent
941dfb07ed
commit
79b510c0f2
@ -407,8 +407,12 @@ out_free_vidh:
|
||||
* @vid_hdr: the volume identifier header
|
||||
* @bitflips: if bit-flips were detected when this physical eraseblock was read
|
||||
*
|
||||
* This function returns zero in case of success and a negative error code in
|
||||
* case of failure.
|
||||
* This function adds information about a used physical eraseblock to the
|
||||
* 'used' tree of the corresponding volume. The function is rather complex
|
||||
* because it has to handle cases when this is not the first physical
|
||||
* eraseblock belonging to the same logical eraseblock, and the newer one has
|
||||
* to be picked, while the older one has to be dropped. This function returns
|
||||
* zero in case of success and a negative error code in case of failure.
|
||||
*/
|
||||
int ubi_scan_add_used(const struct ubi_device *ubi, struct ubi_scan_info *si,
|
||||
int pnum, int ec, const struct ubi_vid_hdr *vid_hdr,
|
||||
|
Loading…
Reference in New Issue
Block a user