Re: Panic in drm_calc_timestamping_constants in staging-next

2015-11-15 Thread Greg KH
On Sun, Nov 15, 2015 at 01:17:00PM -0500, ira.weiny wrote: > With the latest staging-testing and staging-next[*] I am getting the > following panic. > > [*] git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git So 4.4-rc1 also has this issue? Can you use 'git bisect' to track it down

Re: [PATCH 15/20] staging/wilc1000: pass hif operations through initialization

2015-11-15 Thread glen lee
On 2015년 11월 13일 18:17, Arnd Bergmann wrote: On Friday 13 November 2015 16:49:22 glen lee wrote: Hi arnd, I found this. These should be like this. It works fine. + .hif_block_tx_ext = sdio_write, + .hif_block_rx_ext = sdio_read, also, wilc_hif_spi need to be fixed together like th

Re: [PATCHv5 3/3] drm: bridge: anx78xx: Add anx78xx driver support by analogix.

2015-11-15 Thread kbuild test robot
Hi Enric, [auto build test ERROR on: robh/for-next] [also build test ERROR on: v4.3 next-20151115] [cannot apply to: drm/drm-next] url: https://github.com/0day-ci/linux/commits/Enric-Balletbo-i-Serra/Add-initial-support-for-slimport-anx78xx/20151113-200502 base: https://git.kernel.org/pub

[PATCH] staging:rtl8192e: Usage count off by one

2015-11-15 Thread Sean MacLennan
The rtllib driver is not calling try_module_get() when loading the encryption modules. Because of this, you can never remove the module once you have used it one (i.e. bring up the wireless interface). Signed-off-by: Sean MacLennan --- drivers/staging/rtl8192e/rtllib_softmac.c | 2 +- drivers/st

[PATCH] staging-EHCA: Delete unnecessary checks before the function call "kmem_cache_destroy"

2015-11-15 Thread SF Markus Elfring
From: Markus Elfring Date: Sun, 15 Nov 2015 21:58:45 +0100 The kmem_cache_destroy() function tests whether its argument is NULL and then returns immediately. Thus the test around the calls is not needed. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --

Panic in drm_calc_timestamping_constants in staging-next

2015-11-15 Thread ira.weiny
With the latest staging-testing and staging-next[*] I am getting the following panic. [*] git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git [ 11.232549] BUG: unable to handle kernel NULL pointer dereference at 00b0 [ 11.232568] IP: [] drm_calc_timestamping_constan

US National Central Bureau of Interpol,

2015-11-15 Thread Doctor Lisa Wade
US National Central Bureau of Interpol, CYBER CRIMES UNIT Liasian Office, Police Chief, vol. LXXVIII, no. 6, June 2011. Copyright held by the International Association of Chiefs of Police, 950 Pennsylvania Avenue, NW Washington, DC 20530- 0001, e-Mail: sydneybaroso...@gmail.com Hello friend, God

Re: [PATCH] Staging: iio: iio_simple_dummy_buffer: Typo in comments area

2015-11-15 Thread Jonathan Cameron
On 15/11/15 11:35, Nizam Haider wrote: > On Sat, Nov 14, 2015 at 05:21:48PM +, Jonathan Cameron wrote: >> On 14/11/15 09:28, Lars-Peter Clausen wrote: >>> On 11/14/2015 03:44 AM, Nizam Haider wrote: Fix simple typo in comments Signed-off-by: Nizam Haider >>> >>> Thanks for the p

Re: [PATCH] Staging: iio: iio_simple_dummy_buffer: Typo in comments area

2015-11-15 Thread Nizam Haider
On Sat, Nov 14, 2015 at 05:21:48PM +, Jonathan Cameron wrote: > On 14/11/15 09:28, Lars-Peter Clausen wrote: > > On 11/14/2015 03:44 AM, Nizam Haider wrote: > >> Fix simple typo in comments > >> > >> Signed-off-by: Nizam Haider > > > > Thanks for the patch. > > > >> --- > >> drivers/staging

Re: [PATCH] iio: adc: mxs-lradc: Prefer using the BIT macro

2015-11-15 Thread Jonathan Cameron
On 09/11/15 14:26, Nizam Haider wrote: > Replaces bit shifting on 1 with the BIT(x) macro > > Signed-off-by: Nizam Haider Applied to the togreg branch of iio.git - guess I'm going to start getting the autobuilder warnings shortly! Will be pushed out as testing for the autobuilders to play with i

Re: [PATCH] iio: adc: mxs-lradc: Prefer using the BIT macro

2015-11-15 Thread Jonathan Cameron
On 09/11/15 14:40, kbuild test robot wrote: > Hi Nizam, Wow, this one opens up a can of worms that as far as I can tell is in no way actually connected to your patch Nizam! (just in case you were wondering). I'm not actually certain what did trigger this. Right now I haven't found any cases that