The binderfs filesystem never needs to be mounted by the kernel itself.
This is conceptually wrong and should never have been done in the first
place.
Fixes: 3ad20fe393b ("binder: implement binderfs")
Signed-off-by: Christian Brauner
---
drivers/android/binderfs.c | 10 --
1 file changed
Hey,
This small series deals with two fix/improvements for binderfs. And both
actually allows us to remove code. *Yay!*
The first patch removes an unneeded and conceptually wrong kern_mount()
call for binderfs. I think this even might have been pointed out at some
point by Greg. I'm not sure righ
When currently mounting binderfs in the same ipc namespace twice:
mount -t binder binder /A
mount -t binder binder /B
then the binderfs instances mounted on /A and /B will be the same, i.e.
they will have the same superblock. This was the first approach that seemed
reasonable. However, this leads
rtw_wps_start() is part of dead code due to CONFIG_INTEL_WIDI.
The fix removes the deadcode and replaces the function with NULL
in rtw_private_handler. Identified as part of copy_from_user bug.
Signed-off-by: Aditya Pakki
---
.../staging/rtl8723bs/os_dep/ioctl_linux.c| 34 +--
Hi, Haibing
Thanks for your patch, it looks fine for me.
Reviewed-by: Bingbu Cao
On 12/29/2018 10:45 AM, YueHaibing wrote:
css->pipes[pipe].bindex = binary;
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org
On 12/12/18 8:51 PM, Paul Kocialkowski wrote:
Hi,
On Wed, 2018-12-05 at 21:59 +0100, Jernej Škrabec wrote:
+
+#define V4L2_HEVC_DPB_ENTRY_RPS_ST_CURR_BEFORE 0x01
+#define V4L2_HEVC_DPB_ENTRY_RPS_ST_CURR_AFTER 0x02
+#define V4L2_HEVC_DPB_ENTRY_RPS_LT_CURR0x03
+
+#define V4L2_H
Hi Julius,
On 1/6/2019 12:48 PM, Július Milan wrote:
>> Before you send V3, are you sure this is the correct fix? As "frame_type" is
>> input as u16, it seems to me that the frame_type member of struct
>> wilc_reg_frame
>> should be __le16, not __le32.
>
> Yes, I am confident about it.
> The fra
