The patch titled misdn: one handmade ARRAY_SIZE converted has been added to the -mm tree. Its filename is misdn-one-handmade-array_size-converted.patch Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/SubmitChecklist when testing your code *** See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find out what to do about this The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: misdn: one handmade ARRAY_SIZE converted From: Ilpo Järvinen <ilpo.jarvinen@xxxxxxxxxxx> Defined as: static struct device_attribute element_attributes[] = { Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@xxxxxxxxxxx> Cc: Karsten Keil <kkeil@xxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/isdn/mISDN/dsp_pipeline.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff -puN drivers/isdn/mISDN/dsp_pipeline.c~misdn-one-handmade-array_size-converted drivers/isdn/mISDN/dsp_pipeline.c --- a/drivers/isdn/mISDN/dsp_pipeline.c~misdn-one-handmade-array_size-converted +++ a/drivers/isdn/mISDN/dsp_pipeline.c @@ -99,8 +99,7 @@ int mISDN_dsp_element_register(struct mI goto err1; } - for (i = 0; i < (sizeof(element_attributes) - / sizeof(struct device_attribute)); ++i) + for (i = 0; i < ARRAY_SIZE(element_attributes); ++i) ret = device_create_file(&entry->dev, &element_attributes[i]); if (ret) { _ Patches currently in -mm which might be from ilpo.jarvinen@xxxxxxxxxxx are linux-next.patch consolemap-indentation-braces-disagree-reindent.patch misdn-indentation-braces-disagree-add-braces.patch misdn-one-handmade-array_size-converted.patch misdn-indentation-and-braces-disagree-add-braces.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html