linux-kernel - Re: [patch] drivers/media/video/zoran

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]

Date:	Sun, 27 Jan 2008 14:39:03 -0500
From:	"Ronald S. Bultje" <rbultje@...ald.bitfreak.net>
To:	LKML <linux-kernel@...r.kernel.org>
Cc:	"Martin Samuelsson" <sam.linux.kernel@...il.com>
Subject: Re: [patch] drivers/media/video/zoran_card.c: en/decoder loading

Hi,

On Jan 27, 2008 1:01 PM, Martin Samuelsson <sam.linux.kernel@...il.com> wrote:
> This enables the avs6eyes to load the bt866 and ks0127 drivers automatically.
>
> Signed-off-by: Martin Samuelsson <sam.linux.kernel@...il.com>
> ---
>  zoran_card.c |    6 ++++++
>  1 file changed, 6 insertions(+)
> --- linux-2.6.24-ori/drivers/media/video/zoran_card.c   2008-01-24 23:58:37.000000000 +0100
> +++ linux-2.6.24-sam/drivers/media/video/zoran_card.c   2008-01-27 17:16:51.000000000 +0100
> @@ -366,6 +366,12 @@ i2cid_to_modulename (u16 i2c_id)
>        case I2C_DRIVERID_MSE3000:
>                name = "mse3000";
>                break;*/
> +       case I2C_DRIVERID_BT866:
> +               name = "bt866";
> +               break;
> +       case I2C_DRIVERID_KS0127:
> +               name = "ks0127";
> +               break;
>        default:
>                break;
>        }

(For upstream people who will apply the patch in mainstream kernel:)
ack from maintainer.

Ronald

(and sorry to Martin for getting this msg twice.)
--
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/