linux-kernel - Re: [PATCH] staging/vt6655: pointer to driver

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] [day] [month] [year] [list]

Message-ID: <20090704154252.GC5056@kroah.com>
Date:	Sat, 4 Jul 2009 08:42:52 -0700
From:	Greg KH <greg@...ah.com>
To:	Fernando Luis Vázquez Cao 
	<fernando@....ntt.co.jp>
Cc:	gregkh@...e.de,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] staging/vt6655: pointer to driver_data needs to be
 type long

On Fri, Jul 03, 2009 at 10:41:18AM +0900, Fernando Luis Vázquez Cao wrote:
> Greg KH wrote:
> > On Fri, Jun 26, 2009 at 11:12:12AM +0900, Fernando Luis Vázquez Cao wrote:
> >> Fix the compilation error below while at it.
> >>
> >> drivers/staging/vt6655/device_main.c:347: warning: cast from pointer to integer of different size
> >> drivers/staging/vt6655/device_main.c:347: error: initializer element is not constant
> >> drivers/staging/vt6655/device_main.c:347: error: (near initialization for ‘device_id_table[0].driver_data’)
> >>
> >> Signed-off-by: Fernando Luis Vazquez Cao <fernando@....ntt.co.jp>
> > 
> > This patch doesn't apply :(
> > 
> > Care to resync off of tomorrow's linux-next tree?
> 
> It seems that a patch from Alan Cox (linux-next: 38d257422fb010e11180fc9c5794812f390aca74)
> which fixes this issue got merged first, so mine is not needed anymore if you are planning
> to send the fix to Linus before the next merge window. What are your plans?

Ok, i'll stick with Alan's fix for now.

thanks,

greg k-h
--
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/