This is a clean-up patch which replaces DEVICE_ATTR() macro with file
permission specific DEVICE_ATTR_RO() macro for compaction and
readability.
Done using coccinelle:
@r@
identifier attr, show_fn;
declarer name DEVICE_ATTR;
@@
DEVICE_ATTR(attr, \(S_IRUGO\|0444\), show_fn, NULL);
@script:
This is a clean-up patch which replaces DEVICE_ATTR() macro with file
permission specific DEVICE_ATTR_RO() macro for compaction and
readability.
Done using coccinelle:
@r@
identifier attr, show_fn;
declarer name DEVICE_ATTR;
@@
DEVICE_ATTR(attr, \(S_IRUGO\|0444\), show_fn, NULL);
@script:
On Mon, Dec 11, 2017 at 11:58:37AM -0500, David Miller wrote:
> From: Michal Kubecek
> Date: Mon, 11 Dec 2017 17:13:50 +0100
>
> > On Wed, Dec 06, 2017 at 03:57:14PM -0500, David Miller wrote:
> >> From: Kevin Cernekee
> >> Date: Wed, 6 Dec 2017
On Mon, Dec 11, 2017 at 11:58:37AM -0500, David Miller wrote:
> From: Michal Kubecek
> Date: Mon, 11 Dec 2017 17:13:50 +0100
>
> > On Wed, Dec 06, 2017 at 03:57:14PM -0500, David Miller wrote:
> >> From: Kevin Cernekee
> >> Date: Wed, 6 Dec 2017 12:12:27 -0800
> >>
> >> > Currently, a nlmon
This adds a restart function to the davinci watchdog timer driver.
This is copied from arch/arm/mach-davinci/time.c and will allow us to
remove the code from there.
Signed-off-by: David Lechner
---
drivers/watchdog/davinci_wdt.c | 38 ++
This removes the watchdog reset code. The reset has been moved to
drivers/watchdog/davinci_wdt.c. The watchdog driver registers the reset
with the kernel so defining a reset for each machine is no longer needed.
Signed-off-by: David Lechner
---
This adds a restart function to the davinci watchdog timer driver.
This is copied from arch/arm/mach-davinci/time.c and will allow us to
remove the code from there.
Signed-off-by: David Lechner
---
drivers/watchdog/davinci_wdt.c | 38 ++
1 file changed, 38
This removes the watchdog reset code. The reset has been moved to
drivers/watchdog/davinci_wdt.c. The watchdog driver registers the reset
with the kernel so defining a reset for each machine is no longer needed.
Signed-off-by: David Lechner
---
arch/arm/mach-davinci/board-da830-evm.c | 1 -
This series moves the watchdog restart code from arch/arm/mach-davinci
to drivers/watchdog.
Tested working on LEGO MINDSTORMS EV3 (TI AM1808 processor).
David Lechner (2):
watchdog: davinci_wdt: add restart function
ARM: davinci: remove watchdog reset
This series moves the watchdog restart code from arch/arm/mach-davinci
to drivers/watchdog.
Tested working on LEGO MINDSTORMS EV3 (TI AM1808 processor).
David Lechner (2):
watchdog: davinci_wdt: add restart function
ARM: davinci: remove watchdog reset
[+cc linux-pci]
On Mon, Dec 11, 2017 at 11:29:50AM -0500, Sinan Kaya wrote:
> Hi Chris,
>
> >
> > I'm more than happy to provide additional diagnostics and test proposed
> > fixes. As a starter for ten, I've attached the
> > output from 'lspci -v'. If, however, you need to see the backtrace,
[+cc linux-pci]
On Mon, Dec 11, 2017 at 11:29:50AM -0500, Sinan Kaya wrote:
> Hi Chris,
>
> >
> > I'm more than happy to provide additional diagnostics and test proposed
> > fixes. As a starter for ten, I've attached the
> > output from 'lspci -v'. If, however, you need to see the backtrace,
On Thursday, November 30, 2017 4:52 PM, Lukasz Majewski wrote:
>
> The BK3 board is a derivative of the ts72xx reference design.
Lukasz,
I was just reviewing the other TS-72xx boards and noticed this:
> +/* BK3 specific defines */
> +#define BK3_CPLDVER_PHYS_BASE0x2340
>
On Thursday, November 30, 2017 4:52 PM, Lukasz Majewski wrote:
>
> The BK3 board is a derivative of the ts72xx reference design.
Lukasz,
I was just reviewing the other TS-72xx boards and noticed this:
> +/* BK3 specific defines */
> +#define BK3_CPLDVER_PHYS_BASE0x2340
>
On 11/12/17 07:58 AM, Allen Hubbe wrote:
!IS_ALIGNED(addr, BIT_ULL(xlate_pos))
Ok, yes, that's much better. I'll change it. Thanks.
+ /*
+* In certain circumstances we can get a buffer that is
+* not aligned to its size. (Most of the time
+
On 11/12/17 07:58 AM, Allen Hubbe wrote:
!IS_ALIGNED(addr, BIT_ULL(xlate_pos))
Ok, yes, that's much better. I'll change it. Thanks.
+ /*
+* In certain circumstances we can get a buffer that is
+* not aligned to its size. (Most of the time
+
On Mon, Dec 11, 2017 at 06:06:30PM +0100, Takashi Iwai wrote:
> On Mon, 11 Dec 2017 18:00:22 +0100,
> Vinod Koul wrote:
> >
> > On Mon, Dec 11, 2017 at 05:10:17PM +0100, Takashi Iwai wrote:
> > > On Wed, 06 Dec 2017 16:47:00 +0100,
> > > Vinod Koul wrote:
> > > >
> > > > + /* TODO:
On Mon, Dec 11, 2017 at 06:06:30PM +0100, Takashi Iwai wrote:
> On Mon, 11 Dec 2017 18:00:22 +0100,
> Vinod Koul wrote:
> >
> > On Mon, Dec 11, 2017 at 05:10:17PM +0100, Takashi Iwai wrote:
> > > On Wed, 06 Dec 2017 16:47:00 +0100,
> > > Vinod Koul wrote:
> > > >
> > > > + /* TODO:
From: Branislav Radocaj
Date: Sat, 9 Dec 2017 12:51:33 +0100
> If clk_set_rate() fails, we should disable clk before return.
> Found by Linux Driver Verification project (linuxtesting.org).
>
> Signed-off-by: Branislav Radocaj
> ---
>
> Changes
From: Branislav Radocaj
Date: Sat, 9 Dec 2017 12:51:33 +0100
> If clk_set_rate() fails, we should disable clk before return.
> Found by Linux Driver Verification project (linuxtesting.org).
>
> Signed-off-by: Branislav Radocaj
> ---
>
> Changes since v2:
> * Improved inconsistent failure
Adding linux-rt-users group to thread.
From: Jonathan Haws
Sent: Monday, December 11, 2017 08:37
To: mi...@kernel.org; v...@zeniv.linux.org.uk; a...@arndb.de;
a...@linux-foundation.org; deepa.ker...@gmail.com
Cc:
Adding linux-rt-users group to thread.
From: Jonathan Haws
Sent: Monday, December 11, 2017 08:37
To: mi...@kernel.org; v...@zeniv.linux.org.uk; a...@arndb.de;
a...@linux-foundation.org; deepa.ker...@gmail.com
Cc: linux-kernel@vger.kernel.org;
On Mon, Dec 11, 2017 at 10:56:33AM +0100, Vitaly Kuznetsov wrote:
> Roman Kagan writes:
> > On Fri, Dec 08, 2017 at 11:49:57AM +0100, Vitaly Kuznetsov wrote:
> >> +void register_hv_tsc_update(void (*cb)(void))
> >> +{
> >
> > The function name seems unfortunate. IMHO such a
On Mon, Dec 11, 2017 at 10:56:33AM +0100, Vitaly Kuznetsov wrote:
> Roman Kagan writes:
> > On Fri, Dec 08, 2017 at 11:49:57AM +0100, Vitaly Kuznetsov wrote:
> >> +void register_hv_tsc_update(void (*cb)(void))
> >> +{
> >
> > The function name seems unfortunate. IMHO such a name suggests
> >
Em Mon, Dec 11, 2017 at 01:43:12PM -0200, Arnaldo de Melo escreveu:
> Em Fri, Dec 08, 2017 at 06:48:17PM +0100, Michael Petlan escreveu:
> > Hi Arnaldo, so I have tried what you've suggested and looks good.
> > Patch is attached. Sorry for not posting it in-text, but I need to
> > fix my mail
Em Mon, Dec 11, 2017 at 01:43:12PM -0200, Arnaldo de Melo escreveu:
> Em Fri, Dec 08, 2017 at 06:48:17PM +0100, Michael Petlan escreveu:
> > Hi Arnaldo, so I have tried what you've suggested and looks good.
> > Patch is attached. Sorry for not posting it in-text, but I need to
> > fix my mail
On 11/12/17 16:29, Sinan Kaya wrote:
> Hi Chris,
>
>>
>> I'm more than happy to provide additional diagnostics and test proposed
>> fixes. As a starter for ten, I've attached the
>> output from 'lspci -v'. If, however, you need to see the backtrace, I'll
>> need some advice on how to capture
On 11/12/17 16:29, Sinan Kaya wrote:
> Hi Chris,
>
>>
>> I'm more than happy to provide additional diagnostics and test proposed
>> fixes. As a starter for ten, I've attached the
>> output from 'lspci -v'. If, however, you need to see the backtrace, I'll
>> need some advice on how to capture
On Mon, 11 Dec 2017 18:00:22 +0100,
Vinod Koul wrote:
>
> On Mon, Dec 11, 2017 at 05:10:17PM +0100, Takashi Iwai wrote:
> > On Wed, 06 Dec 2017 16:47:00 +0100,
> > Vinod Koul wrote:
> > >
> > > + /* TODO: Read audio mode */
> > > +
> > > + i++;
> > > + }
> >
> > Don't we use
On Mon, 11 Dec 2017 18:00:22 +0100,
Vinod Koul wrote:
>
> On Mon, Dec 11, 2017 at 05:10:17PM +0100, Takashi Iwai wrote:
> > On Wed, 06 Dec 2017 16:47:00 +0100,
> > Vinod Koul wrote:
> > >
> > > + /* TODO: Read audio mode */
> > > +
> > > + i++;
> > > + }
> >
> > Don't we use
On Mon, Dec 11, 2017 at 6:01 PM, Greg Kroah-Hartman
wrote:
> On Mon, Dec 11, 2017 at 02:59:13PM +0200, Mathias Nyman wrote:
>> On 11.12.2017 13:27, Arnd Bergmann wrote:
>> > gcc-8 warnings about the new driver using a memset with a bogus length:
>> >
>> >
On Mon, Dec 11, 2017 at 6:01 PM, Greg Kroah-Hartman
wrote:
> On Mon, Dec 11, 2017 at 02:59:13PM +0200, Mathias Nyman wrote:
>> On 11.12.2017 13:27, Arnd Bergmann wrote:
>> > gcc-8 warnings about the new driver using a memset with a bogus length:
>> >
>> > drivers/usb/host/xhci-dbgcap.c: In
On Mon, Dec 11, 2017 at 01:30:03PM +0800, Huang, Ying wrote:
> Andrew Morton writes:
>
> > On Fri, 08 Dec 2017 16:41:38 +0800 "Huang\, Ying"
> > wrote:
> >
> >> > Why do we need srcu here? Is it enough with rcu like below?
> >> >
> >> > It might
On Mon, Dec 11, 2017 at 01:30:03PM +0800, Huang, Ying wrote:
> Andrew Morton writes:
>
> > On Fri, 08 Dec 2017 16:41:38 +0800 "Huang\, Ying"
> > wrote:
> >
> >> > Why do we need srcu here? Is it enough with rcu like below?
> >> >
> >> > It might have a bug/room to be optimized about
From: Jiri Pirko
Date: Mon, 11 Dec 2017 17:32:46 +0100
> I think that it does not make sense to convert ethtool->netlink_ethtool
> 1:1 feature wise. Now we have devlink, ritch switch representation
> model, tc offload and many others. Lot of things that are in
> ethtool, should
From: Jiri Pirko
Date: Mon, 11 Dec 2017 17:32:46 +0100
> I think that it does not make sense to convert ethtool->netlink_ethtool
> 1:1 feature wise. Now we have devlink, ritch switch representation
> model, tc offload and many others. Lot of things that are in
> ethtool, should be done in
On Mon, Dec 11, 2017 at 02:59:13PM +0200, Mathias Nyman wrote:
> On 11.12.2017 13:27, Arnd Bergmann wrote:
> > gcc-8 warnings about the new driver using a memset with a bogus length:
> >
> > drivers/usb/host/xhci-dbgcap.c: In function 'xhci_dbc_eps_exit':
> > drivers/usb/host/xhci-dbgcap.c:369:2:
On Mon, Dec 11, 2017 at 02:59:13PM +0200, Mathias Nyman wrote:
> On 11.12.2017 13:27, Arnd Bergmann wrote:
> > gcc-8 warnings about the new driver using a memset with a bogus length:
> >
> > drivers/usb/host/xhci-dbgcap.c: In function 'xhci_dbc_eps_exit':
> > drivers/usb/host/xhci-dbgcap.c:369:2:
Den 10.12.2017 23.10, skrev David Lechner:
This adds a new device tree binding for Sitronix ST7735R display panels,
such as the Adafruit 1.8" TFT.
Signed-off-by: David Lechner
Acked-by: Rob Herring
---
v2: changes:
* None, but...
I'm wondering about
Den 10.12.2017 23.10, skrev David Lechner:
This adds a new device tree binding for Sitronix ST7735R display panels,
such as the Adafruit 1.8" TFT.
Signed-off-by: David Lechner
Acked-by: Rob Herring
---
v2: changes:
* None, but...
I'm wondering about my choice of compatible here. I chose
From: Michal Kubecek
Date: Mon, 11 Dec 2017 17:13:50 +0100
> On Wed, Dec 06, 2017 at 03:57:14PM -0500, David Miller wrote:
>> From: Kevin Cernekee
>> Date: Wed, 6 Dec 2017 12:12:27 -0800
>>
>> > Currently, a nlmon link inside a child namespace can
From: Michal Kubecek
Date: Mon, 11 Dec 2017 17:13:50 +0100
> On Wed, Dec 06, 2017 at 03:57:14PM -0500, David Miller wrote:
>> From: Kevin Cernekee
>> Date: Wed, 6 Dec 2017 12:12:27 -0800
>>
>> > Currently, a nlmon link inside a child namespace can observe systemwide
>> > netlink activity.
Wait for the syncronization of all clocks when resuming, not only the
UPLL clock. Do not use regmap_read_poll_timeout, as it will call BUG()
when interrupts are masked, which is the case in here.
Signed-off-by: Romain Izard
Acked-by: Ludovic Desroches
Wait for the syncronization of all clocks when resuming, not only the
UPLL clock. Do not use regmap_read_poll_timeout, as it will call BUG()
when interrupts are masked, which is the case in here.
Signed-off-by: Romain Izard
Acked-by: Ludovic Desroches
Acked-by: Nicolas Ferre
---
Add reg_drivevbus regualtor for boards which are using
external regulator to drive the OTG VBus through N_VBUSEN
PMIC pin.
Signed-off-by: Jagan Teki
---
Changes for v3:
- none
arch/arm64/boot/dts/allwinner/axp803.dtsi | 5 +
1 file changed, 5 insertions(+)
diff
Add reg_drivevbus regualtor for boards which are using
external regulator to drive the OTG VBus through N_VBUSEN
PMIC pin.
Signed-off-by: Jagan Teki
---
Changes for v3:
- none
arch/arm64/boot/dts/allwinner/axp803.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git
Add usb otg support for bananapi-m64 board,
- USB-ID connected with PH9
- USB-DRVVBUS controlled by N_VBUSEN pin from PMIC
Signed-off-by: Jagan Teki
---
Changes for v3:
- Move the position of reg_drivevbus as per binding documentation.
Changes for v2:
- add drvvbus
Add usb otg support for bananapi-m64 board,
- USB-ID connected with PH9
- USB-DRVVBUS controlled by N_VBUSEN pin from PMIC
Signed-off-by: Jagan Teki
---
Changes for v3:
- Move the position of reg_drivevbus as per binding documentation.
Changes for v2:
- add drvvbus regulator
- add N_VBUSEN pin
Like axp221, axp223, axp813 the axp803 is also supporting external
regulator to drive the OTG VBus through N_VBUSEN PMIC pin.
Add support for it.
Signed-off-by: Jagan Teki
Reviewed-by: Rob Herring
---
Changes for v3:
- Update drivevbus in table of
Like axp221, axp223, axp813 the axp803 is also supporting external
regulator to drive the OTG VBus through N_VBUSEN PMIC pin.
Add support for it.
Signed-off-by: Jagan Teki
Reviewed-by: Rob Herring
---
Changes for v3:
- Update drivevbus in table of regulators
From: Jiri Pirko
Date: Mon, 11 Dec 2017 17:02:21 +0100
> Mon, Dec 11, 2017 at 02:53:31PM CET, mkube...@suse.cz wrote:
>>No function implemented yet, only genetlink and module infrastructure.
>>Register/unregister genetlink family "ethtool" and allow the module to be
From: Jiri Pirko
Date: Mon, 11 Dec 2017 17:02:21 +0100
> Mon, Dec 11, 2017 at 02:53:31PM CET, mkube...@suse.cz wrote:
>>No function implemented yet, only genetlink and module infrastructure.
>>Register/unregister genetlink family "ethtool" and allow the module to be
>>autoloaded by genetlink
On Mon, Dec 11, 2017 at 05:10:17PM +0100, Takashi Iwai wrote:
> On Wed, 06 Dec 2017 16:47:00 +0100,
> Vinod Koul wrote:
> >
> > +static int sdw_slave_read_dpn(struct sdw_slave *slave,
> > + struct sdw_dpn_prop *dpn, int count, int ports, char *type)
> > +{
>
> > + nval =
On Mon, Dec 11, 2017 at 05:10:17PM +0100, Takashi Iwai wrote:
> On Wed, 06 Dec 2017 16:47:00 +0100,
> Vinod Koul wrote:
> >
> > +static int sdw_slave_read_dpn(struct sdw_slave *slave,
> > + struct sdw_dpn_prop *dpn, int count, int ports, char *type)
> > +{
>
> > + nval =
When an AT91 programmable clock is declared in the device tree, register
it into the Power Management Controller driver. On entering suspend mode,
the driver saves and restores the Programmable Clock registers to support
the backup mode for these clocks.
Signed-off-by: Romain Izard
When an AT91 programmable clock is declared in the device tree, register
it into the Power Management Controller driver. On entering suspend mode,
the driver saves and restores the Programmable Clock registers to support
the backup mode for these clocks.
Signed-off-by: Romain Izard
Acked-by:
While the core of the backup mode for SAMA5D2 has been integrated in
v4.13, it is far from complete. Individual controllers in the chip have
drivers that do not support the reset of the registers during suspend,
and they need to be adapted to handle it.
The first patch uses the clock wakeup code
While the core of the backup mode for SAMA5D2 has been integrated in
v4.13, it is far from complete. Individual controllers in the chip have
drivers that do not support the reset of the registers during suspend,
and they need to be adapted to handle it.
The first patch uses the clock wakeup code
The contents of the System Clock Status Register (SCSR) needs to be
restored into the System Clock Enable Register (SCER).
As the bootloader will restore some clocks by itself, the issue can be
missed as only the USB controller, the LCD controller, the Image Sensor
controller and the programmable
The contents of the System Clock Status Register (SCSR) needs to be
restored into the System Clock Enable Register (SCER).
As the bootloader will restore some clocks by itself, the issue can be
missed as only the USB controller, the LCD controller, the Image Sensor
controller and the programmable
On Mon, Dec 11, 2017 at 05:52:16PM +0100, Hans de Goede wrote:
> On many laptops setting a different LPM policy then unknown /
> max_performance can lead to power-savings of 1.0 - 1.5 Watts (when idle).
>
> Modern ultrabooks idle around 6W (at 50% screen brightness), 1.0 - 1.5W
> is a significant
On Mon, Dec 11, 2017 at 05:52:16PM +0100, Hans de Goede wrote:
> On many laptops setting a different LPM policy then unknown /
> max_performance can lead to power-savings of 1.0 - 1.5 Watts (when idle).
>
> Modern ultrabooks idle around 6W (at 50% screen brightness), 1.0 - 1.5W
> is a significant
On 12/11/2017 8:30 AM, Eric Paris wrote:
> On Sat, 2017-12-09 at 10:28 -0800, Casey Schaufler wrote:
>> Because a container doesn't have to use namespaces to be a container
>> you still need a mechanism for a process to declare that it is in
>> fact
>> in a container, and to identify the
On 12/11/2017 8:30 AM, Eric Paris wrote:
> On Sat, 2017-12-09 at 10:28 -0800, Casey Schaufler wrote:
>> Because a container doesn't have to use namespaces to be a container
>> you still need a mechanism for a process to declare that it is in
>> fact
>> in a container, and to identify the
On many laptops setting a different LPM policy then unknown /
max_performance can lead to power-savings of 1.0 - 1.5 Watts (when idle).
Modern ultrabooks idle around 6W (at 50% screen brightness), 1.0 - 1.5W
is a significant chunk of this.
There are some performance / latency costs to enabling
On many laptops setting a different LPM policy then unknown /
max_performance can lead to power-savings of 1.0 - 1.5 Watts (when idle).
Modern ultrabooks idle around 6W (at 50% screen brightness), 1.0 - 1.5W
is a significant chunk of this.
There are some performance / latency costs to enabling
Hi Flavio,
Thank you for the patch.
On Wednesday, 6 December 2017 18:38:50 EET Flavio Ceolin wrote:
> pxa_camera_probe() was not calling pxa_camera_deactivate(),
> responsible to call clk_disable_unprepare(), on the failure path. This
> was leading to unbalancing source clock.
>
> Found by
Hi Flavio,
Thank you for the patch.
On Wednesday, 6 December 2017 18:38:50 EET Flavio Ceolin wrote:
> pxa_camera_probe() was not calling pxa_camera_deactivate(),
> responsible to call clk_disable_unprepare(), on the failure path. This
> was leading to unbalancing source clock.
>
> Found by
* Bhumika Goyal [171106 05:17]:
> Make some pointers and function arguments as const. After this change,
> make the structures of type cm_ll_data as const.
Thanks applying both in to omap-for-v4.16/soc.
Regards,
Tony
* Bhumika Goyal [171106 05:17]:
> Make some pointers and function arguments as const. After this change,
> make the structures of type cm_ll_data as const.
Thanks applying both in to omap-for-v4.16/soc.
Regards,
Tony
* Steven Rostedt wrote:
> Daniel Wagner reported a crash on the beaglebone black. This is a
> single CPU architecture, and does not have a functional:
> arch_send_call_function_single_ipi() and can crash if that is called.
>
> As it only has one CPU, it shouldn't be
* Steven Rostedt wrote:
> Daniel Wagner reported a crash on the beaglebone black. This is a
> single CPU architecture, and does not have a functional:
> arch_send_call_function_single_ipi() and can crash if that is called.
>
> As it only has one CPU, it shouldn't be called, but if the kernel
From: Colin Ian King
Function xhci_dbc_free_req is local to the source and does not need to
be in global scope, so make it static.
Cleans up sparse warning:
symbol 'xhci_dbc_free_req' was not declared. Should it be static?
Signed-off-by: Colin Ian King
From: Colin Ian King
Function xhci_dbc_free_req is local to the source and does not need to
be in global scope, so make it static.
Cleans up sparse warning:
symbol 'xhci_dbc_free_req' was not declared. Should it be static?
Signed-off-by: Colin Ian King
---
drivers/usb/host/xhci-dbgtty.c | 2
* Felipe Balbi [171204 11:43]:
> Roger Quadros writes:
>
> > The metastability workaround causes Erratic errors [1]
> > on the HighSpeed USB PHY which can cause upto 2 seconds
> > delay in enumerating to a USB host while in Gadget mode.
> >
> > Disable the
* Felipe Balbi [171204 11:43]:
> Roger Quadros writes:
>
> > The metastability workaround causes Erratic errors [1]
> > on the HighSpeed USB PHY which can cause upto 2 seconds
> > delay in enumerating to a USB host while in Gadget mode.
> >
> > Disable the Run/Stop metastability workaround to
On 2017-12-11 17:35, Mark Brown wrote:
> On Mon, Dec 11, 2017 at 03:26:13PM +0100, Peter Rosin wrote:
>> Hi!
>>
>> Device tree bindings where added for the tfa9879 along with improved
>> support for them in the driver some time ago. All behind my back.
>> This cleans things up and properly adds me
On 2017-12-11 17:35, Mark Brown wrote:
> On Mon, Dec 11, 2017 at 03:26:13PM +0100, Peter Rosin wrote:
>> Hi!
>>
>> Device tree bindings where added for the tfa9879 along with improved
>> support for them in the driver some time ago. All behind my back.
>> This cleans things up and properly adds me
Hello Jacob,
Thank you for the patch.
On Wednesday, 6 December 2017 13:19:34 EET Jacob Chen wrote:
> From: Jacob Chen
>
> Add DT bindings documentation for Rockchip MIPI D-PHY RX
>
> Signed-off-by: Jacob Chen
> ---
>
Hello Jacob,
Thank you for the patch.
On Wednesday, 6 December 2017 13:19:34 EET Jacob Chen wrote:
> From: Jacob Chen
>
> Add DT bindings documentation for Rockchip MIPI D-PHY RX
>
> Signed-off-by: Jacob Chen
> ---
> .../bindings/media/rockchip-mipi-dphy.txt | 71
On 12/08/2017 11:54 PM, Kees Cook wrote:
> On Fri, Dec 8, 2017 at 7:29 AM, Dmitry Vyukov wrote:
>> On Fri, Dec 8, 2017 at 4:29 PM, Andrey Ryabinin
>> wrote:
>>>
>>> So, possible solutions are:
>>>
>>> 1) Simply disable word-at-a-time optimization in
On Mon, Dec 11, 2017 at 05:02:10PM +0100, Takashi Iwai wrote:
> On Wed, 06 Dec 2017 16:46:59 +0100,
> Vinod Koul wrote:
> >
> > + /* Set group device numbers and master device number */
> > + set_bit(SDW_GROUP12_DEV_NUM | SDW_GROUP13_DEV_NUM, bus->assigned);
>
> Is this really correct?
On 12/08/2017 11:54 PM, Kees Cook wrote:
> On Fri, Dec 8, 2017 at 7:29 AM, Dmitry Vyukov wrote:
>> On Fri, Dec 8, 2017 at 4:29 PM, Andrey Ryabinin
>> wrote:
>>>
>>> So, possible solutions are:
>>>
>>> 1) Simply disable word-at-a-time optimization in strscpy(). I seriously
>>> doubt
>>> that
On Mon, Dec 11, 2017 at 05:02:10PM +0100, Takashi Iwai wrote:
> On Wed, 06 Dec 2017 16:46:59 +0100,
> Vinod Koul wrote:
> >
> > + /* Set group device numbers and master device number */
> > + set_bit(SDW_GROUP12_DEV_NUM | SDW_GROUP13_DEV_NUM, bus->assigned);
>
> Is this really correct?
These duplicate includes have been found with scripts/checkincludes.pl but
they have been removed manually to avoid removing false positives.
Signed-off-by: Pravin Shedge
---
net/core/netprio_cgroup.c| 1 -
net/dsa/slave.c | 1 -
These duplicate includes have been found with scripts/checkincludes.pl but
they have been removed manually to avoid removing false positives.
Signed-off-by: Pravin Shedge
---
net/core/netprio_cgroup.c| 1 -
net/dsa/slave.c | 1 -
From: Josef Bacik
Using BPF we can override kprob'ed functions and return arbitrary
values. Obviously this can be a bit unsafe, so make this feature opt-in
for functions. Simply tag a function with KPROBE_ERROR_INJECT_SYMBOL in
order to give BPF access to that function for error
From: Josef Bacik
Using BPF we can override kprob'ed functions and return arbitrary
values. Obviously this can be a bit unsafe, so make this feature opt-in
for functions. Simply tag a function with KPROBE_ERROR_INJECT_SYMBOL in
order to give BPF access to that function for error injection
From: Josef Bacik
This was instrumental in reproducing a space cache bug.
Signed-off-by: Josef Bacik
Acked-by: Ingo Molnar
---
fs/btrfs/free-space-cache.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/btrfs/free-space-cache.c
From: Josef Bacik
This was instrumental in reproducing a space cache bug.
Signed-off-by: Josef Bacik
Acked-by: Ingo Molnar
---
fs/btrfs/free-space-cache.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/btrfs/free-space-cache.c b/fs/btrfs/free-space-cache.c
index
On Mon, Dec 11, 2017 at 07:30:33PM +0530, venkat.prashanth2...@gmail.com wrote:
> From: Venkat Prashanth B U
>
> This is the patch to the omap-dma.c file that fixes
> the following issues:
Thanks Venkat for the patch, but unforntunately it has some issues.
First
On Mon, Dec 11, 2017 at 07:30:33PM +0530, venkat.prashanth2...@gmail.com wrote:
> From: Venkat Prashanth B U
>
> This is the patch to the omap-dma.c file that fixes
> the following issues:
Thanks Venkat for the patch, but unforntunately it has some issues.
First a patch should do only one
From: Josef Bacik
This adds a basic test for bpf_override_return to verify it works. We
override the main function for mounting a btrfs fs so it'll return
-ENOMEM and then make sure that trying to mount a btrfs fs will fail.
Acked-by: Alexei Starovoitov
From: Josef Bacik
This allows us to do error injection with BPF for open_ctree.
Signed-off-by: Josef Bacik
Acked-by: Ingo Molnar
---
fs/btrfs/disk-io.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/btrfs/disk-io.c
From: Josef Bacik
This adds a basic test for bpf_override_return to verify it works. We
override the main function for mounting a btrfs fs so it'll return
-ENOMEM and then make sure that trying to mount a btrfs fs will fail.
Acked-by: Alexei Starovoitov
Acked-by: Ingo Molnar
Signed-off-by:
From: Josef Bacik
This allows us to do error injection with BPF for open_ctree.
Signed-off-by: Josef Bacik
Acked-by: Ingo Molnar
---
fs/btrfs/disk-io.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
index 10a2a579cc7f..02b5f5667754 100644
---
From: Josef Bacik
Error injection is sloppy and very ad-hoc. BPF could fill this niche
perfectly with it's kprobe functionality. We could make sure errors are
only triggered in specific call chains that we care about with very
specific situations. Accomplish this with the
From: Josef Bacik
Error injection is sloppy and very ad-hoc. BPF could fill this niche
perfectly with it's kprobe functionality. We could make sure errors are
only triggered in specific call chains that we care about with very
specific situations. Accomplish this with the
This is the same as v8, just rebased onto the bpf tree.
v8->v9:
- rebased onto the bpf tree.
v7->v8:
- removed the _ASM_KPROBE_ERROR_INJECT since it was not needed.
v6->v7:
- moved the opt-in macro to bpf.h out of kprobes.h.
v5->v6:
- add BPF_ALLOW_ERROR_INJECTION() tagging for functions that
This is the same as v8, just rebased onto the bpf tree.
v8->v9:
- rebased onto the bpf tree.
v7->v8:
- removed the _ASM_KPROBE_ERROR_INJECT since it was not needed.
v6->v7:
- moved the opt-in macro to bpf.h out of kprobes.h.
v5->v6:
- add BPF_ALLOW_ERROR_INJECTION() tagging for functions that
801 - 900 of 1744 matches
Mail list logo