extmod: Use ARRAY_SIZE rather than sentinel
When the array gets down to size zero (which it does in later patches), gcc complains that the index is out of bounds. Avoid this by using ARRAY_SIZE on extensionModules instead. Signed-off-by: Daniel Stone <daniel@fooishbar.org> Reviewed-by: Stéphane Marchesin <stephane.marchesin@gmail.com> Signed-off-by: Keith Packard <keithp@keithp.com>
This commit is contained in:
parent
d35884da2f
commit
f48d8f58b3
|
@ -101,12 +101,6 @@ static ExtensionModule extensionModules[] = {
|
|||
NULL,
|
||||
NULL},
|
||||
#endif
|
||||
{ /* DON'T delete this entry ! */
|
||||
NULL,
|
||||
NULL,
|
||||
NULL,
|
||||
NULL,
|
||||
NULL}
|
||||
};
|
||||
|
||||
static XF86ModuleVersionInfo VersRec = {
|
||||
|
@ -134,7 +128,7 @@ extmodSetup(pointer module, pointer opts, int *errmaj, int *errmin)
|
|||
|
||||
/* XXX the option stuff here is largely a sample/test case */
|
||||
|
||||
for (i = 0; extensionModules[i].name != NULL; i++) {
|
||||
for (i = 0; i < ARRAY_SIZE(extensionModules); i++) {
|
||||
#ifdef XSELINUX
|
||||
if (!strcmp(SELINUX_EXTENSION_NAME, extensionModules[i].name)) {
|
||||
pointer o;
|
||||
|
|
Loading…
Reference in New Issue