linux-next: manual merge of the akpm-current tree with Linus' tree

Hi Andrew, Today's linux-next merge of the akpm-current tree got a conflict in: mm/page_alloc.c between commit: 3e04040df6d4 ("Revert "mm/page_alloc: fix memmap_init_zone pageblock alignment"") from Linus' tree and commit: 45251b0909dc ("mm: remove unused arg from

linux-next: manual merge of the akpm-current tree with Linus' tree

Hi Andrew, Today's linux-next merge of the akpm-current tree got a conflict in: mm/page_alloc.c between commit: 3e04040df6d4 ("Revert "mm/page_alloc: fix memmap_init_zone pageblock alignment"") from Linus' tree and commit: 45251b0909dc ("mm: remove unused arg from

Re: [PATCH v1 1/2] arm: npcm: modify configuration for the NPCM7xx BMC.

On Thu, Mar 15, 2018 at 4:16 PM Tomer Maimon wrote: > Modify configuration and MakeFile > for the Nuvoton NPCM and NPCM7xx BMC. > Signed-off-by: Tomer Maimon > --- > arch/arm/mach-npcm/Kconfig | 40 +++- >

Re: [PATCH v1 1/2] arm: npcm: modify configuration for the NPCM7xx BMC.

On Thu, Mar 15, 2018 at 4:16 PM Tomer Maimon wrote: > Modify configuration and MakeFile > for the Nuvoton NPCM and NPCM7xx BMC. > Signed-off-by: Tomer Maimon > --- > arch/arm/mach-npcm/Kconfig | 40 +++- > arch/arm/mach-npcm/Makefile | 4 +++- > 2

Re: [PATCH v3] vsprintf: Prevent crash when dereferencing invalid pointers

On (03/15/18 18:35), Linus Torvalds wrote: > On Thu, Mar 15, 2018 at 6:18 PM, Sergey Senozhatsky > wrote: > > > > Hm, may be sizeof(ptr) still won't suffice. It would be great if we > > could always look at spec.field_width, which can be up to 2 * sizeof(void >

Re: [PATCH v3] vsprintf: Prevent crash when dereferencing invalid pointers

On (03/15/18 18:35), Linus Torvalds wrote: > On Thu, Mar 15, 2018 at 6:18 PM, Sergey Senozhatsky > wrote: > > > > Hm, may be sizeof(ptr) still won't suffice. It would be great if we > > could always look at spec.field_width, which can be up to 2 * sizeof(void > > *), > > and then just

Re: [PATCH v1 2/2] arm: npcm: Enable L2 Cache in NPCM7xx

On Thu, Mar 15, 2018 at 4:16 PM Tomer Maimon wrote: > Enable L2 Cache in Nuvoton NPCM7xx BMC. > Signed-off-by: Tomer Maimon > --- > arch/arm/mach-npcm/npcm7xx.c | 2 ++ > 1 file changed, 2 insertions(+) > diff --git a/arch/arm/mach-npcm/npcm7xx.c

Re: [PATCH v1 2/2] arm: npcm: Enable L2 Cache in NPCM7xx

On Thu, Mar 15, 2018 at 4:16 PM Tomer Maimon wrote: > Enable L2 Cache in Nuvoton NPCM7xx BMC. > Signed-off-by: Tomer Maimon > --- > arch/arm/mach-npcm/npcm7xx.c | 2 ++ > 1 file changed, 2 insertions(+) > diff --git a/arch/arm/mach-npcm/npcm7xx.c b/arch/arm/mach-npcm/npcm7xx.c > index

Re: linux-next: build warning after merge of the tip tree

Hi Stephen, At 03/16/2018 01:37 PM, Stephen Rothwell wrote: Hi all, After merging the tip tree, yesterday's linux-next build (x86_64 allnoconfig) produced this warning: kernel/cpu.c:129:13: warning: 'cpuhp_is_ap_state' defined but not used [-Wunused-function] static bool

Re: linux-next: build warning after merge of the tip tree

Hi Stephen, At 03/16/2018 01:37 PM, Stephen Rothwell wrote: Hi all, After merging the tip tree, yesterday's linux-next build (x86_64 allnoconfig) produced this warning: kernel/cpu.c:129:13: warning: 'cpuhp_is_ap_state' defined but not used [-Wunused-function] static bool

Re: [PATCH 4/7] soc: qcom: rpmpd: Add support for get/set performance state

On 03/16/2018 10:05 AM, Viresh Kumar wrote: > On 16-03-18, 09:38, Rajendra Nayak wrote: >> With genpd now expecting powerdomain drivers supporting performance >> state to support get/set performance state callbacks, add support for it >> in the rpmpd driver. >> >> Signed-off-by: Rajendra Nayak

Re: [PATCH 4/7] soc: qcom: rpmpd: Add support for get/set performance state

On 03/16/2018 10:05 AM, Viresh Kumar wrote: > On 16-03-18, 09:38, Rajendra Nayak wrote: >> With genpd now expecting powerdomain drivers supporting performance >> state to support get/set performance state callbacks, add support for it >> in the rpmpd driver. >> >> Signed-off-by: Rajendra Nayak

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, yesterday's linux-next build (x86_64 allnoconfig) produced this warning: kernel/cpu.c:129:13: warning: 'cpuhp_is_ap_state' defined but not used [-Wunused-function] static bool cpuhp_is_ap_state(enum cpuhp_state state) ^

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, yesterday's linux-next build (x86_64 allnoconfig) produced this warning: kernel/cpu.c:129:13: warning: 'cpuhp_is_ap_state' defined but not used [-Wunused-function] static bool cpuhp_is_ap_state(enum cpuhp_state state) ^

Re: [PATCH V7 00/13] drivers: Boot Constraint core

On 23-02-18, 15:53, Viresh Kumar wrote: > Hi Greg, > > The V7 version incorporates the organizational changes suggested by Olof > earlier. Everything else is same otherwise. > > I have tested the Hisilicon patches (again) on hikey 9660 board, IMX stuff was > earlier tested by Sascha

Re: [PATCH V7 00/13] drivers: Boot Constraint core

On 23-02-18, 15:53, Viresh Kumar wrote: > Hi Greg, > > The V7 version incorporates the organizational changes suggested by Olof > earlier. Everything else is same otherwise. > > I have tested the Hisilicon patches (again) on hikey 9660 board, IMX stuff was > earlier tested by Sascha

Re: [PATCH v2] watchdog: aspeed: Allow configuring for alternate boot

On 03/15/2018 09:02 AM, Eddie James wrote: From: Milton Miller Allow the device tree to specify a watchdog to fallover to the alternate boot source. The aspeeed watchdog can set a latch directing flash chip select 0 to chip select 1, allowing boot from an alternate media

Re: [PATCH v2] watchdog: aspeed: Allow configuring for alternate boot

On 03/15/2018 09:02 AM, Eddie James wrote: From: Milton Miller Allow the device tree to specify a watchdog to fallover to the alternate boot source. The aspeeed watchdog can set a latch directing flash chip select 0 to chip select 1, allowing boot from an alternate media if the watchdog is

Great News!

We have a great about your E-mail address!!! You Won $950,500.00 USD on Amnesty International UK online E-mail Promotion. For more details about your prize claims, file with the following; Names: Country: Tel: Regards, Mr. David Ford

Great News!

We have a great about your E-mail address!!! You Won $950,500.00 USD on Amnesty International UK online E-mail Promotion. For more details about your prize claims, file with the following; Names: Country: Tel: Regards, Mr. David Ford

Re: [PATCH v2 1/2] hwmon: (ucd9000) Add gpio chip interface

Hi Christopher, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.16-rc5 next-20180315] [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

Re: [PATCH v2 1/2] hwmon: (ucd9000) Add gpio chip interface

Hi Christopher, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.16-rc5 next-20180315] [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

Re: linux-next: build failure after merge of the y2038 tree

Hi Arnd, Do you want me to send the fix as a patch or should I re-post the series? Thanks, Deepa On Thu, Mar 15, 2018 at 7:25 PM, Stephen Rothwell wrote: > Hi Arnd, > > After merging the y2038 tree, today's linux-next build (s390 allnoconfig) > failed like this: > > In

Re: linux-next: build failure after merge of the y2038 tree

Hi Arnd, Do you want me to send the fix as a patch or should I re-post the series? Thanks, Deepa On Thu, Mar 15, 2018 at 7:25 PM, Stephen Rothwell wrote: > Hi Arnd, > > After merging the y2038 tree, today's linux-next build (s390 allnoconfig) > failed like this: > > In file included from

Re: [PATCH v2] watchdog: aspeed: Allow configuring for alternate boot

On Fri, Mar 16, 2018 at 2:32 AM, Eddie James wrote: > From: Milton Miller > > Allow the device tree to specify a watchdog to fallover to > the alternate boot source. > > The aspeeed watchdog can set a latch directing flash chip select 0 to > chip

Re: [PATCH v2] watchdog: aspeed: Allow configuring for alternate boot

On Fri, Mar 16, 2018 at 2:32 AM, Eddie James wrote: > From: Milton Miller > > Allow the device tree to specify a watchdog to fallover to > the alternate boot source. > > The aspeeed watchdog can set a latch directing flash chip select 0 to > chip select 1, allowing boot from an alternate media

Re: [PATCH RFC rebase 3/9] powerpc/64: Use barrier_nospec in syscall entry

On Thu, 15 Mar 2018 20:15:52 +0100 Michal Suchanek wrote: > On powerpc syscall entry is done in assembly so patch in an explicit > barrier_nospec. Same comment as Linus for this -- the barriers are before the branch here, so is it possible the branch instruction can be

Re: [PATCH RFC rebase 3/9] powerpc/64: Use barrier_nospec in syscall entry

On Thu, 15 Mar 2018 20:15:52 +0100 Michal Suchanek wrote: > On powerpc syscall entry is done in assembly so patch in an explicit > barrier_nospec. Same comment as Linus for this -- the barriers are before the branch here, so is it possible the branch instruction can be speculative while the

Re: [PATCH 4/4] mm/hmm: change CPU page table snapshot functions to simplify drivers

On 03/15/2018 11:37 AM, jgli...@redhat.com wrote: > From: Jérôme Glisse > > This change hmm_vma_fault() and hmm_vma_get_pfns() API to allow HMM > to directly write entry that can match any device page table entry > format. Device driver now provide an array of flags value and

Re: [PATCH 4/4] mm/hmm: change CPU page table snapshot functions to simplify drivers

On 03/15/2018 11:37 AM, jgli...@redhat.com wrote: > From: Jérôme Glisse > > This change hmm_vma_fault() and hmm_vma_get_pfns() API to allow HMM > to directly write entry that can match any device page table entry > format. Device driver now provide an array of flags value and we use > enum to

[PATCH] staging: media: davinci_vpfe: add error handling on kmalloc failure

There is no failure checking on the param value which will be allocated memory by kmalloc. Add a null pointer checking statement. Then goto error: and return -ENOMEM error code when kmalloc is failed. Signed-off-by: Ji-Hun Kim ---

[PATCH] staging: media: davinci_vpfe: add error handling on kmalloc failure

There is no failure checking on the param value which will be allocated memory by kmalloc. Add a null pointer checking statement. Then goto error: and return -ENOMEM error code when kmalloc is failed. Signed-off-by: Ji-Hun Kim --- drivers/staging/media/davinci_vpfe/dm365_ipipe.c | 8 1

Re: [PATCH] [v2] Bluetooth: btrsi: rework dependencies

Arnd Bergmann writes: > On Thu, Mar 15, 2018 at 7:30 PM, Marcel Holtmann wrote: >> Hi Arnd, >> >>> The linkage between the bluetooth driver and the wireless >>> driver is not defined properly, leading to build problems >>> such as: >>> >>> warning:

Re: [PATCH] [v2] Bluetooth: btrsi: rework dependencies

Arnd Bergmann writes: > On Thu, Mar 15, 2018 at 7:30 PM, Marcel Holtmann wrote: >> Hi Arnd, >> >>> The linkage between the bluetooth driver and the wireless >>> driver is not defined properly, leading to build problems >>> such as: >>> >>> warning: (BT_HCIRSI) selects RSI_COEX which has unmet

Re: [PATCH 00/16] remove eight obsolete architectures

Hi, On Thu, Mar 15, 2018 at 10:56:48AM +0100, Arnd Bergmann wrote: > On Thu, Mar 15, 2018 at 10:42 AM, David Howells wrote: > > Do we have anything left that still implements NOMMU? Please don't kill !MMU. > Yes, plenty. > I've made an overview of the remaining

Re: [PATCH 00/16] remove eight obsolete architectures

Hi, On Thu, Mar 15, 2018 at 10:56:48AM +0100, Arnd Bergmann wrote: > On Thu, Mar 15, 2018 at 10:42 AM, David Howells wrote: > > Do we have anything left that still implements NOMMU? Please don't kill !MMU. > Yes, plenty. > I've made an overview of the remaining architectures for my own

Re: [PATCH 7/7] soc: qcom: rpmpd: Add a max vote on all corners at init

On 16-03-18, 09:38, Rajendra Nayak wrote: > As we move from no clients/consumers in kernel voting on corners, > to *some* voting and some not voting, we might end up in a situation > where the clients which remove votes can adversly impact others > who still don't have a way to vote. > > To avoid

Re: [PATCH 7/7] soc: qcom: rpmpd: Add a max vote on all corners at init

On 16-03-18, 09:38, Rajendra Nayak wrote: > As we move from no clients/consumers in kernel voting on corners, > to *some* voting and some not voting, we might end up in a situation > where the clients which remove votes can adversly impact others > who still don't have a way to vote. > > To avoid

Re: [PATCH 6/7] mmc: sdhci-msm: Adapt the driver to use OPPs to set clocks/performance state

On 16-03-18, 09:38, Rajendra Nayak wrote: > @@ -1540,6 +1571,9 @@ static int sdhci_msm_probe(struct platform_device *pdev) > pm_runtime_disable(>dev); > pm_runtime_set_suspended(>dev); > pm_runtime_put_noidle(>dev); > + dev_pm_opp_of_remove_table(>dev); You can't do this if

Re: [PATCH 6/7] mmc: sdhci-msm: Adapt the driver to use OPPs to set clocks/performance state

On 16-03-18, 09:38, Rajendra Nayak wrote: > @@ -1540,6 +1571,9 @@ static int sdhci_msm_probe(struct platform_device *pdev) > pm_runtime_disable(>dev); > pm_runtime_set_suspended(>dev); > pm_runtime_put_noidle(>dev); > + dev_pm_opp_of_remove_table(>dev); You can't do this if

Re: [PATCH v2 3/3] vfio/pci: Add ioeventfd support

On Thu, Mar 15, 2018 at 03:31:58PM -0600, Alex Williamson wrote: > The ioeventfd here is actually irqfd handling of an ioeventfd such as > supported in KVM. A user is able to pre-program a device write to > occur when the eventfd triggers. This is yet another instance of > eventfd-irqfd

Re: [PATCH v2 3/3] vfio/pci: Add ioeventfd support

On Thu, Mar 15, 2018 at 03:31:58PM -0600, Alex Williamson wrote: > The ioeventfd here is actually irqfd handling of an ioeventfd such as > supported in KVM. A user is able to pre-program a device write to > occur when the eventfd triggers. This is yet another instance of > eventfd-irqfd

[PATCH 1/1] iommu/vt-d: Use real PASID for flush in caching mode

If caching mode is supported, the hardware will cache none-present or erroneous translation entries. Hence, software should explicitly invalidate the PASID cache after a PASID table entry becomes present. We should issue such invalidation with the PASID value that we have changed. PASID 0 is not

[PATCH 1/1] iommu/vt-d: Use real PASID for flush in caching mode

If caching mode is supported, the hardware will cache none-present or erroneous translation entries. Hence, software should explicitly invalidate the PASID cache after a PASID table entry becomes present. We should issue such invalidation with the PASID value that we have changed. PASID 0 is not

Re: [PATCH v4 08/24] fpga: add FPGA DFL PCIe device driver

On Thu, Mar 15, 2018 at 11:49:56AM -0700, Moritz Fischer wrote: > Hi Hao, > > On Tue, Feb 13, 2018 at 05:24:37PM +0800, Wu Hao wrote: > > From: Zhang Yi > > > > This patch implements the basic framework of the driver for FPGA PCIe > > device which implements the Device

Re: [PATCH v4 08/24] fpga: add FPGA DFL PCIe device driver

On Thu, Mar 15, 2018 at 11:49:56AM -0700, Moritz Fischer wrote: > Hi Hao, > > On Tue, Feb 13, 2018 at 05:24:37PM +0800, Wu Hao wrote: > > From: Zhang Yi > > > > This patch implements the basic framework of the driver for FPGA PCIe > > device which implements the Device Feature List (DFL) in its

Re: [PATCH 5/7] arm64: dts: msm8996: Add rpmpd device node

On 16-03-18, 09:38, Rajendra Nayak wrote: > Add rpmpd device node and its OPP table > > Signed-off-by: Rajendra Nayak > Signed-off-by: Viresh Kumar > --- > arch/arm64/boot/dts/qcom/msm8996.dtsi | 46 > +++ > 1

Re: [PATCH 5/7] arm64: dts: msm8996: Add rpmpd device node

On 16-03-18, 09:38, Rajendra Nayak wrote: > Add rpmpd device node and its OPP table > > Signed-off-by: Rajendra Nayak > Signed-off-by: Viresh Kumar > --- > arch/arm64/boot/dts/qcom/msm8996.dtsi | 46 > +++ > 1 file changed, 46 insertions(+) > > diff --git

Re: [PATCH 4/7] soc: qcom: rpmpd: Add support for get/set performance state

On 16-03-18, 09:38, Rajendra Nayak wrote: > With genpd now expecting powerdomain drivers supporting performance > state to support get/set performance state callbacks, add support for it > in the rpmpd driver. > > Signed-off-by: Rajendra Nayak > Signed-off-by: Viresh Kumar

Re: [PATCH 4/7] soc: qcom: rpmpd: Add support for get/set performance state

On 16-03-18, 09:38, Rajendra Nayak wrote: > With genpd now expecting powerdomain drivers supporting performance > state to support get/set performance state callbacks, add support for it > in the rpmpd driver. > > Signed-off-by: Rajendra Nayak > Signed-off-by: Viresh Kumar > --- >

Re: [PATCH 3/7] dt-bindings: opp: Introduce qcom-opp bindings

On 16-03-18, 09:38, Rajendra Nayak wrote: > On Qualcomm platforms, an OPP node needs to describe an > additional level/corner value that is then communicated to > a remote microprocessor by the CPU, which then takes some > actions (like adjusting voltage values across various rails) > based on the

Re: [PATCH 3/7] dt-bindings: opp: Introduce qcom-opp bindings

On 16-03-18, 09:38, Rajendra Nayak wrote: > On Qualcomm platforms, an OPP node needs to describe an > additional level/corner value that is then communicated to > a remote microprocessor by the CPU, which then takes some > actions (like adjusting voltage values across various rails) > based on the

[PATCH v2] rbd: Remove VLA usage

As part of the effort to remove VLAs from the kernel[1], this moves the literal values into the stack array calculation instead of using a variable for the sizing. The resulting size can be found from sizeof(buf). [1] https://lkml.org/lkml/2018/3/7/621 Signed-off-by: Kyle Spiers

[PATCH v2] rbd: Remove VLA usage

As part of the effort to remove VLAs from the kernel[1], this moves the literal values into the stack array calculation instead of using a variable for the sizing. The resulting size can be found from sizeof(buf). [1] https://lkml.org/lkml/2018/3/7/621 Signed-off-by: Kyle Spiers ---

[PATCH v5 0/2] Remove false-positive VLAs when using max()

Patch 1 adds const_max_t(), patch 2 uses it in all the places max() was used for stack arrays. Commit log from patch 1: ---snip--- kernel.h: Introduce const_max_t() for VLA removal In the effort to remove all VLAs from the kernel[1], it is desirable to build with -Wvla. However, this warning is

[PATCH v5 0/2] Remove false-positive VLAs when using max()

Patch 1 adds const_max_t(), patch 2 uses it in all the places max() was used for stack arrays. Commit log from patch 1: ---snip--- kernel.h: Introduce const_max_t() for VLA removal In the effort to remove all VLAs from the kernel[1], it is desirable to build with -Wvla. However, this warning is

[PATCH v5 2/2] Remove false-positive VLAs when using max()

As part of removing VLAs from the kernel[1], we want to build with -Wvla, but it is overly pessimistic and only accepts constant expressions for stack array sizes, instead of also constant values. The max() macro triggers the warning, so this refactors these uses of max() to use the new

[PATCH v5 2/2] Remove false-positive VLAs when using max()

As part of removing VLAs from the kernel[1], we want to build with -Wvla, but it is overly pessimistic and only accepts constant expressions for stack array sizes, instead of also constant values. The max() macro triggers the warning, so this refactors these uses of max() to use the new

[PATCH v5 1/2] kernel.h: Introduce const_max_t() for VLA removal

In the effort to remove all VLAs from the kernel[1], it is desirable to build with -Wvla. However, this warning is overly pessimistic, in that it is only happy with stack array sizes that are declared as constant expressions, and not constant values. One case of this is the evaluation of the max()

[PATCH v5 1/2] kernel.h: Introduce const_max_t() for VLA removal

In the effort to remove all VLAs from the kernel[1], it is desirable to build with -Wvla. However, this warning is overly pessimistic, in that it is only happy with stack array sizes that are declared as constant expressions, and not constant values. One case of this is the evaluation of the max()

Re: [PATCH][RFC] kernel.h: provide array iterator

On Thu, Mar 15, 2018 at 3:00 AM, Kieran Bingham wrote: > Simplify array iteration with a helper to iterate each entry in an array. > Utilise the existing ARRAY_SIZE macro to identify the length of the array > and pointer arithmetic to process each item as a for

Re: [PATCH][RFC] kernel.h: provide array iterator

On Thu, Mar 15, 2018 at 3:00 AM, Kieran Bingham wrote: > Simplify array iteration with a helper to iterate each entry in an array. > Utilise the existing ARRAY_SIZE macro to identify the length of the array > and pointer arithmetic to process each item as a for loop. > > Signed-off-by: Kieran

Re: [PATCH v10] mmc: Export host capabilities to debugfs.

On Thursday 15 March 2018 05:59 PM, Ulf Hansson wrote: > On 15 March 2018 at 11:26, Andy Shevchenko > wrote: >> On Thu, 2018-03-15 at 11:12 +0100, Ulf Hansson wrote: >>> On 13 March 2018 at 06:10, Harish Jenny K N

Re: [PATCH v10] mmc: Export host capabilities to debugfs.

On Thursday 15 March 2018 05:59 PM, Ulf Hansson wrote: > On 15 March 2018 at 11:26, Andy Shevchenko > wrote: >> On Thu, 2018-03-15 at 11:12 +0100, Ulf Hansson wrote: >>> On 13 March 2018 at 06:10, Harish Jenny K N >>> wrote: >>> Honestly, I don't like this, but maybe other people do, then

[PATCH 4/7] soc: qcom: rpmpd: Add support for get/set performance state

With genpd now expecting powerdomain drivers supporting performance state to support get/set performance state callbacks, add support for it in the rpmpd driver. Signed-off-by: Rajendra Nayak Signed-off-by: Viresh Kumar ---

[PATCH 4/7] soc: qcom: rpmpd: Add support for get/set performance state

With genpd now expecting powerdomain drivers supporting performance state to support get/set performance state callbacks, add support for it in the rpmpd driver. Signed-off-by: Rajendra Nayak Signed-off-by: Viresh Kumar --- drivers/soc/qcom/rpmpd.c | 42

[PATCH 0/7] Add powerdomain driver for corners on msm8996

With performance state support for genpd merged, and with some more patches to add support for them in the OPP layer [1] under discussion, this is an effort to model a powerdomain driver to communicate corner/level values for qualcomm platforms to RPM (Remote Power Manager) This series adds data

[PATCH 0/7] Add powerdomain driver for corners on msm8996

With performance state support for genpd merged, and with some more patches to add support for them in the OPP layer [1] under discussion, this is an effort to model a powerdomain driver to communicate corner/level values for qualcomm platforms to RPM (Remote Power Manager) This series adds data

[PATCH 3/7] dt-bindings: opp: Introduce qcom-opp bindings

On Qualcomm platforms, an OPP node needs to describe an additional level/corner value that is then communicated to a remote microprocessor by the CPU, which then takes some actions (like adjusting voltage values across various rails) based on the value passed. Describe these bindings in the

[PATCH 5/7] arm64: dts: msm8996: Add rpmpd device node

Add rpmpd device node and its OPP table Signed-off-by: Rajendra Nayak Signed-off-by: Viresh Kumar --- arch/arm64/boot/dts/qcom/msm8996.dtsi | 46 +++ 1 file changed, 46 insertions(+) diff --git

[PATCH 3/7] dt-bindings: opp: Introduce qcom-opp bindings

On Qualcomm platforms, an OPP node needs to describe an additional level/corner value that is then communicated to a remote microprocessor by the CPU, which then takes some actions (like adjusting voltage values across various rails) based on the value passed. Describe these bindings in the

[PATCH 5/7] arm64: dts: msm8996: Add rpmpd device node

Add rpmpd device node and its OPP table Signed-off-by: Rajendra Nayak Signed-off-by: Viresh Kumar --- arch/arm64/boot/dts/qcom/msm8996.dtsi | 46 +++ 1 file changed, 46 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi

[PATCH 6/7] mmc: sdhci-msm: Adapt the driver to use OPPs to set clocks/performance state

SDHCI driver needs to set a performance state along with scaling its clocks. Modify the driver to use the newly introduced powerdomain performance state based OPPs to scale clocks as well as set an appropriate powerdomain performance state. The patch also adds OPPs for sdhci device on msm8996.

[PATCH 6/7] mmc: sdhci-msm: Adapt the driver to use OPPs to set clocks/performance state

SDHCI driver needs to set a performance state along with scaling its clocks. Modify the driver to use the newly introduced powerdomain performance state based OPPs to scale clocks as well as set an appropriate powerdomain performance state. The patch also adds OPPs for sdhci device on msm8996.

[PATCH 7/7] soc: qcom: rpmpd: Add a max vote on all corners at init

As we move from no clients/consumers in kernel voting on corners, to *some* voting and some not voting, we might end up in a situation where the clients which remove votes can adversly impact others who still don't have a way to vote. To avoid this situation, have a max vote on all corners at

[PATCH 2/7] soc: qcom: rpmpd: Add a powerdomain driver to model corners

The powerdomains for corners just pass the performance state set by the consumers to the RPM (Remote Power manager) which then takes care of setting the appropriate voltage on the corresponding rails to meet the performance needs. We add all powerdomain data needed on msm8996 here. This driver

[PATCH 7/7] soc: qcom: rpmpd: Add a max vote on all corners at init

As we move from no clients/consumers in kernel voting on corners, to *some* voting and some not voting, we might end up in a situation where the clients which remove votes can adversly impact others who still don't have a way to vote. To avoid this situation, have a max vote on all corners at

[PATCH 2/7] soc: qcom: rpmpd: Add a powerdomain driver to model corners

The powerdomains for corners just pass the performance state set by the consumers to the RPM (Remote Power manager) which then takes care of setting the appropriate voltage on the corresponding rails to meet the performance needs. We add all powerdomain data needed on msm8996 here. This driver

[PATCH 1/7] PM / OPP: Add dev_pm_opp_get_of_node()

From: Viresh Kumar This adds a new helper to let the power domain drivers to access opp->np, so that they can read platform specific properties from the node. Signed-off-by: Viresh Kumar Signed-off-by: Rajendra Nayak ---

[PATCH 1/7] PM / OPP: Add dev_pm_opp_get_of_node()

From: Viresh Kumar This adds a new helper to let the power domain drivers to access opp->np, so that they can read platform specific properties from the node. Signed-off-by: Viresh Kumar Signed-off-by: Rajendra Nayak --- drivers/opp/of.c | 19 +++ include/linux/pm_opp.h

Re: [PATCH RFC 2/2] virtio_ring: support packed ring

On 2018年02月23日 19:18, Tiwei Bie wrote: Signed-off-by: Tiwei Bie --- drivers/virtio/virtio_ring.c | 699 +-- include/linux/virtio_ring.h | 8 +- 2 files changed, 618 insertions(+), 89 deletions(-) diff --git

Re: [PATCH RFC 2/2] virtio_ring: support packed ring

On 2018年02月23日 19:18, Tiwei Bie wrote: Signed-off-by: Tiwei Bie --- drivers/virtio/virtio_ring.c | 699 +-- include/linux/virtio_ring.h | 8 +- 2 files changed, 618 insertions(+), 89 deletions(-) diff --git a/drivers/virtio/virtio_ring.c

Re: [PATCH] KVM: x86: Fix device passthrough when SME is active

On 3/8/2018 5:17 PM, Tom Lendacky wrote: > When using device passthrough with SME active, the MMIO range that is > mapped for the device should not be mapped encrypted. Add a check in > set_spte() to insure that a page is not mapped encrypted if that page > is a device MMIO page as indicated by

Re: [PATCH] KVM: x86: Fix device passthrough when SME is active

On 3/8/2018 5:17 PM, Tom Lendacky wrote: > When using device passthrough with SME active, the MMIO range that is > mapped for the device should not be mapped encrypted. Add a check in > set_spte() to insure that a page is not mapped encrypted if that page > is a device MMIO page as indicated by

Re: [RFC PATCH V1 01/12] audit: add container id

On 2018-03-15 16:27, Stefan Berger wrote: > On 03/01/2018 02:41 PM, Richard Guy Briggs wrote: > > Implement the proc fs write to set the audit container ID of a process, > > emitting an AUDIT_CONTAINER record to document the event. > > > > This is a write from the container orchestrator task to a

Re: [RFC PATCH V1 01/12] audit: add container id

On 2018-03-15 16:27, Stefan Berger wrote: > On 03/01/2018 02:41 PM, Richard Guy Briggs wrote: > > Implement the proc fs write to set the audit container ID of a process, > > emitting an AUDIT_CONTAINER record to document the event. > > > > This is a write from the container orchestrator task to a

Re: mmotm 2018-03-14-16-24 uploaded (lustre)

On Thu, Mar 15 2018, Randy Dunlap wrote: > On 03/14/2018 04:24 PM, a...@linux-foundation.org wrote: >> The mm-of-the-moment snapshot 2018-03-14-16-24 has been uploaded to >> >>http://www.ozlabs.org/~akpm/mmotm/ > > (not from the mmotm patches, but in its linux-next.patch) > >

Re: mmotm 2018-03-14-16-24 uploaded (lustre)

On Thu, Mar 15 2018, Randy Dunlap wrote: > On 03/14/2018 04:24 PM, a...@linux-foundation.org wrote: >> The mm-of-the-moment snapshot 2018-03-14-16-24 has been uploaded to >> >>http://www.ozlabs.org/~akpm/mmotm/ > > (not from the mmotm patches, but in its linux-next.patch) > >

[PATCH v8 39/42] ARM: davinci: remove legacy clocks

This removes the unused legacy clock code from arch/arm/mach-davinci/. Signed-off-by: David Lechner Reviewed-by: Sekhar Nori --- v8 changes: - none v7 changes: - none v6 changes: - none arch/arm/mach-davinci/clock.c | 745

[PATCH v8 39/42] ARM: davinci: remove legacy clocks

This removes the unused legacy clock code from arch/arm/mach-davinci/. Signed-off-by: David Lechner Reviewed-by: Sekhar Nori --- v8 changes: - none v7 changes: - none v6 changes: - none arch/arm/mach-davinci/clock.c | 745

[PATCH v8 34/42] ARM: davinci: dm355: Remove legacy clock init

This removes the unused legacy clock init code from arch/arm/mach-davinci/dm355.c. Signed-off-by: David Lechner Reviewed-by: Sekhar Nori --- v8 changes: - none v7 changes: - rebased - add davinci prefix to commit message v6 changes: - rebased

[PATCH v8 34/42] ARM: davinci: dm355: Remove legacy clock init

This removes the unused legacy clock init code from arch/arm/mach-davinci/dm355.c. Signed-off-by: David Lechner Reviewed-by: Sekhar Nori --- v8 changes: - none v7 changes: - rebased - add davinci prefix to commit message v6 changes: - rebased arch/arm/mach-davinci/dm355.c | 357

[PATCH v8 40/42] ARM: davinci: add device tree support to timer

This adds device tree support to the davinci timer so that when clocks are moved to device tree, the timer will still work. Signed-off-by: David Lechner --- v8 changes: - none v7 changes: - add workaround for platform devices not available in early boot v6 changes: -

[PATCH v8 40/42] ARM: davinci: add device tree support to timer

This adds device tree support to the davinci timer so that when clocks are moved to device tree, the timer will still work. Signed-off-by: David Lechner --- v8 changes: - none v7 changes: - add workaround for platform devices not available in early boot v6 changes: - none

[PATCH v8 37/42] ARM: davinci: dm646x: Remove legacy clock init

This removes the unused legacy clock init code from arch/arm/mach-davinci/dm646x.c. Signed-off-by: David Lechner Reviewed-by: Sekhar Nori --- v8 changes: - rebased v7 changes: - rebased - add davinci prefix to commit message v6 changes: - rebased

[PATCH v8 37/42] ARM: davinci: dm646x: Remove legacy clock init

This removes the unused legacy clock init code from arch/arm/mach-davinci/dm646x.c. Signed-off-by: David Lechner Reviewed-by: Sekhar Nori --- v8 changes: - rebased v7 changes: - rebased - add davinci prefix to commit message v6 changes: - rebased arch/arm/mach-davinci/dm646x.c | 329

[PATCH v8 38/42] ARM: davinci: da8xx: Remove legacy USB and SATA clock init

This removes the unused legacy USB and SATA clock init code from arch/arm/mach-davinci/{devices,usb}-da8xx}.c. Signed-off-by: David Lechner Reviewed-by: Sekhar Nori --- v8 changes: - none v7 changes: - rebased - add davinci prefix to commit message -

[PATCH v8 38/42] ARM: davinci: da8xx: Remove legacy USB and SATA clock init

This removes the unused legacy USB and SATA clock init code from arch/arm/mach-davinci/{devices,usb}-da8xx}.c. Signed-off-by: David Lechner Reviewed-by: Sekhar Nori --- v8 changes: - none v7 changes: - rebased - add davinci prefix to commit message - mention SATA and USB in commit message v6

[PATCH v8 42/42] ARM: dts: da850: Add clocks

This adds clock provider nodes for da850 and wires them up to all of the devices. Signed-off-by: David Lechner --- v8 changes: - fix typo in clock-names property of psc0 - added power-domains properties to nodes that define that property in their device tree bindings v7

[PATCH v8 42/42] ARM: dts: da850: Add clocks

This adds clock provider nodes for da850 and wires them up to all of the devices. Signed-off-by: David Lechner --- v8 changes: - fix typo in clock-names property of psc0 - added power-domains properties to nodes that define that property in their device tree bindings v7 changes: - move

  1   2   3   4   5   6   7   8   9   10   >