On 05/07/16 17:38, Sebastian Frias wrote:
> Hi Jason,
>
> On 07/05/2016 05:53 PM, Jason Cooper wrote:
>>>
>>> Thanks for your comments.
>>> So, aside from some naming issues, do you think the driver is ok?
>>
>> Well, it's going to be few days before I can really dig in to this.
>> Until then,
On Tue, 5 Jul 2016 15:39:33 +0100
Juri Lelli wrote:
return;
> > >
> > > /*
> > > + * Use the scheduling parameters of the top pi-waiter task,
> > > + * if we have one from which we can inherit a deadline.
> > > + */
> > > + if (pi_task &&
On 05/07/16 17:38, Sebastian Frias wrote:
> Hi Jason,
>
> On 07/05/2016 05:53 PM, Jason Cooper wrote:
>>>
>>> Thanks for your comments.
>>> So, aside from some naming issues, do you think the driver is ok?
>>
>> Well, it's going to be few days before I can really dig in to this.
>> Until then,
On Tue, 5 Jul 2016 15:39:33 +0100
Juri Lelli wrote:
return;
> > >
> > > /*
> > > + * Use the scheduling parameters of the top pi-waiter task,
> > > + * if we have one from which we can inherit a deadline.
> > > + */
> > > + if (pi_task && dl_se->dl_boosted &&
On Tue, 5 Jul 2016 14:40:34 +0200
Frederic Weisbecker wrote:
> ...
Thanks for the review Frederic. Here is a fixed version of patch 1,
the other three still seem to apply cleanly.
---8<---
Subject: sched,time: count actually elapsed irq & softirq time
Currently, if there
On Tue, 5 Jul 2016 14:40:34 +0200
Frederic Weisbecker wrote:
> ...
Thanks for the review Frederic. Here is a fixed version of patch 1,
the other three still seem to apply cleanly.
---8<---
Subject: sched,time: count actually elapsed irq & softirq time
Currently, if there was any irq or
On Tue, Jul 5, 2016 at 5:49 PM, Mark Brown wrote:
> On Mon, Jun 27, 2016 at 09:54:07AM -0500, Franklin S Cooper Jr wrote:
>> Occasionally there are times you need to tweak a chained S/G list while
>> maintaining the original list. This function will duplicate the passed
>> in
On Tue, Jul 5, 2016 at 5:49 PM, Mark Brown wrote:
> On Mon, Jun 27, 2016 at 09:54:07AM -0500, Franklin S Cooper Jr wrote:
>> Occasionally there are times you need to tweak a chained S/G list while
>> maintaining the original list. This function will duplicate the passed
>> in chained S/G list and
On Jul 5, 2016, at 9:51 AM, Al Viro wrote:
> On Tue, Jul 05, 2016 at 01:31:10PM +0100, Al Viro wrote:
>> On Tue, Jul 05, 2016 at 02:22:48AM -0400, Oleg Drokin wrote:
>>
+ if (!(open_flags & O_CREAT) && !d_unhashed(dentry)) {
>>
>> s/d_unhashed/d_in_lookup/ in that.
>>
>>> So we come
On Jul 5, 2016, at 9:51 AM, Al Viro wrote:
> On Tue, Jul 05, 2016 at 01:31:10PM +0100, Al Viro wrote:
>> On Tue, Jul 05, 2016 at 02:22:48AM -0400, Oleg Drokin wrote:
>>
+ if (!(open_flags & O_CREAT) && !d_unhashed(dentry)) {
>>
>> s/d_unhashed/d_in_lookup/ in that.
>>
>>> So we come
Provide generic bindings for all Jedec JC-42.4 compatible temperature
sensor chips.
Signed-off-by: Guenter Roeck
---
Documentation/devicetree/bindings/hwmon/jc42.txt | 42
1 file changed, 42 insertions(+)
create mode 100644
With this change, JC-42.4 compatible temperature sensors can be configured
in devicetree by providing a generic "jedec,jc-42.4-temp" binding.
Signed-off-by: Guenter Roeck
---
drivers/hwmon/jc42.c | 10 ++
1 file changed, 10 insertions(+)
diff --git
Provide generic bindings for all Jedec JC-42.4 compatible temperature
sensor chips.
Signed-off-by: Guenter Roeck
---
Documentation/devicetree/bindings/hwmon/jc42.txt | 42
1 file changed, 42 insertions(+)
create mode 100644
With this change, JC-42.4 compatible temperature sensors can be configured
in devicetree by providing a generic "jedec,jc-42.4-temp" binding.
Signed-off-by: Guenter Roeck
---
drivers/hwmon/jc42.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/hwmon/jc42.c
The 'compatible = "nxp,jc42"' binding only happened to work because
the Linux driver is named jc42. The driver now supports generic
bindings for JC-42 compatible chips, so use the generic binding instead.
Cc: Ariel D'Alessandro
Cc: Joachim Eastwood
The 'compatible = "nxp,jc42"' binding only happened to work because
the Linux driver is named jc42. The driver now supports generic
bindings for JC-42 compatible chips, so use the generic binding instead.
Cc: Ariel D'Alessandro
Cc: Joachim Eastwood
Signed-off-by: Guenter Roeck
---
Hi Jason,
On 07/05/2016 05:53 PM, Jason Cooper wrote:
>>
>> Thanks for your comments.
>> So, aside from some naming issues, do you think the driver is ok?
>
> Well, it's going to be few days before I can really dig in to this.
> Until then, what I can say I see is that it looks like you're using
Hi Jason,
On 07/05/2016 05:53 PM, Jason Cooper wrote:
>>
>> Thanks for your comments.
>> So, aside from some naming issues, do you think the driver is ok?
>
> Well, it's going to be few days before I can really dig in to this.
> Until then, what I can say I see is that it looks like you're using
On Wed, Jun 22, 2016 at 11:57 AM, Quinn Tran wrote:
> Johannes, Martin,
>
> Based on the screen shot/call trace, it looks like this adapter is not using
> MSIX. It defaulted back to MSI or INTx interrupt. The code made an
> assumption of MSIX is available. There is
On 07/05/2016 08:48 AM, Rob Herring wrote:
On Sat, Jul 02, 2016 at 10:05:42AM -0700, Guenter Roeck wrote:
Provide generic bindings for all Jedec JC-42.4 compatible temperature
sensor chips.
Signed-off-by: Guenter Roeck
---
RFC to address:
- Is "jc-42-4" ok to use for
On Wed, Jun 22, 2016 at 11:57 AM, Quinn Tran wrote:
> Johannes, Martin,
>
> Based on the screen shot/call trace, it looks like this adapter is not using
> MSIX. It defaulted back to MSI or INTx interrupt. The code made an
> assumption of MSIX is available. There is no point in go through
On 07/05/2016 08:48 AM, Rob Herring wrote:
On Sat, Jul 02, 2016 at 10:05:42AM -0700, Guenter Roeck wrote:
Provide generic bindings for all Jedec JC-42.4 compatible temperature
sensor chips.
Signed-off-by: Guenter Roeck
---
RFC to address:
- Is "jc-42-4" ok to use for JC-42.4 ?
- JC42.4 really
Adds support for fixed-rate clock providers which have not been
enabled via of_clk_init().
This is required by Device trees overlays that introduce clocks
providers.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/clk/clk-fixed-rate.c | 69
Adds support for fixed-rate clock providers which have not been
enabled via of_clk_init().
This is required by Device trees overlays that introduce clocks
providers.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/clk/clk-fixed-rate.c | 69 +---
1
Signed-off-by: Arvind Yadav
---
drivers/input/keyboard/gpio_keys.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/input/keyboard/gpio_keys.c
b/drivers/input/keyboard/gpio_keys.c
index 2909365..a2fa3bb 100644
---
Signed-off-by: Arvind Yadav
---
drivers/input/keyboard/gpio_keys.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/input/keyboard/gpio_keys.c
b/drivers/input/keyboard/gpio_keys.c
index 2909365..a2fa3bb 100644
--- a/drivers/input/keyboard/gpio_keys.c
+++
This driver initializes a clock provider via lpc18xx_creg_clk_init
and then continues the initialization on lpc18xx_creg_clk_probe.
Use the new macro to notify the clk subsystem about this behaviour.
Signed-off-by: Ricardo Ribalda Delgado
---
This driver initializes a clock provider via of_artpec6_clkctrl_setup
and then continues the initialization on artpec6_clkctrl_probe.
Use the new macro to notify the clk subsystem about this behaviour.
Signed-off-by: Ricardo Ribalda Delgado
---
This driver initializes a clock provider via lpc18xx_creg_clk_init
and then continues the initialization on lpc18xx_creg_clk_probe.
Use the new macro to notify the clk subsystem about this behaviour.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/clk/nxp/clk-lpc18xx-creg.c | 3 ++-
1 file
This driver initializes a clock provider via of_artpec6_clkctrl_setup
and then continues the initialization on artpec6_clkctrl_probe.
Use the new macro to notify the clk subsystem about this behaviour.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/clk/axis/clk-artpec6.c | 4 ++--
1 file
This driver initializes a clock provider via sun4i_a10_mod0_setup
and then continues the initialization on sun4i_a10_mod0_clk_probe.
Use the new macro to notify the clk subsystem about this behaviour.
Signed-off-by: Ricardo Ribalda Delgado
---
This driver initializes a clock provider via sun4i_a10_mod0_setup
and then continues the initialization on sun4i_a10_mod0_clk_probe.
Use the new macro to notify the clk subsystem about this behaviour.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/clk/sunxi/clk-mod0.c | 3 ++-
1 file
This driver initializes a clock provider via sun8i_a23_apb0_setup
and then continues the initialization on sun8i_a23_apb0_clk_probe.
Use the new macro to notify the clk subsystem about this behaviour.
Signed-off-by: Ricardo Ribalda Delgado
---
This driver initializes a clock provider via sun8i_a23_apb0_setup
and then continues the initialization on sun8i_a23_apb0_clk_probe.
Use the new macro to notify the clk subsystem about this behaviour.
Signed-off-by: Ricardo Ribalda Delgado
---
This driver initializes a clock provider via sun8i_a23_apb0_setup
and then continues the initialization on sun8i_a23_apb0_clk_probe.
Use the new macro to notify the clk subsystem about this behaviour.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/clk/sunxi/clk-sun8i-apb0.c | 4 ++--
1
This driver initializes a clock provider via sun8i_a23_apb0_setup
and then continues the initialization on sun8i_a23_apb0_clk_probe.
Use the new macro to notify the clk subsystem about this behaviour.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/clk/sunxi/clk-sun8i-apb0.c | 4 ++--
1
This will be used by drivers that requires initialization at
of_clk_init() time and also during platform device probing.
Signed-off-by: Ricardo Ribalda Delgado
---
include/linux/clk-provider.h | 12
1 file changed, 12 insertions(+)
diff --git
Clock providers can be probed as a normal platform device, or via
of_clk_init() before the rest of the platform devices are initialized
using the CLK_OF_DECLARE() macro.
If a driver required both initialization methodologies, the core would call
both probe/init functions.
This changeset prevent
Some clock providers can be initialized via of_clk_init() and also via
platform device probe.
Avoid double initialization of them by setting the OF_POPULATED flag.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/clk/clk.c | 4
1 file changed, 4 insertions(+)
This will be used by drivers that requires initialization at
of_clk_init() time and also during platform device probing.
Signed-off-by: Ricardo Ribalda Delgado
---
include/linux/clk-provider.h | 12
1 file changed, 12 insertions(+)
diff --git a/include/linux/clk-provider.h
Clock providers can be probed as a normal platform device, or via
of_clk_init() before the rest of the platform devices are initialized
using the CLK_OF_DECLARE() macro.
If a driver required both initialization methodologies, the core would call
both probe/init functions.
This changeset prevent
Some clock providers can be initialized via of_clk_init() and also via
platform device probe.
Avoid double initialization of them by setting the OF_POPULATED flag.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/clk/clk.c | 4
1 file changed, 4 insertions(+)
diff --git
Adds support for fixed-factor clock providers which have not been
enabled via of_clk_init().
This is required by Device trees overlays that introduce clocks
providers.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/clk/clk-fixed-factor.c | 72
On 6/6/2016 12:53 PM, Rhyland Klein wrote:
> Check the return value of get_temp, which can fail. If it does, then
> unlock and return the error code.
>
> Signed-off-by: Rhyland Klein
> ---
> drivers/thermal/thermal_helpers.c | 4
> 1 file changed, 4 insertions(+)
>
>
On 6/6/2016 12:53 PM, Rhyland Klein wrote:
> Check the return value of get_temp, which can fail. If it does, then
> unlock and return the error code.
>
> Signed-off-by: Rhyland Klein
> ---
> drivers/thermal/thermal_helpers.c | 4
> 1 file changed, 4 insertions(+)
>
> diff --git
Adds support for fixed-factor clock providers which have not been
enabled via of_clk_init().
This is required by Device trees overlays that introduce clocks
providers.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/clk/clk-fixed-factor.c | 72 +++---
1
This driver initializes a clock provider via sun4i_a10_mod0_setup
and then continues the initialization on sun4i_a10_mod0_clk_probe.
Use the new macro to notify the clk subsystem about this behaviour.
Signed-off-by: Ricardo Ribalda Delgado
---
Hi,
[auto build test ERROR on hid/for-next]
[also build test ERROR on v4.7-rc6 next-20160705]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Benjamin-Tissoires/HID-wacom-cleanup-EKR-LED
Peter Chen writes:
> of_node_put needs to be called when the device node which is got
> from of_parse_phandle has finished using.
>
> Cc: Eric Anholt
> Signed-off-by: Peter Chen
> ---
> drivers/gpu/drm/vc4/vc4_hdmi.c | 13 +++--
On Mon, Jul 04, 2016 at 09:44:42PM +0530, Pratyush Anand wrote:
> From: Pratyush Anand
>
> Most of the platform have 3 or more viewports. We do not need to share
> viewport for such platform between IO and CFG. Assign viewport 2 to IO
> transactions in such cases.
>
>
This driver initializes a clock provider via sun4i_a10_mod0_setup
and then continues the initialization on sun4i_a10_mod0_clk_probe.
Use the new macro to notify the clk subsystem about this behaviour.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/clk/sunxi/clk-mod0.c | 3 ++-
1 file
Hi,
[auto build test ERROR on hid/for-next]
[also build test ERROR on v4.7-rc6 next-20160705]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Benjamin-Tissoires/HID-wacom-cleanup-EKR-LED
Peter Chen writes:
> of_node_put needs to be called when the device node which is got
> from of_parse_phandle has finished using.
>
> Cc: Eric Anholt
> Signed-off-by: Peter Chen
> ---
> drivers/gpu/drm/vc4/vc4_hdmi.c | 13 +++--
> 1 file changed, 7 insertions(+), 6 deletions(-)
>
>
On Mon, Jul 04, 2016 at 09:44:42PM +0530, Pratyush Anand wrote:
> From: Pratyush Anand
>
> Most of the platform have 3 or more viewports. We do not need to share
> viewport for such platform between IO and CFG. Assign viewport 2 to IO
> transactions in such cases.
>
> Signed-off-by: Pratyush
Exynos7 has the same CPU clock registers layout as that present
in Exynos5433 except for the bits in the MUX_STAT* registers.
Add a new CLK_CPU_HAS_MODIFIED_MUX_STAT flag to handle this change.
Signed-off-by: Abhilash Kesavan
---
drivers/clk/samsung/clk-cpu.c | 10
Exynos7 has the same CPU clock registers layout as that present
in Exynos5433 except for the bits in the MUX_STAT* registers.
Add a new CLK_CPU_HAS_MODIFIED_MUX_STAT flag to handle this change.
Signed-off-by: Abhilash Kesavan
---
drivers/clk/samsung/clk-cpu.c | 10 --
CMU_ATLAS generates all the necessary clocks for the Cortex-A57
block. Enable clock support for this block, which includes:
- addition of mux/divider/gate/pll clocks
- addition of CPU clocks configuration data
- instantiation of the atlas CPU clock
Signed-off-by: Abhilash
CMU_ATLAS generates all the necessary clocks for the Cortex-A57
block. Enable clock support for this block, which includes:
- addition of mux/divider/gate/pll clocks
- addition of CPU clocks configuration data
- instantiation of the atlas CPU clock
Signed-off-by: Abhilash
This patch set adds the atlas clock hierarchy on Exynos7. It also
modifies the existing cpu clock infrastructure to handle exynos7
differences. These patches are a pre-requisite for enabling CPUFreq
on Exynos7. This patchset has been tested on next-20160704. The
opp device tree changes, cpufreq-dt
This patch set adds the atlas clock hierarchy on Exynos7. It also
modifies the existing cpu clock infrastructure to handle exynos7
differences. These patches are a pre-requisite for enabling CPUFreq
on Exynos7. This patchset has been tested on next-20160704. The
opp device tree changes, cpufreq-dt
Add initial PMU settings for exynos7. This is required for
future suspend-to-ram and cpuidle support.
Signed-off-by: Eunseok Choi
Signed-off-by: Abhilash Kesavan
---
drivers/soc/samsung/Kconfig | 2 +-
drivers/soc/samsung/Makefile
Add support for the Power Management Unit on Exynos7. These patches
have been tested on an Exynos7 espresso board (next-20160704).
Abhilash Kesavan (2):
soc: samsung: Change type of PMU configuration register value to u32
soc: samsung: Add support for Exynos7 PMU
Exynos7 has certain PMU registers that needs to be configured with
u32 values.
Signed-off-by: Abhilash Kesavan
---
drivers/soc/samsung/exynos-pmu.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/soc/samsung/exynos-pmu.h
Add initial PMU settings for exynos7. This is required for
future suspend-to-ram and cpuidle support.
Signed-off-by: Eunseok Choi
Signed-off-by: Abhilash Kesavan
---
drivers/soc/samsung/Kconfig | 2 +-
drivers/soc/samsung/Makefile| 3 +-
Add support for the Power Management Unit on Exynos7. These patches
have been tested on an Exynos7 espresso board (next-20160704).
Abhilash Kesavan (2):
soc: samsung: Change type of PMU configuration register value to u32
soc: samsung: Add support for Exynos7 PMU
Exynos7 has certain PMU registers that needs to be configured with
u32 values.
Signed-off-by: Abhilash Kesavan
---
drivers/soc/samsung/exynos-pmu.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/soc/samsung/exynos-pmu.h b/drivers/soc/samsung/exynos-pmu.h
index
On 07/05/2016 08:56 AM, Mason wrote:
> On 05/07/2016 17:28, Florian Fainelli wrote:
>
>> nb8800.c does not currently show suspend/resume hooks implemented, are
>> you positive that when you suspend, you properly tear down all HW, stop
>> transmit queues, etc. and do the opposite upon resumption?
On 07/05/2016 08:56 AM, Mason wrote:
> On 05/07/2016 17:28, Florian Fainelli wrote:
>
>> nb8800.c does not currently show suspend/resume hooks implemented, are
>> you positive that when you suspend, you properly tear down all HW, stop
>> transmit queues, etc. and do the opposite upon resumption?
On Jul 5, 2016 5:35 AM, "Paul Burton" wrote:
>
> Hi PrasannaKumar,
>
>
> On 25/06/16 13:14, PrasannaKumar Muralidharan wrote:
>>
>> From: PrasannaKumar Muralidharan
>>
>> This patch adds support for context switching Xburst MXU registers. The
On Mon, Jul 04, 2016 at 03:47:30PM +0200, gabriel.fernan...@st.com wrote:
> From: Maxime Coquelin
>
> This adds documentation of device tree bindings for the
> STM32 reset controller.
>
> Signed-off-by: Maxime Coquelin
> ---
>
On Jul 5, 2016 5:35 AM, "Paul Burton" wrote:
>
> Hi PrasannaKumar,
>
>
> On 25/06/16 13:14, PrasannaKumar Muralidharan wrote:
>>
>> From: PrasannaKumar Muralidharan
>>
>> This patch adds support for context switching Xburst MXU registers. The
>> registers are named xr0 to xr16. xr16 is the
On Mon, Jul 04, 2016 at 03:47:30PM +0200, gabriel.fernan...@st.com wrote:
> From: Maxime Coquelin
>
> This adds documentation of device tree bindings for the
> STM32 reset controller.
>
> Signed-off-by: Maxime Coquelin
> ---
> .../devicetree/bindings/reset/st,stm32-rcc.txt | 50
>
Hi Mason,
On Tue, Jul 05, 2016 at 05:07:09PM +0200, Mason wrote:
> Jason Cooper wrote:
> > Sebastian Frias wrote:
> >> Mason wrote:
> >>> Sebastian Frias wrote:
> >>>
> .../sigma,smp87xx-irqrouter.txt| 69 +++
> >>>
> >>> In the *actual* submission, we can't use a
Hi Mason,
On Tue, Jul 05, 2016 at 05:07:09PM +0200, Mason wrote:
> Jason Cooper wrote:
> > Sebastian Frias wrote:
> >> Mason wrote:
> >>> Sebastian Frias wrote:
> >>>
> .../sigma,smp87xx-irqrouter.txt| 69 +++
> >>>
> >>> In the *actual* submission, we can't use a
Hi Andrew/Chris-
Please find attached patches to add firmware update via the F34 function
to the RMI4 driver.
I've now resolved all issues that I was aware of in my testing, would
appreciate any input.
Git tree here:
https://github.com/ndyer/linux/commits/synaptics-fw-update-2016-07-05
best
Signed-off-by: Nick Dyer
---
drivers/input/rmi4/Kconfig | 11 ++
drivers/input/rmi4/Makefile | 1 +
drivers/input/rmi4/rmi_bus.c| 3 +
drivers/input/rmi4/rmi_driver.c | 146 +-
drivers/input/rmi4/rmi_driver.h | 6 +
drivers/input/rmi4/rmi_f01.c
---
drivers/input/rmi4/rmi_driver.c | 139 +---
1 file changed, 86 insertions(+), 53 deletions(-)
diff --git a/drivers/input/rmi4/rmi_driver.c b/drivers/input/rmi4/rmi_driver.c
index faa295e..543cf7a 100644
--- a/drivers/input/rmi4/rmi_driver.c
+++
Hi Andrew/Chris-
Please find attached patches to add firmware update via the F34 function
to the RMI4 driver.
I've now resolved all issues that I was aware of in my testing, would
appreciate any input.
Git tree here:
https://github.com/ndyer/linux/commits/synaptics-fw-update-2016-07-05
best
Signed-off-by: Nick Dyer
---
drivers/input/rmi4/Kconfig | 11 ++
drivers/input/rmi4/Makefile | 1 +
drivers/input/rmi4/rmi_bus.c| 3 +
drivers/input/rmi4/rmi_driver.c | 146 +-
drivers/input/rmi4/rmi_driver.h | 6 +
drivers/input/rmi4/rmi_f01.c| 6 +
---
drivers/input/rmi4/rmi_driver.c | 139 +---
1 file changed, 86 insertions(+), 53 deletions(-)
diff --git a/drivers/input/rmi4/rmi_driver.c b/drivers/input/rmi4/rmi_driver.c
index faa295e..543cf7a 100644
--- a/drivers/input/rmi4/rmi_driver.c
+++
Hi,
[auto build test ERROR on hid/for-next]
[also build test ERROR on v4.7-rc6 next-20160705]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Benjamin-Tissoires/HID-wacom-cleanup-EKR-LED
Hi,
[auto build test ERROR on hid/for-next]
[also build test ERROR on v4.7-rc6 next-20160705]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Benjamin-Tissoires/HID-wacom-cleanup-EKR-LED
On Tue, Jul 5, 2016 at 5:42 PM, Alan Stern wrote:
> On Tue, 5 Jul 2016, Dmitry Vyukov wrote:
>
>> Hello,
>>
>> The following program trigger the following WARNING:
>>
>> [ cut here ]
>> WARNING: CPU: 0 PID: 6263 at mm/page_alloc.c:3584[<
On Tue, Jul 5, 2016 at 5:42 PM, Alan Stern wrote:
> On Tue, 5 Jul 2016, Dmitry Vyukov wrote:
>
>> Hello,
>>
>> The following program trigger the following WARNING:
>>
>> [ cut here ]
>> WARNING: CPU: 0 PID: 6263 at mm/page_alloc.c:3584[< inline >]
>>
On 05/07/2016 17:28, Florian Fainelli wrote:
> nb8800.c does not currently show suspend/resume hooks implemented, are
> you positive that when you suspend, you properly tear down all HW, stop
> transmit queues, etc. and do the opposite upon resumption?
I am currently testing the error path for
On 05/07/2016 17:28, Florian Fainelli wrote:
> nb8800.c does not currently show suspend/resume hooks implemented, are
> you positive that when you suspend, you properly tear down all HW, stop
> transmit queues, etc. and do the opposite upon resumption?
I am currently testing the error path for
On Thu, 2016-06-30 at 15:47 +0200, Andreas Gruenbacher wrote:
> POSIX ACLs and richacls are both objects allocated by kmalloc() with a
> reference count which are freed by kfree_rcu(). An inode can either
> cache an access and a default POSIX ACL, or a richacl (richacls do not
> have default
On Thu, 2016-06-30 at 15:47 +0200, Andreas Gruenbacher wrote:
> POSIX ACLs and richacls are both objects allocated by kmalloc() with a
> reference count which are freed by kfree_rcu(). An inode can either
> cache an access and a default POSIX ACL, or a richacl (richacls do not
> have default
Provide a security hook which is called when xattrs of a file are being
copied up. This hook is called once for each xattr and one can either
accept or reject xattr. If 0 is returned, xattr will be copied up, if 1
is returned, xattr will not be copied up and if negative error code
is returned,
Right now selinux_determine_inode_label() works on security pointer of
current task. Soon I need this to work on a security pointer retrieved
from a set of creds. So start passing in a pointer and caller can decide
where to fetch security pointer from.
Signed-off-by: Vivek Goyal
Provide a security hook which is called when xattrs of a file are being
copied up. This hook is called once for each xattr and one can either
accept or reject xattr. If 0 is returned, xattr will be copied up, if 1
is returned, xattr will not be copied up and if negative error code
is returned,
Right now selinux_determine_inode_label() works on security pointer of
current task. Soon I need this to work on a security pointer retrieved
from a set of creds. So start passing in a pointer and caller can decide
where to fetch security pointer from.
Signed-off-by: Vivek Goyal
---
Hey Sebastian,
On Tue, Jul 05, 2016 at 05:18:42PM +0200, Sebastian Frias wrote:
> On 07/05/2016 04:41 PM, Jason Cooper wrote:
> > On Tue, Jul 05, 2016 at 02:30:12PM +0200, Sebastian Frias wrote:
> >> On 07/04/2016 02:11 PM, Mason wrote:
> > ...
> .../sigma,smp87xx-irqrouter.txt
Hey Sebastian,
On Tue, Jul 05, 2016 at 05:18:42PM +0200, Sebastian Frias wrote:
> On 07/05/2016 04:41 PM, Jason Cooper wrote:
> > On Tue, Jul 05, 2016 at 02:30:12PM +0200, Sebastian Frias wrote:
> >> On 07/04/2016 02:11 PM, Mason wrote:
> > ...
> .../sigma,smp87xx-irqrouter.txt
ovl_getxattr() currently uses vfs_getxattr() on realinode. This fails
if mounter does not have DAC/MAC permission to access getxattr.
Specifically this becomes a problem when selinux is trying to initialize
overlay inode and does ->getxattr(overlay_inode). A task might trigger
initialization of
Subject: [PATCH v5 1/3] LSM: Add /sys/kernel/security/lsm
I got tired of having to find indirect ways to
determine what security modules are active on a system.
I have added /sys/kernel/security/lsm, which contains a
comma separated list of the active security modules. No
more groping around in
ovl_getxattr() currently uses vfs_getxattr() on realinode. This fails
if mounter does not have DAC/MAC permission to access getxattr.
Specifically this becomes a problem when selinux is trying to initialize
overlay inode and does ->getxattr(overlay_inode). A task might trigger
initialization of
Subject: [PATCH v5 1/3] LSM: Add /sys/kernel/security/lsm
I got tired of having to find indirect ways to
determine what security modules are active on a system.
I have added /sys/kernel/security/lsm, which contains a
comma separated list of the active security modules. No
more groping around in
Subject: [PATCH v5 3/3] LSM: Add context interface for proc attrs
The /proc/.../attr/current interface is used by all three
Linux security modules (SELinux, Smack and AppArmor) to
report and modify the process security attribute. This is
all fine when there is exactly one of these modules active
Subject: [PATCH v5 2/3] LSM: module hierarchy in /proc/.../attr
Back in 2007 I made what turned out to be a rather serious
mistake in the implementation of the Smack security module.
The SELinux module used an interface in /proc to manipulate
the security context on processes. Rather than use a
501 - 600 of 1352 matches
Mail list logo