On Fri, Jan 29, 2016 at 11:25:29AM -0800, Brian Norris wrote:
> Hi,
>
> These are an assortment of fixes and updates to the SPI NOR lock/unlock
> feature. The biggest new features are:
> (a) Status Register protection; I don't see why this shouldn't be enabled by
> default. See patch 4's
On Fri, Jan 29, 2016 at 11:25:29AM -0800, Brian Norris wrote:
> Hi,
>
> These are an assortment of fixes and updates to the SPI NOR lock/unlock
> feature. The biggest new features are:
> (a) Status Register protection; I don't see why this shouldn't be enabled by
> default. See patch 4's
> "Lee" == Lee Duncan writes:
Lee> It looks like Mike and Chris are good with it.
However, it received no formal reviews or acked-bys...
--
Martin K. Petersen Oracle Linux Engineering
> "Lee" == Lee Duncan writes:
Lee> It looks like Mike and Chris are good with it.
However, it received no formal reviews or acked-bys...
--
Martin K. Petersen Oracle Linux Engineering
On Mon, Feb 29, 2016 at 05:35:02PM -0300, Ezequiel Garcia wrote:
> On 29 January 2016 at 16:25, Brian Norris wrote:
> > Some flash support a bit in the status register that inverts protection
> > so that it applies to the bottom of the flash, not the top. This yields
On 2016/3/7 21:37, Paul E. McKenney wrote:
> On Mon, Mar 07, 2016 at 03:02:05PM +0800, Kefeng Wang wrote:
>>
>>
>> On 2016/3/7 13:40, Davidlohr Bueso wrote:
>>> On Mon, 07 Mar 2016, Kefeng Wang wrote:
On 2016/3/3 16:36, Davidlohr Bueso wrote:
>>>
> +/*
> + * Indicates early
On Mon, Feb 29, 2016 at 05:35:02PM -0300, Ezequiel Garcia wrote:
> On 29 January 2016 at 16:25, Brian Norris wrote:
> > Some flash support a bit in the status register that inverts protection
> > so that it applies to the bottom of the flash, not the top. This yields
> > additions to the
On 2016/3/7 21:37, Paul E. McKenney wrote:
> On Mon, Mar 07, 2016 at 03:02:05PM +0800, Kefeng Wang wrote:
>>
>>
>> On 2016/3/7 13:40, Davidlohr Bueso wrote:
>>> On Mon, 07 Mar 2016, Kefeng Wang wrote:
On 2016/3/3 16:36, Davidlohr Bueso wrote:
>>>
> +/*
> + * Indicates early
On Fri, 2016-03-04 at 15:01 +, David Howells wrote:
> Add a secondary system keyring that can be added to by root whilst the
> system is running - provided the key being added is vouched for by a key
> built into the kernel or already added to the secondary keyring.
>
> Rename .system_keyring
On Fri, 2016-03-04 at 15:01 +, David Howells wrote:
> Add a secondary system keyring that can be added to by root whilst the
> system is running - provided the key being added is vouched for by a key
> built into the kernel or already added to the secondary keyring.
>
> Rename .system_keyring
Hi Fengguang Wu,
Thank you for your patch.
> -Original Message-
> From: kbuild test robot [mailto:l...@intel.com]
> Sent: 2016年3月8日 7:54
> To: Yang, Wenyou
> Cc: kbuild-...@01.org; Lee Jones ; Rob Herring
> ; Pawel Moll
Hi Fengguang Wu,
Thank you for your patch.
> -Original Message-
> From: kbuild test robot [mailto:l...@intel.com]
> Sent: 2016年3月8日 7:54
> To: Yang, Wenyou
> Cc: kbuild-...@01.org; Lee Jones ; Rob Herring
> ; Pawel Moll ; Mark Rutland
> ; Ian Campbell ; Kumar
> Gala ; Ferre, Nicolas ;
>
On 2016/3/8 2:42, Laura Abbott wrote:
> On 03/07/2016 12:16 AM, Leizhen (ThunderTown) wrote:
>>
>>
>> On 2016/3/7 12:34, Joonsoo Kim wrote:
>>> On Fri, Mar 04, 2016 at 03:35:26PM +0800, Hanjun Guo wrote:
On 2016/3/4 14:38, Joonsoo Kim wrote:
> On Fri, Mar 04, 2016 at 02:05:09PM +0800,
On 2016/3/8 2:42, Laura Abbott wrote:
> On 03/07/2016 12:16 AM, Leizhen (ThunderTown) wrote:
>>
>>
>> On 2016/3/7 12:34, Joonsoo Kim wrote:
>>> On Fri, Mar 04, 2016 at 03:35:26PM +0800, Hanjun Guo wrote:
On 2016/3/4 14:38, Joonsoo Kim wrote:
> On Fri, Mar 04, 2016 at 02:05:09PM +0800,
On Tue, 08 Mar 2016 10:20:22 +1100
Michael Ellerman wrote:
> >
> > There is one remaining issue which I think would be really nice to
> > have(TM), and that's Steven's Ack for the whole thing :)
>
> Yeah. He's been on CC the whole time, but he's probably getting a bit
On Tue, 08 Mar 2016 10:20:22 +1100
Michael Ellerman wrote:
> >
> > There is one remaining issue which I think would be really nice to
> > have(TM), and that's Steven's Ack for the whole thing :)
>
> Yeah. He's been on CC the whole time, but he's probably getting a bit sick of
> it all, as
On Monday, March 07, 2016 03:53:13 PM Chen, Yu C wrote:
> Hi Rafael,
> (resend for broken content)
>
> > -Original Message-
> > From: rjwyso...@gmail.com [mailto:rjwyso...@gmail.com] On Behalf Of
> > Rafael J. Wysocki
> > Sent: Monday, March 07, 2016 9:19 PM
> > To: Chen, Yu C
> > Cc:
On Monday, March 07, 2016 03:53:13 PM Chen, Yu C wrote:
> Hi Rafael,
> (resend for broken content)
>
> > -Original Message-
> > From: rjwyso...@gmail.com [mailto:rjwyso...@gmail.com] On Behalf Of
> > Rafael J. Wysocki
> > Sent: Monday, March 07, 2016 9:19 PM
> > To: Chen, Yu C
> > Cc:
Add fast_restart node as a pmc's child node to support fast startup
signal configuration.
Signed-off-by: Wenyou Yang
---
Changes in v4:
- add fast_restart node to the DT file.
Changes in v3: None
Changes in v2: None
arch/arm/boot/dts/at91-sama5d2_xplained.dts |8
Add fast_restart node as a pmc's child node to support fast startup
signal configuration.
Signed-off-by: Wenyou Yang
---
Changes in v4:
- add fast_restart node to the DT file.
Changes in v3: None
Changes in v2: None
arch/arm/boot/dts/at91-sama5d2_xplained.dts |8
1 file
Add DT bindings to configurate the PMC_FSMR and PMC_FSPR registers
to trigger a fast restart signal to PMC.
Signed-off-by: Wenyou Yang
Acked-by: Rob Herring
---
Changes in v4:
- add Acked-by tag.
Changes in v3:
- update the property description.
Add DT bindings to configurate the PMC_FSMR and PMC_FSPR registers
to trigger a fast restart signal to PMC.
Signed-off-by: Wenyou Yang
Acked-by: Rob Herring
---
Changes in v4:
- add Acked-by tag.
Changes in v3:
- update the property description.
Changes in v2:
- change the property name
From: Ian Munsie
This adds an afu_driver_ops structure with event_pending and
deliver_event callbacks. An AFU driver such as cxlflash can fill these
out and associate it with a context to enable passing custom AFU
specific events to userspace.
The cxl driver will call
From: Ian Munsie
This adds an afu_driver_ops structure with event_pending and
deliver_event callbacks. An AFU driver such as cxlflash can fill these
out and associate it with a context to enable passing custom AFU
specific events to userspace.
The cxl driver will call event_pending() during
From: Michael Neuling
This provides AFU drivers a means to associate private data with a cxl
context. This is particularly intended for make the new callbacks for
driver specific events easier for AFU drivers to use, as they can easily
get back to any private data structures
From: Michael Neuling
This provides AFU drivers a means to associate private data with a cxl
context. This is particularly intended for make the new callbacks for
driver specific events easier for AFU drivers to use, as they can easily
get back to any private data structures they may use.
The fast startup signal is used as wake up sources for ULP1 mode.
As soon as a fast startup signal is asserted, the embedded 12 MHz
RC oscillator restarts automatically.
This patch is to configure the fast startup signals, which signal
is enabled to trigger the PMC to wake up the system from ULP1
The fast startup signal is used as wake up sources for ULP1 mode.
As soon as a fast startup signal is asserted, the embedded 12 MHz
RC oscillator restarts automatically.
This patch is to configure the fast startup signals, which signal
is enabled to trigger the PMC to wake up the system from ULP1
The ULP1 (Ultra Low-power mode 1) is introduced by SAMA5D2.
In the ULP1 mode, all the clocks are shut off, inclusive the embedded
12MHz RC oscillator, so as to achieve the lowest power consumption
with the system in retention mode and able to resume on the wake up
events. As soon as the wake up
The ULP1 (Ultra Low-power mode 1) is introduced by SAMA5D2.
In the ULP1 mode, all the clocks are shut off, inclusive the embedded
12MHz RC oscillator, so as to achieve the lowest power consumption
with the system in retention mode and able to resume on the wake up
events. As soon as the wake up
I found that page-types is very slow and my testing shows many timeout errors.
Here's an example with a simple program allocating 1000 thps.
$ time ./page-types -p $(pgrep -f test_alloc)
...
real0m17.201s
user0m16.889s
sys 0m0.312s
$ time ./page-types.patched -p $(pgrep
To make the code more legible and prepare to add the ULP1 mode
support in the future, create a separate procedure for the ULP0 mode.
Signed-off-by: Wenyou Yang
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
arch/arm/mach-at91/pm_suspend.S | 65
I found that page-types is very slow and my testing shows many timeout errors.
Here's an example with a simple program allocating 1000 thps.
$ time ./page-types -p $(pgrep -f test_alloc)
...
real0m17.201s
user0m16.889s
sys 0m0.312s
$ time ./page-types.patched -p $(pgrep
To make the code more legible and prepare to add the ULP1 mode
support in the future, create a separate procedure for the ULP0 mode.
Signed-off-by: Wenyou Yang
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
arch/arm/mach-at91/pm_suspend.S | 65
The ULP1 (Ultra Low-power mode 1) is introduced by SAMA5D2.
In order to achieve the lowest power consumption, in the ULP1 mode,
all the clocks are shut off, inclusive the embedded 12MHz RC oscillator.
The fast startup signal is used as a wake up source for ULP1 mode.
As soon as the wake up event
The ULP1 (Ultra Low-power mode 1) is introduced by SAMA5D2.
In order to achieve the lowest power consumption, in the ULP1 mode,
all the clocks are shut off, inclusive the embedded 12MHz RC oscillator.
The fast startup signal is used as a wake up source for ULP1 mode.
As soon as the wake up event
On Thu, Mar 03, 2016 at 10:06:54AM -0500, Tejun Heo wrote:
> All the prerequisite patches are now available in cgroup/for-4.6
> branch.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-4.6
>
> If the perf_event changes look okay, we can either apply the first
> patch to
Excerpts from Matt Ochs's message of 2016-03-08 11:26:55 +1100:
> Any reason for adding these extra lines as part of this commit?
mpe asked for some newlines here in the v1 submission, and it only
really made sense to do so if all the related sections had consistent
whitespace as well.
> > +/*
>
On Thu, Mar 03, 2016 at 10:06:54AM -0500, Tejun Heo wrote:
> All the prerequisite patches are now available in cgroup/for-4.6
> branch.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-4.6
>
> If the perf_event changes look okay, we can either apply the first
> patch to
Excerpts from Matt Ochs's message of 2016-03-08 11:26:55 +1100:
> Any reason for adding these extra lines as part of this commit?
mpe asked for some newlines here in the v1 submission, and it only
really made sense to do so if all the related sections had consistent
whitespace as well.
> > +/*
>
On 2016/3/4 13:33, Hanjun Guo wrote:
> Hi Joonsoo,
>
> On 2016/3/4 10:02, Joonsoo Kim wrote:
>> On Thu, Mar 03, 2016 at 08:49:01PM +0800, Hanjun Guo wrote:
>>> On 2016/3/3 15:42, Joonsoo Kim wrote:
2016-03-03 10:25 GMT+09:00 Laura Abbott :
> (cc -mm and Joonsoo Kim)
On 2016/3/4 13:33, Hanjun Guo wrote:
> Hi Joonsoo,
>
> On 2016/3/4 10:02, Joonsoo Kim wrote:
>> On Thu, Mar 03, 2016 at 08:49:01PM +0800, Hanjun Guo wrote:
>>> On 2016/3/3 15:42, Joonsoo Kim wrote:
2016-03-03 10:25 GMT+09:00 Laura Abbott :
> (cc -mm and Joonsoo Kim)
>
>
> On
On 2016/3/8 6:59, Andrew Morton wrote:
> On Mon, 7 Mar 2016 18:43:47 +0800 "Leizhen (ThunderTown)"
> wrote:
>
>> Suppose:
>> CONFIG_SPARSEMEM is opened.
>> CONFIG_DMA_API_DEBUG or CONFIG_CMA is opened.
>>
>> Then virt_to_page or phys_to_page will be called.
On 2016/3/8 6:59, Andrew Morton wrote:
> On Mon, 7 Mar 2016 18:43:47 +0800 "Leizhen (ThunderTown)"
> wrote:
>
>> Suppose:
>> CONFIG_SPARSEMEM is opened.
>> CONFIG_DMA_API_DEBUG or CONFIG_CMA is opened.
>>
>> Then virt_to_page or phys_to_page will be called. Finally, in __pfn_to_page,
>>
On 03/07/2016 10:39 AM, Khalid Aziz wrote:
On 03/07/2016 11:12 AM, Dave Hansen wrote:
On 03/07/2016 09:53 AM, Andy Lutomirski wrote:
Also, what am I missing? Tying these tags to the physical page seems
like a poor design to me. This seems really awkward to use.
Yeah, can you describe the
On 03/07/2016 10:39 AM, Khalid Aziz wrote:
On 03/07/2016 11:12 AM, Dave Hansen wrote:
On 03/07/2016 09:53 AM, Andy Lutomirski wrote:
Also, what am I missing? Tying these tags to the physical page seems
like a poor design to me. This seems really awkward to use.
Yeah, can you describe the
From: Vignesh R
Add hwmod entries for the PWMSS on DRA7.
Set l4_root_clk_div as the main_clk of PWMSS. It is fixed-factored clock
equal to L4PER2_L3_GICLK/2(l3_iclk_div/2).
Signed-off-by: Vignesh R
[fcoo...@ti.com: Do not add eQEP, ePWM and eCAP hwmod
Devices that utilize the OCP registers and/or PRCM registers and
register bit fields should be modelled using hwmod. Since eQEP, ePWM and
eCAP don't fall under this category, remove their hwmod entries.
Instead these clocks simply use the clock that is pass through by its
parent PWMSS. Therefore,
ECAP and ePWM do not have OCP integration registers, have L3/L4 ports, etc.
Therefore, they shouldn't be using hwmod at all. Remove their hwmod
properties.
For ePWM add the tbclk to the node rather than depending on hwmod to do so.
Signed-off-by: Franklin S Cooper Jr
---
From: Vignesh R
Add PWMSS device tree nodes for DRA7 SoC family and add documentation
for dt bindings.
Signed-off-by: Vignesh R
[fcoo...@ti.com: Add eCAP and use updated bindings for PWMSS and ePWM]
Signed-off-by: Franklin S Cooper Jr
---
This patch series adds support for PWM for DRA7. The IP is same as that
present in AM33XX and AM437XX.
However, before doing so remove unnecessary hwmod entries for eCAP, ePWM
and eQEP.
This series is almost identical to v4. Only difference is the addition of
eCAP DT nodes in the dra7.dtsi file.
From: Vignesh R
Add hwmod entries for the PWMSS on DRA7.
Set l4_root_clk_div as the main_clk of PWMSS. It is fixed-factored clock
equal to L4PER2_L3_GICLK/2(l3_iclk_div/2).
Signed-off-by: Vignesh R
[fcoo...@ti.com: Do not add eQEP, ePWM and eCAP hwmod entries]
Signed-off-by: Franklin S Cooper
Devices that utilize the OCP registers and/or PRCM registers and
register bit fields should be modelled using hwmod. Since eQEP, ePWM and
eCAP don't fall under this category, remove their hwmod entries.
Instead these clocks simply use the clock that is pass through by its
parent PWMSS. Therefore,
ECAP and ePWM do not have OCP integration registers, have L3/L4 ports, etc.
Therefore, they shouldn't be using hwmod at all. Remove their hwmod
properties.
For ePWM add the tbclk to the node rather than depending on hwmod to do so.
Signed-off-by: Franklin S Cooper Jr
---
From: Vignesh R
Add PWMSS device tree nodes for DRA7 SoC family and add documentation
for dt bindings.
Signed-off-by: Vignesh R
[fcoo...@ti.com: Add eCAP and use updated bindings for PWMSS and ePWM]
Signed-off-by: Franklin S Cooper Jr
---
Version 5 changes:
Add DT node for eCAP and update
This patch series adds support for PWM for DRA7. The IP is same as that
present in AM33XX and AM437XX.
However, before doing so remove unnecessary hwmod entries for eCAP, ePWM
and eQEP.
This series is almost identical to v4. Only difference is the addition of
eCAP DT nodes in the dra7.dtsi file.
From: Vignesh R
tbclk is used by ehrpwm to generate PWM waveform on DRA7 SoC. Add Linux
clock to control ehrpwm tbclk.
The TRM says, tbclk is derived from SYSCLKOUT. SYSCLKOUT is nothing but
ehrpwm functional clock derived from the gateable interface and
functional clock of
The eCAP and ePWM doesn't have their own separate clocks. They simply
utilize the clock provided directly by the PWMSS. Therefore, they simply
need to grab a reference to their parent's clock.
Signed-off-by: Franklin S Cooper Jr
---
drivers/pwm/pwm-tiecap.c | 2 +-
From: Vignesh R
tbclk is used by ehrpwm to generate PWM waveform on DRA7 SoC. Add Linux
clock to control ehrpwm tbclk.
The TRM says, tbclk is derived from SYSCLKOUT. SYSCLKOUT is nothing but
ehrpwm functional clock derived from the gateable interface and
functional clock of
The eCAP and ePWM doesn't have their own separate clocks. They simply
utilize the clock provided directly by the PWMSS. Therefore, they simply
need to grab a reference to their parent's clock.
Signed-off-by: Franklin S Cooper Jr
---
drivers/pwm/pwm-tiecap.c | 2 +-
drivers/pwm/pwm-tiehrpwm.c
On Tue, Mar 08, 2016 at 1:28AM, Scott Wood wrote:
> -Original Message-
> From: Scott Wood [mailto:o...@buserror.net]
> Sent: Tuesday, March 08, 2016 1:28 AM
> To: Qiang Zhao ; Rob Herring
> Cc: Yang-Leo Li ; Xiaobo Xie
On Tue, Mar 08, 2016 at 1:28AM, Scott Wood wrote:
> -Original Message-
> From: Scott Wood [mailto:o...@buserror.net]
> Sent: Tuesday, March 08, 2016 1:28 AM
> To: Qiang Zhao ; Rob Herring
> Cc: Yang-Leo Li ; Xiaobo Xie ;
> linux-kernel@vger.kernel.org; devicet...@vger.kernel.org;
> -Original Message-
> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
> Sent: Monday, March 7, 2016 3:00 AM
> To: linux-s...@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org; KY
> Srinivasan ; Haiyang Zhang
>
> -Original Message-
> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
> Sent: Monday, March 7, 2016 3:00 AM
> To: linux-s...@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org; KY
> Srinivasan ; Haiyang Zhang
> ; Cathy Avery ; James E.J.
> Bottomley ;
On Wed, 24 Feb 2016 13:31:34 -0800
Jacob Pan wrote:
> Changes since v5:
> - Split changes into seprate patches. No code change.
> Changes since V4:
> - Deleted unnecessary cpumask_any_and() call, assign first
> cpu as lead Changes since V3:
> -
+++ Andrew Morton [07/03/16 15:24 -0800]:
On Mon, 7 Mar 2016 18:12:20 -0500 Jessica Yu wrote:
+++ Jessica Yu [26/02/16 15:28 -0500]:
>+++ Jessica Yu [26/02/16 15:20 -0500]:
>>Implement basic character sets for the '%[' conversion specifier.
>>
>>The '%[' conversion specifier
On Wed, 24 Feb 2016 13:31:34 -0800
Jacob Pan wrote:
> Changes since v5:
> - Split changes into seprate patches. No code change.
> Changes since V4:
> - Deleted unnecessary cpumask_any_and() call, assign first
> cpu as lead Changes since V3:
> - Avoid for_each_online_cpu()
+++ Andrew Morton [07/03/16 15:24 -0800]:
On Mon, 7 Mar 2016 18:12:20 -0500 Jessica Yu wrote:
+++ Jessica Yu [26/02/16 15:28 -0500]:
>+++ Jessica Yu [26/02/16 15:20 -0500]:
>>Implement basic character sets for the '%[' conversion specifier.
>>
>>The '%[' conversion specifier matches a
A couple of the EDAC drivers have a nice memdev_dmi_entry structure for
decoding DMI memory device entries. Move the structure definition to
dmi.h so that it can be shared between those drivers and also other
parts of the kernel; the i915 graphics driver is going to need to use
this structure
A couple of the EDAC drivers have a nice memdev_dmi_entry structure for
decoding DMI memory device entries. Move the structure definition to
dmi.h so that it can be shared between those drivers and also other
parts of the kernel; the i915 graphics driver is going to need to use
this structure
On 02/12/2016 09:54 AM, James Bottomley wrote:
> On Fri, 2016-02-12 at 09:38 -0800, Lee Duncan wrote:
>> The scsi_transport_iscsi module already uses the ida_simple
>> routines for managing the target ID, if requested to do
>> so. This change replaces an ever-increasing atomic integer
>> that
On 02/12/2016 09:54 AM, James Bottomley wrote:
> On Fri, 2016-02-12 at 09:38 -0800, Lee Duncan wrote:
>> The scsi_transport_iscsi module already uses the ida_simple
>> routines for managing the target ID, if requested to do
>> so. This change replaces an ever-increasing atomic integer
>> that
From: David Rivshin
This adds a binding description for the is31fl3236/35/18/16 I2C LED
controllers.
Signed-off-by: David Rivshin
Acked-by: Rob Herring
---
Changes from v1:
- swapped node name and label in example
- added Rob's
From: David Rivshin
Si-En Technology was acquired by ISSI in 2011, and it appears that
the IS31FL3218/IS31FL3216 are just rebranded SN3218/SN3216 devices.
Add the "si-en,sn3218" and "si-en,sn3216" compatible strings into the
IS31FL32XX driver as aliases for the issi
From: David Rivshin
This adds a binding description for the is31fl3236/35/18/16 I2C LED
controllers.
Signed-off-by: David Rivshin
Acked-by: Rob Herring
---
Changes from v1:
- swapped node name and label in example
- added Rob's ack (given above fix) [1]
Changes from RFC:
- Removed
From: David Rivshin
Si-En Technology was acquired by ISSI in 2011, and it appears that
the IS31FL3218/IS31FL3216 are just rebranded SN3218/SN3216 devices.
Add the "si-en,sn3218" and "si-en,sn3216" compatible strings into the
IS31FL32XX driver as aliases for the issi equivalents, and update
From: David Rivshin
The IS31FL32xx family of LED controllers are I2C devices with multiple
constant-current channels, each with independent 256-level PWM control.
Datasheets: http://www.issi.com/US/product-analog-fxled-driver.shtml
This has been tested on the IS31FL3236
From: David Rivshin
The IS31FL32xx family of LED controllers are I2C devices with multiple
constant-current channels, each with independent 256-level PWM control.
Datasheets: http://www.issi.com/US/product-analog-fxled-driver.shtml
This has been tested on the IS31FL3236 and IS31FL3216, on an
From: David Rivshin
ISSI is the stock ticker Integrated Silicon Solutions Inc.
Company website: http://www.issi.com
Signed-off-by: David Rivshin
Acked-by: Rob Herring
---
Changes from v1:
- added Rob's ack [1]
Changes from RFC:
From: David Rivshin
This series adds support for the ISSI IS31FL32xx family of I2C LED
controllers. Since the IS31FL3218/3216 are actually the same devices as
the SN3218/3216, adds their compatible strings as aliases.
As requested, this series is based on the current
From: David Rivshin
ISSI is the stock ticker Integrated Silicon Solutions Inc.
Company website: http://www.issi.com
Signed-off-by: David Rivshin
Acked-by: Rob Herring
---
Changes from v1:
- added Rob's ack [1]
Changes from RFC:
none
[1] https://lkml.org/lkml/2016/3/4/961
From: David Rivshin
This series adds support for the ISSI IS31FL32xx family of I2C LED
controllers. Since the IS31FL3218/3216 are actually the same devices as
the SN3218/3216, adds their compatible strings as aliases.
As requested, this series is based on the current linux-leds/for-next, minus
Hi, Chris
> From: linux-acpi-ow...@vger.kernel.org [mailto:linux-acpi-
> Subject: Re: [PATCH] ACPICA: Events: Execute some _REG methods in early
> boot
>
> On Mon, Mar 07, 2016 at 06:36:05AM +, Zheng, Lv wrote:
> > Hi,
> >
> > First of all, why don't you respond on the kernel bugzilla?
> >
Hi, Chris
> From: linux-acpi-ow...@vger.kernel.org [mailto:linux-acpi-
> Subject: Re: [PATCH] ACPICA: Events: Execute some _REG methods in early
> boot
>
> On Mon, Mar 07, 2016 at 06:36:05AM +, Zheng, Lv wrote:
> > Hi,
> >
> > First of all, why don't you respond on the kernel bugzilla?
> >
4.2.8-ckt5 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Linus Torvalds
commit 176bed1de5bf977938cad26551969eca8f0883b1 upstream.
The vmstat code uses
4.2.8-ckt5 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Thomas Hellstrom
commit 12617971c443c50750a12a77ea0e08319d161975 upstream.
A regression introduced when the
4.2.8-ckt5 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Andrey Konovalov
commit 07d86ca93db7e5cdf4743564d98292042ec21af7 upstream.
The 'umidi' object will be free'd on
4.2.8-ckt5 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Thomas Hellstrom
commit 12617971c443c50750a12a77ea0e08319d161975 upstream.
A regression introduced when the master ttm lock was split
4.2.8-ckt5 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Andrey Konovalov
commit 07d86ca93db7e5cdf4743564d98292042ec21af7 upstream.
The 'umidi' object will be free'd on the error path by
4.2.8-ckt5 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Linus Torvalds
commit 176bed1de5bf977938cad26551969eca8f0883b1 upstream.
The vmstat code uses "schedule_delayed_work_on()" to do the
4.2.8-ckt5 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Vegard Nossum
commit 005ce0713006a76d2b0c924ce0e2629e5d8510c3 upstream.
Ran into this on UML:
4.2.8-ckt5 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Ryan Ware
commit 613317bd212c585c20796c10afe5daaa95d4b0a1 upstream.
This patch fixes vulnerability CVE-2016-2085.
4.2.8-ckt5 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Vegard Nossum
commit 005ce0713006a76d2b0c924ce0e2629e5d8510c3 upstream.
Ran into this on UML:
drivers/built-in.o: In function
4.2.8-ckt5 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Ryan Ware
commit 613317bd212c585c20796c10afe5daaa95d4b0a1 upstream.
This patch fixes vulnerability CVE-2016-2085. The problem exists
4.2.8-ckt5 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Kamal Mostafa
This reverts commit 504017f7fa4377d77f134a6465f047858318e1f1.
Breaks ppc64 builds on hosts which
4.2.8-ckt5 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Kamal Mostafa
This reverts commit 504017f7fa4377d77f134a6465f047858318e1f1.
Breaks ppc64 builds on hosts which don't include the kmod
4.2.8-ckt5 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: CQ Tang
commit fda3bec12d0979aae3f02ee645913d66fbc8a26e upstream.
This is a 32-bit register. Apparently harmless on
4.2.8-ckt5 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Vegard Nossum
commit 01cc5235604d61018712c11a14d74230f6a38bf4 upstream.
Ran into this on UML:
4.2.8-ckt5 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Yong Li
commit 97a249e98a72d6b79fb7350a8dd56b147e9d5bdb upstream.
Without this change, the name entity for mcp4725
4.2.8-ckt5 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Vegard Nossum
commit 01cc5235604d61018712c11a14d74230f6a38bf4 upstream.
Ran into this on UML:
drivers/iio/accel/stk8ba50.c: In function
301 - 400 of 2750 matches
Mail list logo