| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: I7a4b1caadfe499d2394c8645e45903759b672e8b
|
|
|
|
|
| |
Change-Id: If943fe6b46a8261ca936e07a36e11c10c7e6d63a
Signed-off-by: Sasha Levitskiy <sanek@google.com>
|
|
|
|
|
|
|
| |
match confidence.
Change-Id: I62ce57054b7e0cfda8aa260176e504113677d993
Signed-off-by: Sasha Levitskiy <sanek@google.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Inheritance of HAL object is performed by composing a child structure of a
single parent structure located at offset 0 followed by new data members
and function pointers in the child structure.
For example,
struct child {
struct parent common;
int a_data_member;
void (*a_method)(struct child *c, int v);
};
HAL code assumes this layout when accessing child structures given a pointer
to a parent structure such that users write code like the following...
void child_method(struct *parent, int v) {
struct child * c = (struct child*)parent;
// do stuff with c
}
Code above will break if a member is added before "common" in "struct child".
This change adds comments that describe the restriction on the location of
parent HAL objects within a derived HAL object. HAL objects that already
have comments that describe the required location of parent objects are not
modified.
Change-Id: Ibe4300275286ef275b2097534c84f1029d761d87
|
|
|
|
|
| |
Change-Id: Id0a8e120043c00bf351aa1c9d3f0c06c2e4af947
Signed-off-by: Sasha Levitskiy <sanek@google.com>
|
|
|
|
|
| |
Change-Id: I7a2593837148ad80df970d89950f396c7704e71b
Signed-off-by: Sasha Levitskiy <sanek@google.com>
|
|
|
|
|
| |
Change-Id: I99e8e2f24f0264c2217d67a75fe437756596053c
Signed-off-by: Sasha Levitskiy <sanek@google.com>
|
|
|
|
|
|
|
| |
requested functionality.
Change-Id: Ib99e3edb99579ac4495918eb57d1022d75dccb57
Signed-off-by: Sasha Levitskiy <sanek@google.com>
|
|
Change-Id: I4e55c42841c3b6a1327a16bdf6d1d4bb3847c7f3
Signed-off-by: Sasha Levitskiy <sanek@google.com>
|