| 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
| ||
|
Date: Thu, 24 Feb 2011 16:43:42 -0800 From: Greg KH <gregkh@...e.de> To: Belisko Marek <marek.belisko@...il.com> Cc: alan@...ux.intel.com, devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] staging: gma500: Fix compilation error. On Thu, Feb 24, 2011 at 08:58:52PM +0100, Belisko Marek wrote: > Hi Greg, > > On Thu, Feb 24, 2011 at 6:12 PM, Greg KH <gregkh@...e.de> wrote: > > On Thu, Feb 24, 2011 at 10:33:18AM +0100, Marek Belisko wrote: > >> This patch will fix following compilation error: > >> drivers/staging/gma500/psb_drv.c:1635: error: unknown field ‘pci_driver’ specified in initializer > >> drivers/staging/gma500/psb_drv.c:1636: error: unknown field ‘name’ specified in initializer > >> drivers/staging/gma500/psb_drv.c:1636: warning: initialization from incompatible pointer type > >> drivers/staging/gma500/psb_drv.c:1637: error: unknown field ‘id_table’ specified in initializer > >> drivers/staging/gma500/psb_drv.c:1637: warning: excess elements in union initializer > >> drivers/staging/gma500/psb_drv.c:1637: warning: (near initialization for ‘driver.kdriver’) > >> drivers/staging/gma500/psb_drv.c:1638: error: unknown field ‘resume’ specified in initializer > >> drivers/staging/gma500/psb_drv.c:1638: warning: excess elements in union initializer > >> drivers/staging/gma500/psb_drv.c:1638: warning: (near initialization for ‘driver.kdriver’) > >> drivers/staging/gma500/psb_drv.c:1639: error: unknown field ‘suspend’ specified in initializer > >> drivers/staging/gma500/psb_drv.c:1639: warning: excess elements in union initializer > >> drivers/staging/gma500/psb_drv.c:1639: warning: (near initialization for ‘driver.kdriver’) > >> drivers/staging/gma500/psb_drv.c:1640: error: unknown field ‘probe’ specified in initializer > >> drivers/staging/gma500/psb_drv.c:1640: warning: excess elements in union initializer > >> drivers/staging/gma500/psb_drv.c:1640: warning: (near initialization for ‘driver.kdriver’) > >> drivers/staging/gma500/psb_drv.c:1641: error: unknown field ‘remove’ specified in initializer > >> drivers/staging/gma500/psb_drv.c:1641: warning: excess elements in union initializer > >> drivers/staging/gma500/psb_drv.c:1641: warning: (near initialization for ‘driver.kdriver’) > >> drivers/staging/gma500/psb_drv.c:1643: error: unknown field ‘driver’ specified in initializer > >> drivers/staging/gma500/psb_drv.c:1643: warning: excess elements in union initializer > >> drivers/staging/gma500/psb_drv.c:1643: warning: (near initialization for ‘driver.kdriver’) > >> drivers/staging/gma500/psb_drv.c: In function ‘psb_init’: > >> drivers/staging/gma500/psb_drv.c:1664: error: implicit declaration of function ‘drm_init’ > >> drivers/staging/gma500/psb_drv.c: In function ‘psb_exit’: > >> drivers/staging/gma500/psb_drv.c:1669: error: implicit declaration of function ‘drm_exit’ > >> > >> Signed-off-by: Marek Belisko <marek.belisko@...n-nandra.com> > > > > Odd, how come I'm not hitting these in the staging-next tree? Is it > > because an api changed in the DRM layer in the linux-next tree? > Yes DRM api was changed: > commit 8410ea3b95d105a5be5db501656f44bbb91197c1 > Author: Dave Airlie <airlied@...il.com> > Date: Wed Dec 15 03:16:38 2010 +1000 > > drm: rework PCI/platform driver interface. > > Introduce union kdriver which encapsulate pci_driver struct. > That's cause of error in gma500. Ok, this is going to get messy then, this patch should be held by Stephen in linux-next until we merge stuff with Linus, and then I'll be able to apply it to my tree. So I'll just save it in my queue until that time happens, 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/
Powered by blists - more mailing lists