linux-kernel - Re: [PATCH] [media] lnbh25: fix lnbh25

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CABxcv=n_N-176+iOsBaroJoGy0kj35YELyfLnaXJGmsi9xkDOg@mail.gmail.com>
Date:	Fri, 16 Oct 2015 23:45:46 +0200
From:	Javier Martinez Canillas <javier@...hile0.org>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Mauro Carvalho Chehab <mchehab@....samsung.com>,
	Linux Media Mailing List <linux-media@...r.kernel.org>,
	Sergey Kozlov <serjk@...up.ru>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] [media] lnbh25: fix lnbh25_attach inline wrapper

Hello Arnd,

On Fri, Oct 16, 2015 at 10:32 PM, Arnd Bergmann <arnd@...db.de> wrote:
> The 'static inline' version of lnbh25_attach() has an incorrect
> prototype which results in a build error when
> CONFIG_DVB_LNBH25 is disabled:
>
> In file included from /git/arm-soc/drivers/media/pci/netup_unidvb/netup_unidvb_core.c:36:0:
> /git/arm-soc/drivers/media/dvb-frontends/lnbh25.h:46:86: error: unknown type name 'dvb_frontend'
>
> This changes the code to have the correct prototype.
>
> Signed-off-by: Arnd Bergmann <arnd@...db.de>
> Fixes: e025273b86fb ("[media] lnbh25: LNBH25 SEC controller driver")
> ---

Same for this patch, the same change is already in the media fixes branch [0].

[0]: http://git.linuxtv.org/cgit.cgi/media_tree.git/commit/?h=fixes&id=b36a55cf298127a285806c52d8777c49548f3785

Best regards,
Javier
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/