Searched hist:"9 e0e252a" (Results 1 – 3 of 3) sorted by relevance
/openbmc/linux/block/ |
H A D | badblocks.c | 9e0e252a Thu Dec 24 20:20:32 CST 2015 Vishal Verma <vishal.l.verma@intel.com> badblocks: Add core badblock management code
Take the core badblocks implementation from md, and make it generally available. This follows the same style as kernel implementations of linked lists, rb-trees etc, where you can have a structure that can be embedded anywhere, and accessor functions to manipulate the data.
The only changes in this copy of the code are ones to generalize function/variable names from md-specific ones. Also add init and free functions.
Signed-off-by: Vishal Verma <vishal.l.verma@intel.com> Signed-off-by: Dan Williams <dan.j.williams@intel.com> 9e0e252a Thu Dec 24 20:20:32 CST 2015 Vishal Verma <vishal.l.verma@intel.com> badblocks: Add core badblock management code Take the core badblocks implementation from md, and make it generally available. This follows the same style as kernel implementations of linked lists, rb-trees etc, where you can have a structure that can be embedded anywhere, and accessor functions to manipulate the data. The only changes in this copy of the code are ones to generalize function/variable names from md-specific ones. Also add init and free functions. Signed-off-by: Vishal Verma <vishal.l.verma@intel.com> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
|
H A D | Makefile | 9e0e252a Thu Dec 24 20:20:32 CST 2015 Vishal Verma <vishal.l.verma@intel.com> badblocks: Add core badblock management code
Take the core badblocks implementation from md, and make it generally available. This follows the same style as kernel implementations of linked lists, rb-trees etc, where you can have a structure that can be embedded anywhere, and accessor functions to manipulate the data.
The only changes in this copy of the code are ones to generalize function/variable names from md-specific ones. Also add init and free functions.
Signed-off-by: Vishal Verma <vishal.l.verma@intel.com> Signed-off-by: Dan Williams <dan.j.williams@intel.com> 9e0e252a Thu Dec 24 20:20:32 CST 2015 Vishal Verma <vishal.l.verma@intel.com> badblocks: Add core badblock management code Take the core badblocks implementation from md, and make it generally available. This follows the same style as kernel implementations of linked lists, rb-trees etc, where you can have a structure that can be embedded anywhere, and accessor functions to manipulate the data. The only changes in this copy of the code are ones to generalize function/variable names from md-specific ones. Also add init and free functions. Signed-off-by: Vishal Verma <vishal.l.verma@intel.com> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
|
/openbmc/linux/include/linux/ |
H A D | badblocks.h | 9e0e252a Thu Dec 24 20:20:32 CST 2015 Vishal Verma <vishal.l.verma@intel.com> badblocks: Add core badblock management code
Take the core badblocks implementation from md, and make it generally available. This follows the same style as kernel implementations of linked lists, rb-trees etc, where you can have a structure that can be embedded anywhere, and accessor functions to manipulate the data.
The only changes in this copy of the code are ones to generalize function/variable names from md-specific ones. Also add init and free functions.
Signed-off-by: Vishal Verma <vishal.l.verma@intel.com> Signed-off-by: Dan Williams <dan.j.williams@intel.com> 9e0e252a Thu Dec 24 20:20:32 CST 2015 Vishal Verma <vishal.l.verma@intel.com> badblocks: Add core badblock management code Take the core badblocks implementation from md, and make it generally available. This follows the same style as kernel implementations of linked lists, rb-trees etc, where you can have a structure that can be embedded anywhere, and accessor functions to manipulate the data. The only changes in this copy of the code are ones to generalize function/variable names from md-specific ones. Also add init and free functions. Signed-off-by: Vishal Verma <vishal.l.verma@intel.com> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
|