The reset function for this driver is a bit of a mess; clean it up to
ensure that it is functioning properly.
Signed-off-by: Chase Southwood chase.southw...@yahoo.com
---
2: *Changed order of register accesses for digital input registers back to
original ordering.
*Removed read of digital output
sparse complains as follows:
drivers/staging/vt6656/aes_ccmp.c:221:6: warning: symbol 'AESbGenCCMP'
was not declared. Should it be static?
In order to suppress the warning, we include the aes_ccmp.h header file
which contains an appropriate extern declaration.
Signed-off-by: huanqi chi
On 2014-04-16 22:19, H Hartley Sweeten wrote:
Step 5 of the (*do_cmdtest) validates that the cmd-chanlist is compatible
with the hardware.
As pointed out by Ian Abbott, some of the step 5 operations are buggy because
they access the cmd-chanlist[] without checking the cmd-chanlist_len.
This
Dan Carpenter dan.carpen...@oracle.com writes:
tree: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
staging-next
head: dff222670ebebf1a7f147a23ccb5fc0312f2ae7e
commit: da290c54610f49ef475f7f88668259216b08fc36 [133/193] staging:
rtl8723au: OnAssocReq23a(): Clean up and use
On Thu, Apr 17, 2014 at 11:50:13AM +0200, Jes Sorensen wrote:
Old smatch warnings:
drivers/staging/rtl8723au/core/rtw_mlme_ext.c:4362
collect_bss_info23a() error: __builtin_memcpy() 'bssid-IEs' too small
(768 vs u32max)
drivers/staging/rtl8723au/core/rtw_mlme_ext.c:4860 process_80211d()
On Thu, Apr 17, 2014 at 11:50:13AM +0200, Jes Sorensen wrote:
Old smatch warnings:
drivers/staging/rtl8723au/core/rtw_mlme_ext.c:4362
collect_bss_info23a() error: __builtin_memcpy() 'bssid-IEs' too small
(768 vs u32max)
drivers/staging/rtl8723au/core/rtw_mlme_ext.c:4860 process_80211d()
Fixes code style errors in drivers/staging/bcm/Qos.c
Signed-off-by: Marcos A. Di Pietro marcos...@gmail.com
---
drivers/staging/bcm/Qos.c | 17 -
1 file changed, 12 insertions(+), 5 deletions(-)
diff --git a/drivers/staging/bcm/Qos.c b/drivers/staging/bcm/Qos.c
index
The latest staging tree based on 3.15-rc1 has revealed a bug that I
introduced into the dgap driver way back. Various oops occur when
loading and unloading the driver multiple times in succession. The oops
never actually indicate anything dgap driver related. When I send a
patch to fix the
Fix naked sscanf
Signed-off-by: Alexandr Terekhov alexandr_terek...@epam.com
diff --git a/drivers/staging/gdm72xx/gdm_wimax.c
b/drivers/staging/gdm72xx/gdm_wimax.c
index 05ce2a2..7f60da3 100644
--- a/drivers/staging/gdm72xx/gdm_wimax.c
+++ b/drivers/staging/gdm72xx/gdm_wimax.c
@@ -285,6 +285,7
On Thu, Apr 17, 2014 at 09:07:12AM -0400, Mark Hounschell wrote:
The latest staging tree based on 3.15-rc1 has revealed a bug that I
introduced into the dgap driver way back. Various oops occur when
loading and unloading the driver multiple times in succession. The oops
never actually indicate
In a patch entitles staging: r8188eu: Fix case where ethtype was never obtained
and always be checked against 0 (commit ID unknown), I introduce an endian
error.
This patch fixes that, and removes two additional sparse warnings.
drivers/staging/rtl8188eu/core/rtw_recv.c:653:6: warning: symbol
dgap driver uses semaphore for obtaining lock. I upgraded it to use MUTEX.
Signed-off-by: Kumar Gaurav kumargauravgup...@gmail.com
---
drivers/staging/dgap/dgap_tty.c | 17 +
1 file changed, 5 insertions(+), 12 deletions(-)
diff --git a/drivers/staging/dgap/dgap_tty.c
Hi All,
Please ignore this patch. I'm sending with correct Subject Line
On Thursday 17 April 2014 09:21 PM, Kumar Gaurav wrote:
dgap driver uses semaphore for obtaining lock. I upgraded it to use MUTEX.
Signed-off-by: Kumar Gaurav kumargauravgup...@gmail.com
---
dgap driver uses semaphore for obtaining lock. I upgraded it to use MUTEX.
Signed-off-by: Kumar Gaurav kumargauravgup...@gmail.com
---
drivers/staging/dgap/dgap_tty.c | 17 +
1 file changed, 5 insertions(+), 12 deletions(-)
diff --git a/drivers/staging/dgap/dgap_tty.c
This driver supports two cmd-start_src values, TRIG_INT and TRIG_EXT. For
TRIG_INT sources, the cmd-start_arg is actually the valid trig_num that is
passed to the async (*inttrig) callback. This driver trivially validates the
arg for this source to be 0.
Refactor the (*inttrig) so that the
This driver supports three cmd-start_src values, TRIG_NOW, TRIG_EXT, and
TRIG_INT. TRIG_NOW sources should always have an arg of 0 and arg for TRIG_EXT
sources is driver specific. This driver does not use the cmd-start_arg with
the TRIG_EXT source so a trivial value of 0 is good.
When the
The cmd-start_arg should be trivially validated in Step 3 of the
(*do_cmdtest) functions. Add the necessary code.
For the analog output, a cmd-start_src of TRIG_NOW and TRIG_INT is
supported. For both sources the cmd-start_arg is validated to be 0.
For a TRIG_INT source, the cmd-start_Arg is
This series continues the cleanup of the comedi async command support.
H Hartley Sweeten (26):
staging: comedi: drivers: core validates chanlist_len max
staging: comedi: drivers: properly validate cmd-scan_end_arg
staging: comedi: addi_apci_3xxx: fix ai subdevice 'len_chanlist'
staging:
This driver supports two cmd-start_src values, TRIG_NOW and TRIG_INT. TRIG_NOW
sources should always have an arg of 0. For TRIG_INT sources, the cmd-start_arg
is actually the valid trig_num that is passed to the async (*inttrig) callback.
This driver trivially validates the arg for both sources to
For both ai and ao commands this driver supports a cmd-start_src of
TRIG_NOW or TRIG_INT. The cmd-start_arg is trivially validated for
both sources to be 0.
For a TRIG_INT source, the cmd-start_arg is actually the valid
trig_num that is used by the async (*inttrig) callback.
Refactor the
This driver only a cmd-start_src of TRIG_NOW or TRIG_INT. The cmd-start_arg
is trivially validated for both sources to be 0. For a TRIG_INT source, the
cmd-start_arg is actually the valid trig_num that is passed to the async
(*inttrig) callback.
Refactor the (*inttrig) function so that the
The comedi core checks if the (cmd-chanlist_len s-len_chanlist) when the
comedi_cmd is copied from user to kernel space by __comedi_get_user_cmd().
If so, the core returns -EINVAL and will not call the subdevice (*do_cmdtest)
and (*do_cmd).
Remove the unnecessary max checks in the comedi driver
The comedi_subdevices array is kzalloc()'d so the async command callbacks do
not need to be set to NULL when the analog output subdevice is initialized.
Also, remove the initialzation of the subdevice 'len_chanlist' since this
value is only used by the async commands. The core will default it to
The cmd-start_arg should be trivially validated in Step 3 of the
(*do_cmdtest) functions. Add the necessary code.
Signed-off-by: H Hartley Sweeten hswee...@visionengravers.com
Cc: Ian Abbott abbo...@mev.co.uk
Cc: Greg Kroah-Hartman gre...@linuxfoundation.org
---
This driver supports a cmd-start_src of TRIG_NOW or TRIG_INT. The
cmd-start_arg is trivially validated for both sources to be 0.
For a TRIG_INT source, the cmd-start_arg is actually the valid
trig_num that is used by the async (*inttrig) callback.
Refactor the (*inttrig) function so that the
For aesthetics, rename the local variable 'error' to 'err'. This is the
normal name for this local variable in (*do_cmdtest) functions.
Signed-off-by: H Hartley Sweeten hswee...@visionengravers.com
Cc: Ian Abbott abbo...@mev.co.uk
Cc: Greg Kroah-Hartman gre...@linuxfoundation.org
---
This driver only supports a cmd-start_src of TRIG_INT for ai commands. The
cmd-start_arg is trivially validated to be 0. For TRIG_INT source, the
cmd-start_arg is actually the valid trig_num that is passed to the async
(*inttrig) callback.
Refactor the (*inttrig) function so that the
This driver supports a cmd-start_src of TRIG_NOW or TRIG_INT. The
cmd-start_arg is trivially validated for both sources to be 0.
For a TRIG_INT source, the cmd-start_arg is actually the valid
trig_num that is used by the async (*inttrig) callback.
Refactor the (*inttrig) function so that the
This driver supports two cmd-start_src values, TRIG_NOW and TRIG_EXT.
For aesthetics, replace the default case when validating the cmd-start_arg
with the proper case statement.
Signed-off-by: H Hartley Sweeten hswee...@visionengravers.com
Cc: Ian Abbott abbo...@mev.co.uk
Cc: Greg Kroah-Hartman
This driver only supports a cmd-start_src of TRIG_INT for ao commands. The
cmd-start_arg is trivially validated to be 0. For TRIG_INT source, the
cmd-start_arg is actually the valid trig_num that is passed to the async
(*inttrig) callback.
Refactor the (*inttrig) function so that the
This driver supports cmd-start_src sources of TRIG_NOW and TRIG_EXT.
Refactor the (*do_cmdtest) to clarify the trivial validation of the
cmd-start_arg.
This also fixes a bug, the cmd-start_src has the trigger not the
cmd-start_arg.
Signed-off-by: H Hartley Sweeten hswee...@visionengravers.com
This driver supports cmd-start_src values of TRIG_NOW, TRIG_EXT, and
TRIG_INT. Currently the cmd-start_arg is only validated for TRIG_NOW.
For TRIG_EXT sources, the cmd-start_src is driver specific. For a
TRIG_INT source, the cmd-start_arg is actually the valid trig_num
that is used by the async
This driver trivially validates the cmd-start_arg for all cmd-start_src values
to be 0. For TRIG_INT source, the cmd-start_arg is actually the valid trig_num
that is passed to the async (*inttrig) callback.
Refactor the (*inttrig) functions so that the cmd-start_arg is used to check
the
trig_num
The cmd-start_arg should be trivially validated in Step 3 of the
(*do_cmdtest) functions. Add the necessary code.
Signed-off-by: H Hartley Sweeten hswee...@visionengravers.com
Cc: Ian Abbott abbo...@mev.co.uk
Cc: Greg Kroah-Hartman gre...@linuxfoundation.org
---
The async command 'arguments' should be trivially validated in Step 3 of
the (*do_cmdtest) not Step 2b. Move the validataion in this driver to the
proper place.
This driver supports two cmd-start_src values, TRIG_NOW and TRIG_EXT.
TRIG_NOW sources should always have an arg of 0. The arg for
This driver supportes cmd-start_src sources of TRIG_NOW, TRIG_INT, TRIG_OTHER,
and TRIG_EXT. Refactor the (*do_cmdtest) to clarify the trivial validation of
the cmd-start_arg. For a TRIG_INT source, the cmd-start_arg is actually the
valid trig_num that is passed to the async (*inttrig) callback.
Clarify the cmd-start_arg validation in Step 3 of the (*do_cmdtest)
functions.
For a TRIG_INT source, the cmd-start_arg is actually the valid
trig_num that is used by the async (*inttrig) callbacks.
Refactor the (*inttrig) functions so that the cmd-start_arg is used
to check the trig_num instead
When the async command 'scan_end_src' is TRIG_COUNT the 'scan_end_arg'
is the cmd-chanlist_len. Fix a couple open-coded drivers. Add the
check to the drivers that do not validate this command argument.
The core validates that the cmd-chanlist_len is = s-len_chanlist.
During the post config after
For all cmd-start_src values this driver trivially validates that the
cmd-start_arg is 0.
For a TRIG_INT source, the cmd-start_arg is actually the valid trig_num
that is used by the async (*inttrig) callback.
Refactor the (*inttrig) functions so that the cmd-start_arg is used to
check the
This driver supports a cmd-start_src of TRIG_NOW, TRIG_INT or TRIG_EXT.
Clarify the cmd-start_arg validation in Step 3 of the (*do_cmdtest).
For a TRIG_INT source, the cmd-start_arg is actually the valid
trig_num that is used by the async (*inttrig) callback.
Refactor the (*inttrig) function so
Due to a driver limitation, the (*do_cmdtest) for the analog input subdevice
overrides the cmd-chanlist_len to force single channel chanlists. But, the
cmd-scan_end_arg was already validated before this happens. Instead of
fixing the (*do_cmdtest) just set the subdevice len_chanlist to 1 to limit
-Original Message-
From: David Miller [mailto:da...@davemloft.net]
Sent: Monday, April 7, 2014 2:43 PM
To: Haiyang Zhang
Cc: net...@vger.kernel.org; KY Srinivasan; o...@aepfle.de;
jasow...@redhat.com; linux-ker...@vger.kernel.org; driverdev-
de...@linuxdriverproject.org
Subject:
From: Haiyang Zhang haiya...@microsoft.com
Date: Thu, 17 Apr 2014 17:25:31 +
Is the net-next tree open now?
No, it is not.
___
devel mailing list
de...@linuxdriverproject.org
Dan Carpenter dan.carpen...@oracle.com writes:
On Thu, Apr 17, 2014 at 11:50:13AM +0200, Jes Sorensen wrote:
Old smatch warnings:
drivers/staging/rtl8723au/core/rtw_mlme_ext.c:4362
collect_bss_info23a() error: __builtin_memcpy() 'bssid-IEs' too small
(768 vs u32max)
Replace OS_kmalloc/OS_kfree with kzalloc/kfree.
And also some allocation doesn't need to use GFP_DMA
so just use GFP_KERNEL.
c4_new() function is never called, remove it.
Signed-off-by: Daeseok Youn daeseok.y...@gmail.com
---
V4: update patch description, OS_kmalloc should be replaced with
45 matches
Mail list logo
