The patch titled git-alsa-tiwai: sound/drivers/pcsp/pcsp.c build fix has been added to the -mm tree. Its filename is git-alsa-tiwai-sound-drivers-pcsp-pcspc-build-fix.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://www.zip.com.au/~akpm/linux/patches/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: git-alsa-tiwai: sound/drivers/pcsp/pcsp.c build fix From: Mariusz Kozlowski <m.kozlowski@xxxxxxxxxx> sound/drivers/pcsp/pcsp.c: In function 'snd_pcsp_create': sound/drivers/pcsp/pcsp.c:54: error: 'loops_per_jiffy' undeclared (first use in this function) sound/drivers/pcsp/pcsp.c:54: error: (Each undeclared identifier is reported only once sound/drivers/pcsp/pcsp.c:54: error: for each function it appears in.) Signed-off-by: Mariusz Kozlowski <m.kozlowski@xxxxxxxxxx> Cc: Jaroslav Kysela <perex@xxxxxxxx> Cc: Takashi Iwai <tiwai@xxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- sound/drivers/pcsp/pcsp.c | 1 + 1 file changed, 1 insertion(+) diff -puN sound/drivers/pcsp/pcsp.c~git-alsa-tiwai-sound-drivers-pcsp-pcspc-build-fix sound/drivers/pcsp/pcsp.c --- a/sound/drivers/pcsp/pcsp.c~git-alsa-tiwai-sound-drivers-pcsp-pcspc-build-fix +++ a/sound/drivers/pcsp/pcsp.c @@ -12,6 +12,7 @@ #include <sound/initval.h> #include <sound/pcm.h> #include <linux/input.h> +#include <linux/delay.h> #include <asm/bitops.h> #include "pcsp_input.h" #include "pcsp.h" _ Patches currently in -mm which might be from m.kozlowski@xxxxxxxxxx are git-alsa-tiwai-sound-drivers-pcsp-pcspc-build-fix.patch reiser4.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