- 14 May, 2018 19 commits
-
-
Ajay Singh authored
Instead of kmalloc and memcpy use kmemdup in handle_connect_timeout(). Also return -ENOMEM incase of failure to allocate the memory. Signed-off-by:
Ajay Singh <ajay.kathat@microchip.com> Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
Ajay Singh authored
Fix line over 80 characters issue in host_int_parse_assoc_resp_info() by using shorter name for the local variable. Signed-off-by:
-
Ajay Singh authored
Split host_int_parse_join_bss_param() to avoid the line over 80 character issue reported by checkpatch.pl script. Signed-off-by:
-
Ajay Singh authored
Fix line over 80 char issue in host_int_handle_disconnect() by using temp variable to hold the 'wilc_connect_result' function pointer. Signed-off-by:
-
Ajay Singh authored
Fix line over 80 character issue found by checkpatch.pl script by aligning the input argument in function call. Signed-off-by:
-
Ajay Singh authored
Fix checkpatch reported issue of line over 80 char in handle_key(). Introduced new functions by spliting existing function to address the checkpatch issue. Signed-off-by:
-
Ajay Singh authored
Remove the use of unnecessary 'ret' variable and use existing 'result' variable to hold the status. Also changed type of 'result' from s32 to int to confirm with the function return type. Signed-off-by:
-
Ajay Singh authored
During memory allocation failure in handle_key() the complete() was not called for comp_test_key_block event. So now added the code to call complete() for event during error scenario. Signed-off-by:
-
Kamal Heib authored
Quoted strings should not be split to help text grep in the source. Signed-off-by:
Kamal Heib <kamalheib1@gmail.com> Signed-off-by:
-
Kamal Heib authored
This change fixes all the lines that get over 80 characters. Signed-off-by:
-
Kamal Heib authored
This commit replaces all the unsigned definitions in favour of 'unsigned int' which is preferred. Signed-off-by:
-
Eric Anholt authored
We just need some integer handles that can map back to our message struct when we're handling a reply, which struct idr is perfect for. v2: Fix error check to look at the right variable. Signed-off-by:
Eric Anholt <eric@anholt.net> Signed-off-by:
-
Christophe JAILLET authored
'buf' is allocated with 'kvzalloc()'. 'kvfree()' must be used to free it. Signed-off-by:
Christophe JAILLET <christophe.jaillet@wanadoo.fr> Fixes: 11c647ca ("staging: lustre: obdclass: variable llog chunk size") Reviewed-by:
NeilBrown <neilb@suse.com> Signed-off-by:
-
Christophe JAILLET authored
According to error handling path before and after this one, we should go to 'out_md_fid' here, instead of 'out_md', if 'obd_connect()' fails. Signed-off-by:
Andreas Dilger <andreas.dilger@intel.com> Signed-off-by:
-
Colin Ian King authored
Trivial fix to spelling mistake in DEBUG_REQ message text Signed-off-by:
Colin Ian King <colin.king@canonical.com> Reviewed-by:
-
Doug Oucharek authored
Under upstream staging commit 5a2ca43f, the list handling code in kiblnd_handle_early_rxs() got changed to list_for_each_safe(). That protects against the current thread from deleting the current entry it is looking at. It does not protect against another thread from deleting the next item in the list (which the tmp variable points to). The way this routine holds then releases a lock opens the door to other threads doing just that. This patch reverts this commit on this routine. Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-9886 Fixes: 5a2ca43f ("Staging: lustre: Iterate list using list_for_each_entry") Signed-off-by:
Doug Oucharek <dougso@me.com> Signed-off-by:
-
Samuel Thibault authored
Signed-off-by:
Samuel Thibault <samuel.thibault@ens-lyon.org> Signed-off-by:
-
Greg Kroah-Hartman authored
Commit 7d7cdb4f ("staging: most: video: remove debugging code") ended up adding a bunch of build warnings about unused variables. Fix that up by removing those variables as we don't need them anymore. Cc: Abdun Nihaal <abdun.nihaal@gmail.com> Reported-by:
Stephen Rothwell <sfr@canb.auug.org.au> Fixes: 7d7cdb4f ("staging: most: video: remove debugging code") Signed-off-by:
-
Eric Anholt authored
Noticed by Stephen Rothwell in -next. Signed-off-by:
-
- 11 May, 2018 21 commits
-
-
Tim Collier authored
Fix checkpatch warning for misaligned * characters in the block comment at the start of p80211metastruct.h; with this change the file is checkpatch clean. Signed-off-by:
Tim Collier <osdevtc@gmail.com> Signed-off-by:
-
Eric Anholt authored
The arg is a u32 *, so switch over to that in our declarations. Signed-off-by:
-
Eric Anholt authored
Fixes a compiler warning about a set-but-not-used variable. I think this was just leftover dead code from before set_framerate_params(), since that also sets up some mmal_parameter_rational structs for fps. Signed-off-by:
-
Eric Anholt authored
The v4l2 uapi uses u8[] for strings, so cast those to char * to avoid compiler warnings about unsigned vs signed with sprintf() and friends. Signed-off-by:
-
Dave Stevenson authored
As requested by Mauro Carvalho Chehab in review. Signed-off-by:
Dave Stevenson <dave.stevenson@raspberrypi.org> Signed-off-by:
-
Dave Stevenson authored
Fix a typo flagged by checkpatch, and another in the same line. Signed-off-by:
-
Dave Stevenson authored
The error conditions don't warrant taking the kernel down, so remove BUG_ON. Signed-off-by:
-
Dave Stevenson authored
struct vchiq_mmal_rect is only referenced from mmal-parameters.h, yet was defined in mmal-vchiq.h. Move it to avoid having to include multiple headers for no reason. Signed-off-by:
-
Dave Stevenson authored
mmal-parameters.h didn't have the normal ... protection to stop it being included multiple times. Add it. Signed-off-by:
-
Dave Stevenson authored
The MMAL and V4L2 buffers had been disassociated, and linked on demand. Seeing as both are finite and low in number, and we now have the same number of each, link them for the duration. This removes the complexity of maintaining lists as the struct mmal_buffer context comes back from the VPU, so we can directly link back to the relevant V4L2 buffer. Signed-off-by:
-
Dave Stevenson authored
For historical reasons, the number of buffers passed to the VPU over MMAL did not match that passed from V4L2. That is a silly situation as the driver has to duplicate serialisation and other functions that have already been implemented in V4L2/videobuf2. As we had more V4L2 buffers than MMAL ones, the MMAL buffer headers were returned to the VPU immediately on being filled, which is now invalid. Match the number of buffers notified in queue_setup with that used in MMAL. Return buffers only when we get them from V4L2. Signed-off-by:
-
Dave Stevenson authored
There is no requirement to serialise bulk transfers as that is all done in VCHI, and if a second MMAL_MSG_TYPE_BUFFER_TO_HOST happened before the VCHI_CALLBACK_BULK_RECEIVED, then the service_callback thread is deadlocked. Remove the bulk_mutex so that multiple receives can be scheduled at a time. Signed-off-by:
-
Dave Stevenson authored
The struct mmal_msg_context was being allocated for every message being sent to the VPU, and freed when it came back. Whilst that is required behaviour for some messages (mainly the synchronous ones), it is wasteful for the video buffers that make up the majority of the traffic. Add to the buffer_init/cleanup hooks that it allocates/frees the msg_context required. v2: changes by anholt from the downstream tree: clean up indentation, pass an error value through, forward-declare the struct so we have less void * Signed-off-by: -
Dave Stevenson authored
Interleaved RGB and single plane YUV formats can be delivered by the GPU without the secondary step of removing padding, as the bytesperline field can be set appropriately. Planar YUV needs the GPU to still remove padding, as there is no way to report that there is padding between the planes (ie on the height). The multi-planar formats are NOT applicable, as there is no easy way to make them contiguous in memory (ie one large allocation that gets broken up). The whole task is passed across to videobuf2 which has no notion of that requirement. v2: Changes by anholt from the downstream driver: Flag two more planar formats as needing padding removal, and remove broken userspace workaround. Signed-off-by: -
Eric Anholt authored
This allows bcm2835-camera to automatically probe after VCHI has loaded, rather than only successfully probing if the arbitrary probe order chooses us after VCHI. Signed-off-by:
-
Eric Anholt authored
We had the camera driver set up in a module_init function, but that meant that the camera driver would fail to load if it was initialized before VCHI. By attaching to this platform_device, it can get a defined load order. Signed-off-by:
-
Ivan Safonov authored
Rx handler (assigned with netdev_rx_handler_register, called from __netif_receive_skb()) uses value of dev->rx_handler_data. The driver has no rx handler and does not need it, so remove rx_handler_data read. Signed-off-by:
Ivan Safonov <insafonov@gmail.com> Signed-off-by:
-
Justin Skists authored
Add a static prefix to the declaration for libcfs_dev. This would fix the following sparse warning: drivers/staging/lustre/lnet/libcfs/module.c:317:19: warning: symbol 'libcfs_dev' was not declared. Should it be static? Signed-off-by:
Justin Skists <justin.skists@juzza.co.uk> Reviewed-by:
-
Colin Ian King authored
Trivial fix to spelling mistake in ODM_RT_TRACE message text Signed-off-by:
-
Abdun Nihaal authored
This patch removes debugging code in video.c that causes the following checkpatch warning: WARNING: Prefer using '\"%s...\", __func__' to using function's name in a string Signed-off-by:
Abdun Nihaal <abdun.nihaal@gmail.com> Signed-off-by:
-
Nathan Chancellor authored
This satisfies a checkpatch.pl warning and is the preferred method for notating the license due to its lack of ambiguity. Signed-off-by:
Nathan Chancellor <natechancellor@gmail.com> Signed-off-by:
-
