On Fri, Aug 04, 2017 at 12:45:06PM +0200, Peter Rosin wrote:
> The redundant fb helpers .load_lut, .gamma_set and .gamma_get are
> no longer used. Remove the dead code that was not doing anything
> sensible anyway.
>
> Signed-off-by: Peter Rosin
> ---
> drivers/staging/vboxvideo/vbox_fb.c | 15
The config_log_add() function first calls config_log_put() with the
variable 'cld' and then jumps to label 'out_cld', which will call
the same function with the same 'cld' variable. However, at this
point, 'cld' might have been already freed by the first invocation
of config_log_put(). Even if we r
I ran into a rare build error during randconfig testing:
drivers/staging/media/imx/imx-media-capture.o: In function
`capture_stop_streaming':
imx-media-capture.c:(.text+0x224): undefined reference to `vb2_buffer_done'
drivers/staging/media/imx/imx-media-capture.o: In function
`imx_media_capture_
Making some functions 'static' has uncovered a few functions that
have no caller, through the gcc warnings:
atomisp/i2c/imx/imx.c::12: error: 'imx_t_focus_vcm' defined but not used
[-Werror=unused-function]
atomisp/i2c/imx/imx.c:1103:12: error: 'imx_vcm_init' defined but not used
[-Werror=un
On Sun, Aug 06, 2017 at 05:44:36PM +0200, Hans de Goede wrote:
> On 06-08-17 16:30, Guenter Roeck wrote:
> > On 08/06/2017 05:35 AM, Hans de Goede wrote:
> > > On ACPI platforms, there are no phandles and we need to get the vbus by a
> > > system wide unique name. Add support for a new "fcs,vbus-r
Stephen Hemminger writes:
> With new transparent VF support, it is possible to get a deadlock
> when some of the deferred work is running and the unregister_vf
> is trying to cancel the work element. The solution is to use
> trylock and reschedule (similar to bonding and team device).
>
> Reporte
Vitaly Kuznetsov writes:
> Stephen Hemminger writes:
>
>> With new transparent VF support, it is possible to get a deadlock
>> when some of the deferred work is running and the unregister_vf
>> is trying to cancel the work element. The solution is to use
>> trylock and reschedule (similar to bon
Use kvmalloc()/kvzalloc() instead of atomisp_kernel_malloc()
/atomisp_kernel_zalloc().
Signed-off-by: Geliang Tang
---
.../media/atomisp/pci/atomisp2/atomisp_cmd.c | 31 +-
.../media/atomisp/pci/atomisp2/atomisp_cmd.h | 2 --
.../atomisp/pci/atomisp2/atomisp_comp
Hi Mark,
On 07-08-17 13:10, Mark Brown wrote:
On Sun, Aug 06, 2017 at 05:44:36PM +0200, Hans de Goede wrote:
On 06-08-17 16:30, Guenter Roeck wrote:
On 08/06/2017 05:35 AM, Hans de Goede wrote:
On ACPI platforms, there are no phandles and we need to get the vbus by a
system wide unique name
Vitaly Kuznetsov writes:
> Vitaly Kuznetsov writes:
>
>> Stephen Hemminger writes:
>>
>>> With new transparent VF support, it is possible to get a deadlock
>>> when some of the deferred work is running and the unregister_vf
>>> is trying to cancel the work element. The solution is to use
>>> tr
On Mon, 07 Aug 2017 15:37:49 +0200
Vitaly Kuznetsov wrote:
> Vitaly Kuznetsov writes:
>
> > Stephen Hemminger writes:
> >
> >> With new transparent VF support, it is possible to get a deadlock
> >> when some of the deferred work is running and the unregister_vf
> >> is trying to cancel the w
On Mon, 07 Aug 2017 17:17:19 +0200
Vitaly Kuznetsov wrote:
> Vitaly Kuznetsov writes:
>
> > Vitaly Kuznetsov writes:
> >
> >> Stephen Hemminger writes:
> >>
> >>> With new transparent VF support, it is possible to get a deadlock
> >>> when some of the deferred work is running and the unre
On Mon, Aug 07, 2017 at 04:41:18PM +0200, Hans de Goede wrote:
> On 07-08-17 13:10, Mark Brown wrote:
> Problem 1)
> The regulator in question is part of the bq24292i charger-IC attached to
> a private i2c bus between the PMIC and the charger. The driver for the i2c
> controller inside the PMIC w
Previous fix was incomplete.
Stephen Hemminger (1):
netvsc: make sure and unregister datapath
drivers/net/hyperv/hyperv_net.h | 3 --
drivers/net/hyperv/netvsc.c | 2 --
drivers/net/hyperv/netvsc_drv.c | 71 -
3 files changed, 28 insertions(+), 48
Go back to switching datapath directly in the notifier callback.
Otherwise datapath might not get switched on unregister.
No need for calling the NOTIFY_PEERS notifier since that is only for
a gratitious ARP/ND packet; but that is not required with Hyper-V
because both VF and synthetic NIC have th
On Fri, Aug 04, 2017 at 05:29:10PM +0200, Boris Brezillon wrote:
> We are planning to share more code between different NAND based
> devices (SPI NAND, OneNAND and raw NANDs), but before doing that
> we need to move the existing include/linux/mtd/nand.h file into
> include/linux/mtd/rawnand.h so we
Hi,
On 07-08-17 17:41, Mark Brown wrote:
On Mon, Aug 07, 2017 at 04:41:18PM +0200, Hans de Goede wrote:
On 07-08-17 13:10, Mark Brown wrote:
Problem 1)
The regulator in question is part of the bq24292i charger-IC attached to
a private i2c bus between the PMIC and the charger. The driver f
Hi Boris,
On 08/04/2017 04:29 PM, Boris Brezillon wrote:
[...]
drivers/mtd/nand/jz4780_nand.c | 2 +-
[...]
For JZ4780,
Acked-By: Harvey Hunt
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.
On Friday, August 04, 2017 8:29 AM, Boris Brezillon wrote:
> We are planning to share more code between different NAND based
> devices (SPI NAND, OneNAND and raw NANDs), but before doing that
> we need to move the existing include/linux/mtd/nand.h file into
> include/linux/mtd/rawnand.h so we can l
On 08/04/2017 10:29 AM, Boris Brezillon wrote:
> We are planning to share more code between different NAND based
> devices (SPI NAND, OneNAND and raw NANDs), but before doing that
> we need to move the existing include/linux/mtd/nand.h file into
> include/linux/mtd/rawnand.h so we can later creat
Greg,
This v2 adds the TODO you requested to clarify prism54 will be removed in
two kernel releases from now, and so no further cleanup is needed other
than to ensure the driver compiles.
This is based on linux-next tag next-20170807.
Luis
Luis R. Rodriguez (2):
wireless: move prism54 out
prism54 is deprecated in favor of the p54pci device driver. Although
only *one soul* had reported issues with it long ago Linux most Linux
distributions these days just disable the device driver given the
conflicts with the PCI IDs of p54pci and the *very* unlikely situation
of folks really need th
This will ensure I get emails on my work and personal email address.
Signed-off-by: Luis R. Rodriguez
---
MAINTAINERS | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 3deaddc8c578..997b8062397a 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -
Cleans up some incongruous braces
Signed-off-by: Frank Jozsa
---
drivers/staging/pi433/pi433_if.c | 203 +++
1 file changed, 78 insertions(+), 125 deletions(-)
diff --git a/drivers/staging/pi433/pi433_if.c b/drivers/staging/pi433/pi433_if.c
index ed737f4b1e77
Cleans up some incongruous braces
Signed-off-by: Frank Jozsa
---
drivers/staging/pi433/pi433_if.c | 203 +++
1 file changed, 78 insertions(+), 125 deletions(-)
diff --git a/drivers/staging/pi433/pi433_if.c b/drivers/staging/pi433/pi433_if.c
index ed737f4b1e77
* Hans de Goede [170806 05:37]:
> Register the 5V boost converter as a regulator named
> "regulator-bq24190-usb-vbus". Note the name includes "bq24190" because
> the bq24190 family is also used on ACPI devices where there are no
> device-tree phandles, so regulator_get will fallback to the name an
26 matches
Mail list logo
