Age | Commit message (Collapse) | Author |
|
With only `sp_func_proto_paren = remove` set there are some cases where
uncrustify misses removing a space between the function name and the
opening '('. This sets all of the related options to `force` as well.
|
|
This is run with uncrustify 0.70.1, and black 19.10b0.
|
|
Also rename SEC_COUNT to BLOCK_COUNT and SEC_SIZE to BLOCK_SIZE.
|
|
|
|
|
|
|
|
Functionality is unchanged.
|
|
This patch eliminates heap allocation in the VFS FAT disk IO layer, when
calling the underlying readblocks/writeblocks methods. The bytearray
object that is passed to these methods is now allocated on the C stack
rather than the heap (it's only 4 words big).
This means that these methods should not retain a pointer to the buffer
object that is passed in, but this was already a restriction because the
original heap-allocated bytearray had its buffer passed by reference.
|
|
There were several different spellings of MicroPython present in comments,
when there should be only one.
|
|
Some ports may want to compile with generic MICROPY_VFS support but without
the VfsFat class. This patch allows such a thing.
|
|
vfs.h is for generic VFS declarations, and vfs_fat.h is for VfsFat
specific things.
|
|
Everyone should now be using the new ooFatFs library. The old one is no
longer supported and will be removed.
|
|
Replaced by MICROPY_VFS and the VFS sub-system.
|
|
The VfsFat object can now be mounted by the generic VFS sub-system.
|
|
If MICROPY_VFS_FAT is enabled by a port then the port must switch to using
MICROPY_FATFS_OO. Otherwise a port can continue to use the FatFs code
without any changes.
|
|
|
|
|