办理纸箱证，产地证，买单报关

ÄúºÃ:רҵ°ìÀíÖ½ÏäÖ¤,µÆÊÎÖ½ÏäÖ¤,µç³ØÖ½ÏäÖ¤,²úµØÖ¤,½ø³ö¿Ú±¨¹Ø,ºËÏúµ¥µÈÒµÎñ,»¶Ó­×Éѯ¡£ÕÅÏÈÉú:13824390642 Áõ*С*½ã:13510682636 µç»°:0755-25412065QQ 774386269 136058366 ÉîÛÚÊнðÓî»Ô½ø³ö¿ÚóÒ×ÓÐÏÞ¹«Ë¾ ___ devel mailing list devel@linuxdriverproject.o

Re: [PATCH] bcb: Android bootloader control block driver

> > Other boards (don't have a specific example here, perhaps Andrew can > provide one) need to store the reboot reason on disk. For this case, I'm trying to get the alternate boot logic to work on PC compatible devices. I have a patch against SYSLINUX which reads this area and selects an alter

RE: [PATCH net,1/1] hyperv: Add support for setting MAC from within guests

> -Original Message- > From: Ben Hutchings [mailto:bhutchi...@solarflare.com] > Sent: Friday, July 06, 2012 8:19 PM > To: Haiyang Zhang > Cc: da...@davemloft.net; net...@vger.kernel.org; KY Srinivasan; > o...@aepfle.de; linux-ker...@vger.kernel.org; devel@linuxdriverproject.org > Subject:

Re: [PATCH] bcb: Android bootloader control block driver

On Sat, Jul 7, 2012 at 4:05 PM, Greg KH wrote: > On Sat, Jul 07, 2012 at 03:39:09PM -0700, Colin Cross wrote: >> On many (most?) ARM SoCs, the reboot flag is not stored on disk, or >> anywhere else userspace can access. It is stored in a power >> management controller scratch register that surviv

Re: [PATCH] bcb: Android bootloader control block driver

On Sat, Jul 07, 2012 at 03:39:09PM -0700, Colin Cross wrote: > On many (most?) ARM SoCs, the reboot flag is not stored on disk, or > anywhere else userspace can access. It is stored in a power > management controller scratch register that survives resets, or a > register in an external I2C PMIC, o

Re: [PATCH] bcb: Android bootloader control block driver

On Sun, Jul 1, 2012 at 5:10 PM, NeilBrown wrote: > On Fri, 29 Jun 2012 21:37:36 -0700 Colin Cross wrote: > >> What's the point of the existing syscall option if it doesn't work on >> all platforms, or at least all platforms that want to support it? It >> doesn't make sense to me to use REBOOT2 o

Can We Work Together ?

Hi, This is Akar Sova a native of israel,can we work and share this project together.If interested get email back for more details to.(akars...@israelmail.com) ___ devel mailing list devel@linuxdriverproject.org http://driverdev.linuxdriverproject.or

[PATCH] lirc: fix non-ANSI function declaration warning

Sparse is warning about non-ANSI function declaration. Add void to the parameterless function. drivers/staging/media/lirc/lirc_bt829.c:174:22: warning: non-ANSI function declaration of function 'poll_main' Signed-off-by: Emil Goode --- drivers/staging/media/lirc/lirc_bt829.c |2 +-

[PATCH] CSR: fix function declaration warnings

Sparse is warning about non-ANSI function declaration. Add void to the parameterless function. drivers/staging/csr/csr_wifi_hip_chiphelper.c:633:31: warning: non-ANSI function declaration of function 'ChipHelper_Null' I also fixed this checkpatch error: ERROR: "foo* bar" should be "foo *b

LOAN!!

Do you need 100% Finance? I am Ms.Jonna Tim ,a financial lender and consultant, CEO Of PRIVATE MONEY GROUP. We are coorporate lenders in United States of America/Europe/Asia/Canada/Australia. I can service your financial need with less payback problem that is why we fund you for just 2%. Whateve

[staging:staging-next 54/100] WARNING: drivers/iio/dac/ad5064.o(.init.text+0x72): Section mismatch in reference from the function init_module() to the function .exit.text:ad5064_spi_unregister_driver(

Hi Lars-Peter, There are new compile warnings show up in tree: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git staging-next head: 0932966b1ca03217c6e0c18375867b1a99ee5af0 commit: 6a17a0768f77626046aa441843b318a00bac3800 [54/100] iio:dac:ad5064: Add support for the ad5629r a

[PATCH] Staging: nvec: fix coding style issues

From: Adnan Ali This commit fixes coding style issues that includes long lines. Cc: Adnan Ali Signed-off-by: Marc Dietrich --- Adnan didn't replied to my request to rebase and resubmit. So I'm sending it here again. --- drivers/staging/nvec/nvec.c |6 -- 1 file changed, 4 insertions(

[PATCH 7/8] staging/ft1000-pcmcia: fix checkpatch warnings

The below checkpatch warns fixed, drivers/staging/ft1000/ft1000-pcmcia/ft1000_proc.c:38: ERROR: that open brace { should be on the previous line drivers/staging/ft1000/ft1000-pcmcia/ft1000_proc.c:45: ERROR: that open brace { should be on the previous line drivers/staging/ft1000/ft1000-pcmcia/ft1

[PATCH 8/8] staging/ft1000: remove unnecessary assignment of ret with STATUS_SUCCESS

as ret is assigned to the return of ft1000_poll, we dont need to initialise ret with STATUS_SUCCESS. Signed-off-by: Devendra Naga --- drivers/staging/ft1000/ft1000-usb/ft1000_usb.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/ft1000/ft1000-usb/ft1000_usb

[PATCH 6/8] staging/ft1000: fix the foo * bar warning

Signed-off-by: Devendra Naga --- drivers/staging/ft1000/ft1000-pcmcia/ft1000_hw.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/ft1000/ft1000-pcmcia/ft1000_hw.c b/drivers/staging/ft1000/ft1000-pcmcia/ft1000_hw.c index 67ad7ee..9a5ba07 100644 --- a/driver

[PATCH 5/8] staging/ft1000: fix the no brace needed warning in ft1000_read_fifo_len

as the if else statements enclose only one line, so braces around them are not needed. The following warning is fixed drivers/staging/ft1000/ft1000-pcmcia/ft1000_hw.c:100: WARNING: braces {} are not necessary for any arm of this statement Signed-off-by: Devendra Naga --- drivers/staging/ft100

[PATCH 4/8] staging/ft1000: fix sparse warning about the kernel thread handler function

sparse throws warning about the ft1000_poll_thread as drivers/staging/ft1000/ft1000-usb/ft1000_usb.c:40:5: warning: symbol 'ft1000_poll_thread' was not declared. Should it be static? Signed-off-by: Devendra Naga --- drivers/staging/ft1000/ft1000-usb/ft1000_usb.c |2 +- 1 file changed, 1 in

[PATCH 3/8] staging/ft1000: fix sparse warning

sparse warns about having 0 assigned to a pointer, fix it up by using NULL. The following sparse warning is fixed drivers/staging/ft1000/ft1000-usb/ft1000_debug.c:170:52: warning: Using plain integer as NULL pointer Signed-off-by: Devendra Naga --- drivers/staging/ft1000/ft1000-usb/ft1000_deb

[PATCH 2/8] staging/ft1000: fix the spaces issue at the start of line

The following warns fixed drivers/staging/ft1000/ft1000-pcmcia/ft1000_hw.c:2032: ERROR: code indent should use tabs where possible drivers/staging/ft1000/ft1000-pcmcia/ft1000_hw.c:2032: WARNING: please, no spaces at the start of a line Signed-off-by: Devendra Naga --- drivers/staging/ft1000/f

[PATCH 1/8] staging/ft1000: fix the no brace needed warning in ft1000_interrupt

as the if statement encloses only one line braces around it are not needed. The following warn fixed, WARNING: braces {} are not necessary for single statement blocks Signed-off-by: Devendra Naga --- drivers/staging/ft1000/ft1000-pcmcia/ft1000_hw.c |5 ++--- 1 file changed, 2 insertions(+),

[PATCHv2 4/4] staging: omap-thermal: add OMAP5 data structures

This patch adds the data structures needed for proper registration of OMAP5 chips. This patch includes definitions for these chip versions: . OMAP5430 Signed-off-by: Eduardo Valentin --- drivers/staging/omap-thermal/Kconfig | 12 + drivers/staging/omap-thermal/Makefile|1 +

[PATCHv2 3/4] staging: omap-thermal: add OMAP4 data structures

This patch adds the data structures needed for proper registration of OMAP4 chips. This patch includes definitions for these chip versions: . OMAP4430 . OMAP4460 . OMAP4470 Signed-off-by: Eduardo Valentin --- drivers/staging/omap-thermal/Kconfig | 14 ++ drivers/staging/omap-thermal/Ma

[PATCHv2 2/4] staging: omap-thermal: common code to expose driver to thermal framework

This patch has the common thermal framework support for OMAP bandgap driver. It includes the zone registration and unregistration, the cpu cooling and the trip definitions. The trips definition is essentially one trip for passive cooling using the generic cpu cooling device and another one for the

[PATCHv2 1/4] staging: OMAP4+: thermal: introduce bandgap temperature sensor

In the System Control Module, OMAP supplies a voltage reference and a temperature sensor feature that are gathered in the band gap voltage and temperature sensor (VBGAPTS) module. The band gap provides current and voltage reference for its internal circuits and other analog IP blocks. The analog-to

[PATCHv2 0/4] staging: adding OMAP bandgap driver

Greg, Here is the reworked series with the omap bangap driver and minimalist thermal framework support. Diff from v1 is simple that now it won't break compilation. Only change is between patch 1 and patch 2, I have added the missing and needed Makefile and Kconfig entries in patch 1, for omap-band