On Fri, Dec 09, 2022 at 03:23:10PM +0100, Sergei Shtepa wrote: > Sergei Shtepa (21): > documentation, blkfilter: Block Device Filtering Mechanism > block, blkfilter: Block Device Filtering Mechanism > documentation, capability: fix Generic Block Device Capability > documentation, blksnap: Block Devices Snapshots Module > block, blksnap: header file of the module interface > block, blksnap: module management interface functions > block, blksnap: init() and exit() functions > block, blksnap: interaction with sysfs > block, blksnap: attaching and detaching the filter and handling I/O > units > block, blksnap: map of change block tracking > block, blksnap: minimum data storage unit of the original block device > block, blksnap: buffer in memory for the minimum data storage unit > block, blksnap: functions and structures for performing block I/O > operations > block, blksnap: storage for storing difference blocks > block, blksnap: event queue from the difference storage > block, blksnap: owner of information about overwritten blocks of the > original block device > block, blksnap: snapshot image block device > block, blksnap: snapshot > block, blksnap: Kconfig and Makefile > block, blksnap: adds a blksnap to the kernel tree > block, blksnap: adds a maintainer for new files > Per convention in block subsystem (see for example `git log --no-merges -- drivers/block/`), the patch subject prefix should looks like "block component: some patch" (e.g. "blksnap: do something"). Thanks. -- An old man doll... just what I always wanted! - Clara
Attachment:
signature.asc
Description: PGP signature
