diff options
| author | Bruce Ashfield <bruce.ashfield@windriver.com> | 2015-12-11 13:30:10 -0500 | 
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2015-12-28 09:25:16 +0000 | 
| commit | 9563aa8a2577a4942b3d5df3ece0ab6c6d03237d (patch) | |
| tree | 9292564355036725efef41d7883ca18b8ebb5a72 /scripts/lib/devtool/sdk.py | |
| parent | cefc24d6af3feee77a03fead47888bdb8cbfa9c3 (diff) | |
| download | poky-9563aa8a2577a4942b3d5df3ece0ab6c6d03237d.tar.gz | |
yaffs2: fix checkpoint functionality
Updating the linux-yocto SRCREVs to pull in the following change:
  Author: He Zhe <zhe.he@windriver.com>
  Date:   Wed Dec 2 01:31:31 2015 -0500
    fs/yaffs2: fix missing checkpoint on yaffs
    For yaffs file system, the mode of reading or writing is restricted
    at four pointer where are mnt->mnt_flags,mnt->mnt_sb->s_flags,mtd->flags and
    dev->read_only,the first three is used handle file and file
    system(eg,remount) operation, and last one(dev->read_only) almost is
    used handle checkpoint of yaffs2. However, in current code, the
    dev->read_only only can be changed at first time when the yaffs2
    file system is mounted, later it can't be changed again(eg,mount -o
    remount), the result is that the checkpoint's saving operation
    always can't succeed if you set readonly mode for yaffs2 file system
    when it is mounted at the first time.
    To fix this issue, we implement yaffs_remount_fs() which allows the
    rootfs to be remounted as r/w.
    Signed-off-by: Wenlin Kang <wenlin.kang@windriver.com>
    Signed-off-by: He Zhe <zhe.he@windriver.com>
    Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
(From OE-Core rev: 289fd2bf61d0761a93d17f18b9079fc9f61e0031)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts/lib/devtool/sdk.py')
0 files changed, 0 insertions, 0 deletions
