* Sam Ravnborg wrote:
> On Sat, Jan 28, 2017 at 11:11:22PM +0100, Ingo Molnar wrote:
> >
> > The plan is to keep the old UAPI header in place but the kernel won't
> > use it anymore - and after some time we'll try to remove it. (User-space
> > tools better have local copies of headers anyway, i
This patch adds platform driver support for Synopsys UDC.
A new driver file (snps_udc_plat.c) is created for this purpose
where the platform driver registration is done based on OF
node.
Currently, UDC integrated into Broadcom's iProc SoCs (Northstar2
and Cygnus) work with this driver.
New membe
The device node is used for UDCs integrated into Broadcom's
iProc family of SoCs'. The UDC is based on Synopsys Designware
Cores AHB Subsystem USB Device Controller IP.
Signed-off-by: Raviteja Garimella
---
.../bindings/usb/brcm,iproc-snps-udc.txt | 24 ++
1 file ch
On Mon, Jan 30, 2017 at 8:07 AM, Rafael J. Wysocki wrote:
> On Mon, Jan 30, 2017 at 5:29 AM, Viresh Kumar wrote:
>> acpi_processor_ppc_notifier() can live without using CPUFREQ_START
>> (which is gonna be removed soon), as it is only used while setting
>> ignore_ppc to 0. This can be done with th
On Sun 29-01-17 16:50:03, Trevor Cordes wrote:
> On 2017-01-25 Michal Hocko wrote:
> > On Wed 25-01-17 04:02:46, Trevor Cordes wrote:
> > > OK, I patched & compiled mhocko's git tree from the other day
> > > 4.9.0+. (To confirm, weird, but mhocko's git tree I'm using from a
> > > couple of weeks ag
On Sun, 29 Jan 2017 22:54:11 +0100
Lukasz Majewski wrote:
> This commit provides apply() callback implementation for i.MX's PWMv2.
>
> Suggested-by: Stefan Agner
> Suggested-by: Boris Brezillon
> Signed-off-by: Lukasz Majewski
> Reviewed-by: Boris Brezillon
> ---
> Changes for v5:
> - Modify
On Sun, Jan 29, 2017 at 11:22 PM, Omar Sandoval wrote:
> On Mon, Jan 30, 2017 at 08:05:52AM +0100, Hannes Reinecke wrote:
>> On 01/29/2017 05:58 AM, Dan Williams wrote:
>> > Warnings of the following form occur because scsi reuses a devt number
>> > while the block layer still has it referenced as
On Sun, Jan 29, 2017 at 09:56:40AM +0800, Icenowy Zheng wrote:
> H3 and A64 SoCs have a bigger SID controller, which has its direct read
> address at 0x200 position in the SID block, not 0x0.
>
> Also, H3 SID controller has some silicon bug that makes the direct read
> value wrong at first, add co
On Mon, Jan 30, 2017 at 08:23:12AM +0100, Thierry Reding wrote:
> On Sun, Jan 29, 2017 at 10:54:07PM +0100, Lukasz Majewski wrote:
> > From: Lukasz Majewski
> >
> > This patch provides separate set of pwm ops utilized by
> > i.MX's PWMv1 and PWMv2.
> >
> > Signed-off-by: Lothar Waßmann
> > Sign
Hi,
On Sat, Jan 28, 2017 at 08:22:29PM +0800, Chen-Yu Tsai wrote:
> Hi everyone,
>
> This is v2 of my A80 CCU clk patches. Changes since v1:
>
> - Use pre-divider adjusted parent rate for rounding.
>
> - Use else statement for the case where the PLL lock status bit is
> in same register
> The subject line is not very descriptive. How about "Enforce level
> triggering for legacy interrupts"?
>
> On 25/01/17 08:52, Bharat Kumar Gogada wrote:
> > - Few wifi end points which only support legacy interrupts,
> > performs hardware reset functionalities after disabling interrupts
> > by
On Mon, Jan 30, 2017 at 08:05:52AM +0100, Hannes Reinecke wrote:
> On 01/29/2017 05:58 AM, Dan Williams wrote:
> > Warnings of the following form occur because scsi reuses a devt number
> > while the block layer still has it referenced as the name of the bdi
> > [1]:
> >
> > WARNING: CPU: 1 PID:
Hello,
The following program triggers use-after-free in sg_start_req:
https://gist.githubusercontent.com/dvyukov/be6561d2819fe30a78711234e53866b8/raw/1d75d4508f7a8ebb0b1ec0d18c0054fbffbc0708/gistfile1.txt
BUG: KASAN: use-after-free in bio_copy_user_iov+0xee1/0xf00
block/bio.c:1248 at addr 880
On Sun, Jan 29, 2017 at 10:54:09PM +0100, Lukasz Majewski wrote:
> From: Lukasz Majewski
>
> The software reset code has been extracted from imx_pwm_config_v2 function
> and moved to new one - imx_pwm_sw_reset().
>
> This change reduces the overall size of imx_pwm_config_v2() and prepares
> it f
On Sun, Jan 29, 2017 at 10:54:07PM +0100, Lukasz Majewski wrote:
> From: Lukasz Majewski
>
> This patch provides separate set of pwm ops utilized by
> i.MX's PWMv1 and PWMv2.
>
> Signed-off-by: Lothar Waßmann
> Signed-off-by: Bhuvanchandra DV
> Signed-off-by: Lukasz Majewski
> Acked-by: Shawn
On Sat, Jan 28, 2017 at 11:09 PM, Bjorn Helgaas wrote:
> On Sun, Jan 15, 2017 at 09:03:45PM +0100, Lukas Wunner wrote:
>> Currently PCIe ports are only allowed to go to D3 if the BIOS is dated
>> 2015 or newer to avoid potential issues with old chipsets. However for
>> Thunderbolt we know that ev
On Mon, Jan 30, 2017 at 5:29 AM, Viresh Kumar wrote:
> acpi_processor_ppc_notifier() can live without using CPUFREQ_START
> (which is gonna be removed soon), as it is only used while setting
> ignore_ppc to 0. This can be done with the help of "ignore_ppc < 0"
> check alone. The notifier function
On Mon, Jan 30, 2017 at 07:45:21AM +0100, Greg Kroah-Hartman wrote:
> On Mon, Jan 30, 2017 at 10:36:29AM +0530, Shailendra Verma wrote:
> > of_device_get_match_data could return NULL, and so can cause
> > a NULL pointer dereference later.
> >
> > Signed-off-by: Shailendra Verma
> > ---
> > drive
On Mon, Jan 30, 2017 at 10:33:07AM +0530, Shailendra Verma wrote:
> of_device_get_match_data could return NULL, and so can cause
> a NULL pointer dereference later.
>
> Signed-off-by: Shailendra Verma
> ---
> drivers/i2c/busses/i2c-tegra.c |4
> 1 file changed, 4 insertions(+)
This wil
On Mon, Jan 30, 2017 at 4:47 AM, Michael Ellerman wrote:
> "Gautham R. Shenoy" writes:
>
>> From: "Gautham R. Shenoy"
>>
>> In the current code for powernv_add_idle_states, there is a lot of code
>> duplication while initializing an idle state in powernv_states table.
>>
>> Add an inline helper
On Mon, Jan 30, 2017 at 10:23:45AM +0530, Shailendra Verma wrote:
> of_match_device could return NULL, and so can cause a NULL
> pointer dereference later.
>
> Signed-off-by: Shailendra Verma
> ---
> drivers/gpu/drm/tegra/sor.c |4
> 1 file changed, 4 insertions(+)
No, this will never
On Mon, Jan 30, 2017 at 10:22:33AM +0530, Shailendra Verma wrote:
> of_match_device could return NULL, and so can cause a NULL
> pointer dereference later.
>
> Signed-off-by: Shailendra Verma
> ---
> drivers/pwm/pwm-sun4i.c |4
> drivers/pwm/pwm-tegra.c |5 +
> 2 files changed,
On 01/29/2017 05:58 AM, Dan Williams wrote:
> Warnings of the following form occur because scsi reuses a devt number
> while the block layer still has it referenced as the name of the bdi
> [1]:
>
> WARNING: CPU: 1 PID: 93 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x62/0x80
> sysfs: cannot create dupl
Hi all,
There will be no linux-next release until Monday (next-20170130).
Changes since 20170125:
New tree: spi-nor
The drm tree lost its build failure.
The block tree gained a build failure so I used the version from
next-20170125.
The tip tree gained a conflict against the drm-misc-fixes tr
On Mon, Jan 30, 2017 at 7:23 AM, Olof Johansson wrote:
> Hi Krzysztof,
>
> On Sun, Jan 29, 2017 at 10:06:29PM +0200, Krzysztof Kozlowski wrote:
>> Hi,
>>
>> On top of previous pull request.
>>
>> This adds proper clocks to LPASS node on Exynos5433 which is needed
>> by Marek's patchset:
>> - [PAT
On Mon, Jan 30, 2017 at 10:36:29AM +0530, Shailendra Verma wrote:
> of_device_get_match_data could return NULL, and so can cause
> a NULL pointer dereference later.
>
> Signed-off-by: Shailendra Verma
> ---
> drivers/usb/host/xhci-tegra.c |4
> 1 file changed, 4 insertions(+)
>
> diff
Hi all,
On Mon, 30 Jan 2017 17:49:01 +1100 Stephen Rothwell
wrote:
>
> There will be no linux-next release until Monday (next-20170130).
Obviously, this is not longer relevant :-)
--
Cheers,
Stephen Rothwell
On Sun, Jan 29, 2017 at 06:53:42PM -0700, Jens Axboe wrote:
> Huh, I wonder how that snuck past my allmodconfig builds, that looks
> like a clear failure.
I also did tons of test builds and never saw it, not sure why
the NVMe-SCSI code still someone how an implicit include of scsi_cmnd.h.
But in
On Fri, Jan 27, 2017 at 05:15:32PM +, Patrice CHOTARD wrote:
> Here is the correct one
>
> PLease consider this second round of STi dts update for v4.11 :
>
> The following changes since commit 2016ead446b98c42dffd9b6c03ce813e5cb3b810:
>
>ARM: dts: STiH407-family: Supply Mailbox properti
On Sun, Jan 29, 2017 at 11:56:38PM +, James Simmons wrote:
>
> > On Sat, 2017-01-21 at 19:40 -0500, James Simmons wrote:
> > > The upstream kernel requires proper structures so
> > > convert nearly all the LNet wire protocols typedefs in
> > > the LNet core.
> >
> > Thanks.
> >
> > Perhaps s
Hi Krzysztof,
On 29 January 2017 at 19:05, Krzysztof Kozlowski wrote:
> Hi,
>
> On Odroid XU4 with an external usb2514 hub (evaluation board from SMSC
> or TI) connected to the USB2.0 port of EHCI controller, whenever I
> plug some USB device into the usb2514 hub I see errors like:
> [ 73.96917
>
> On 25/01/17 08:52, Bharat Kumar Gogada wrote:
> > - Legacy interrupts are level triggered, virtual irq line of End Point
> > shows as edge in /proc/interrupts.
> > - Setting irq flags of virtual irq line of EP to level triggered at
> > the time of mapping.
> >
> > Signed-off-by: Bharat Kumar G
Mark all the applicable VMAs with VM_CDM explicitly during mbind(MPOL_BIND)
call if the user provided nodemask has a CDM node.
Signed-off-by: Anshuman Khandual
---
mm/mempolicy.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/mm/mempolicy.c b/mm/mempolicy.c
index 78e095b.
Kernel cannot track device memory accesses behind VMAs containing CDM
memory. Hence all the VM_CDM marked VMAs should not be part of the auto
NUMA migration scheme. This patch also adds a new function is_cdm_vma()
to detect any VMA marked with flag VM_CDM.
Signed-off-by: Anshuman Khandual
---
in
of_match_device could return NULL, and so can cause a NULL
pointer dereference later.
Signed-off-by: Shailendra Verma
---
drivers/pinctrl/mvebu/pinctrl-dove.c |4
drivers/pinctrl/mvebu/pinctrl-kirkwood.c |4
drivers/pinctrl/mvebu/pinctrl-orion.c|4
3 files chan
On Mon, Jan 09, 2017 at 04:59:37PM +0530, Yury Norov wrote:
> This series enables aarch64 with ilp32 mode.
>
> As supporting work, it introduces ARCH_32BIT_OFF_T configuration
> option that is enabled for existing 32-bit architectures but disabled
> for new arches (so 64-bit off_t is is used by ne
We calculate page/lru accouting index with checking if the page/lru is
file. This will be a problem when we introduce a new LRU list. So add a
wrap for the calculation.
The patch is based on Minchan's previous patch.
Cc: Michal Hocko
Cc: Minchan Kim
Cc: Hugh Dickins
Cc: Johannes Weiner
Cc: Ri
Move the MADV_FREE pages into LRU_LAZYFREE list. The reason why we need
to do this is described in last patch. Next patch will reclaim the
pages.
The patch is based on Minchan's previous patch.
Cc: Michal Hocko
Cc: Minchan Kim
Cc: Hugh Dickins
Cc: Johannes Weiner
Cc: Rik van Riel
Cc: Mel Gor
Now MADV_FREE pages can be easily reclaimed even for swapless system. We
can safely enable MADV_FREE for all systems.
Cc: Michal Hocko
Cc: Minchan Kim
Cc: Hugh Dickins
Cc: Johannes Weiner
Cc: Rik van Riel
Cc: Mel Gorman
Signed-off-by: Shaohua Li
---
mm/madvise.c | 8 +---
1 file change
When memory pressure is high, we must free lazyfree pages. If we free
lazyfree pages, the cost reaccessing the pages is a page fault and page
allocation. The cost is much lower than swapin a page or refill a file
page cache because refilling anon/file page includes the same cost plus
extra IO cost,
MADV_FREE pages are in anonymous LRU list currently, there are several problems:
- Doesn't support system without swap enabled. Because if swap is off,
we can't or can't efficiently age anonymous pages. And since MADV_FREE
pages are mixed with other anonymous pages, we can't reclaim MADV_FREE p
We are going to add MADV_FREE pages into a new LRU list. Add a new flag
to indicate such pages. Note, we are reusing PG_mappedtodisk for the new
flag. This is ok because no anonymous pages have this flag set.
The patch is based on Minchan's previous patch.
Cc: Michal Hocko
Cc: Minchan Kim
Cc: H
Hi,
We are trying to use MADV_FREE in jemalloc. Several issues are found. Without
solving the issues, jemalloc can't use the MADV_FREE feature.
- Doesn't support system without swap enabled. Because if swap is off, we can't
or can't efficiently age anonymous pages. And since MADV_FREE pages are
On Fri, Jan 27, 2017 at 04:10:10PM +, Patrice CHOTARD wrote:
> Hi Arnd, Olof, Kevin
>
> Please consider this set for inclusion into the next v4.10-rc.
>
> The following changes since commit 7ce7d89f48834cefece7804d38fc5d85382edf77:
>
>Linux 4.10-rc1 (2016-12-25 16:13:08 -0800)
>
> are a
On Sun, Jan 29, 2017 at 10:06:27PM +0200, Krzysztof Kozlowski wrote:
> Hi,
>
> On top of previous pull request (tags/samsung-drivers-soc-pmu-4.11).
>
> This adds support for Exynos5433 to PMU driver which is needed
> by Marek's patchset:
> - [PATCH v2 0/8] Pad retentions support for Exynos5433
>
On Sat, Jan 28, 2017 at 01:45:10AM +0100, Alexandre Belloni wrote:
> Arnd, Olof
>
> The EBI was requiring more fixing than expected in preparation of the
> NAND driver rework for 4.12.
>
> The following changes since commit ee194289502a6901cc77dc9a893bf2afd351ac5e:
>
> memory/atmel-ebi: Fix ns
On Mon, Jan 30, 2017 at 10:55:45AM +0900, Masahiro Yamada wrote:
> I am resending this series to a...@kernel.org
> as requested by Olof Johansson.
>
> No code change since the previous post.
>
>
>
> Masahiro Yamada (2):
> arm64: defconfig: enable CONFIG_MTD_BLOCK
> arm64: defconfig: enable
On Sun, Jan 29, 2017 at 10:06:30PM +0200, Krzysztof Kozlowski wrote:
>
> On top of previous pull request.
>
>
> The following changes since commit cda1a52dab50340728e46601e6c9da9fc4beaf1f:
>
> ARM: s3c64xx: Constify wake_irqs (2016-12-29 15:41:44 +0200)
>
> are available in the git repositor
Hi Krzysztof,
On Sun, Jan 29, 2017 at 10:06:29PM +0200, Krzysztof Kozlowski wrote:
> Hi,
>
> On top of previous pull request.
>
> This adds proper clocks to LPASS node on Exynos5433 which is needed
> by Marek's patchset:
> - [PATCH v2 0/8] Pad retentions support for Exynos5433
>https://lkml
On 01/10/2017 08:32 AM, Juergen Gross wrote:
The Xen network frontend/backend supports multiple tx/rx queues for one
virtual interface. The number of queues supported by the backend is
set to the number of cpus of the backend driver domain (usually dom0)
and the number of queues requested by th
On Sun, Jan 29, 2017 at 10:06:28PM +0200, Krzysztof Kozlowski wrote:
> Hi,
>
> On top of previous pull request.
>
> Best regards,
> Krzysztof
>
>
> The following changes since commit bca9085e0ae93253bc93ce218c85ac7d7e7f1831:
>
> ARM: dts: exynos: remove Exynos4212 support (dead code) (2017-0
On Thu, Jan 26, 2017 at 05:27:54PM +0100, Alexandre Belloni wrote:
> Hi,
>
> Two non urgent fixes for 4.11 that could hopefully be backported as far
> back as possible to make kernelci (and our users) happy.
>
> The following changes since commit 21dd0ece34c2a07432a1cd0bbcb4815ce2b49173:
>
> A
If 'evsel' is NULL, in perf_evsel__is_bpf_output()
NULL pointer error can happen so check it.
Cc: Jiri Olsa
Cc: Namhyung Kim
Signed-off-by: Taeung Song
---
tools/perf/util/evsel.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/tools/perf/util/evsel.c b/tools/perf/uti
Currently there are several parts not checking NULL
after allocating with zalloc() or asigning NULL value
to a pointer variable after doing free().
So I fill in code checking NULL and
use zfree() instead of free().
Cc: Namhyung Kim
Cc: Jiri Olsa
Signed-off-by: Taeung Song
---
tools/perf/util/
of_device_get_match_data could return NULL, and so can cause
a NULL pointer dereference later.
Signed-off-by: Shailendra Verma
---
drivers/gpu/drm/exynos/exynos_drm_dsi.c |4
drivers/gpu/drm/exynos/exynos_drm_fimd.c |4
drivers/gpu/drm/exynos/exynos_hdmi.c |4
dri
of_device_get_match_data could return NULL, and so can cause
a NULL pointer dereference later.
Signed-off-by: Shailendra Verma
---
drivers/memory/atmel-sdramc.c |4
1 file changed, 4 insertions(+)
diff --git a/drivers/memory/atmel-sdramc.c b/drivers/memory/atmel-sdramc.c
index 12080b0.
of_device_get_match_data could return NULL, and so can cause
a NULL pointer dereference later.
Signed-off-by: Shailendra Verma
---
drivers/usb/host/xhci-tegra.c |4
1 file changed, 4 insertions(+)
diff --git a/drivers/usb/host/xhci-tegra.c b/drivers/usb/host/xhci-tegra.c
index a59fafb.
of_device_get_match_data could return NULL, and so can cause
a NULL pointer dereference later.
Signed-off-by: Shailendra Verma
---
drivers/thermal/imx_thermal.c |4
1 file changed, 4 insertions(+)
diff --git a/drivers/thermal/imx_thermal.c b/drivers/thermal/imx_thermal.c
index 06912f0.
of_device_get_match_data could return NULL, and so can cause
a NULL pointer dereference later.
Signed-off-by: Shailendra Verma
---
sound/soc/samsung/i2s.c |7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/sound/soc/samsung/i2s.c b/sound/soc/samsung/i2s.c
index 7825bff.
of_match_device could return NULL, and so can cause a NULL
pointer dereference later.
Signed-off-by: Shailendra Verma
---
drivers/phy/phy-berlin-usb.c |5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/phy/phy-berlin-usb.c b/drivers/phy/phy-berlin-usb.c
index 2017751..c85c516 10
of_device_get_match_data could return NULL, and so can cause
a NULL pointer dereference later.
Signed-off-by: Shailendra Verma
---
drivers/video/fbdev/ssd1307fb.c |4
1 file changed, 4 insertions(+)
diff --git a/drivers/video/fbdev/ssd1307fb.c b/drivers/video/fbdev/ssd1307fb.c
index 29
of_device_get_match_data could return NULL, and so can cause
a NULL pointer dereference later.
Signed-off-by: Shailendra Verma
---
drivers/i2c/busses/i2c-tegra.c |4
1 file changed, 4 insertions(+)
diff --git a/drivers/i2c/busses/i2c-tegra.c b/drivers/i2c/busses/i2c-tegra.c
index 4af9b
of_match_device could return NULL, and so can cause a NULL
pointer dereference later.
Signed-off-by: Shailendra Verma
---
drivers/pci/host/pcie-hisi.c |4
1 file changed, 4 insertions(+)
diff --git a/drivers/pci/host/pcie-hisi.c b/drivers/pci/host/pcie-hisi.c
index 56154c2..3256f8f 100
of_match_device could return NULL, and so can cause a NULL
pointer dereference later.
Signed-off-by: Shailendra Verma
---
drivers/mtd/nand/mxc_nand.c |4
drivers/mtd/nand/vf610_nfc.c |4
2 files changed, 8 insertions(+)
diff --git a/drivers/mtd/nand/mxc_nand.c b/drivers/mtd/n
of_match_device could return NULL, and so can cause a NULL
pointer dereference later.
Signed-off-by: Shailendra Verma
---
arch/arm/plat-pxa/ssp.c |4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/plat-pxa/ssp.c b/arch/arm/plat-pxa/ssp.c
index ba13f79..7d1cd51 100644
--- a/arch/
On Wed, Dec 28, 2016 at 5:37 PM, Chanwoo Choi wrote:
> +++ b/drivers/devfreq/devfreq.c
> @@ -620,6 +620,23 @@ struct devfreq *devfreq_add_device(struct device *dev,
> goto err_init;
> }
>
> + /*
> +* Get the suspend frequency from OPP table. But the devfreq de
of_match_device could return NULL, and so can cause a NULL
pointer dereference later.
Signed-off-by: Shailendra Verma
---
drivers/spi/spi-mxs.c |5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/spi/spi-mxs.c b/drivers/spi/spi-mxs.c
index 5b0e9a3..c3aea7e 100644
--- a/drivers/sp
of_match_device could return NULL, and so can cause a NULL
pointer dereference later.
Signed-off-by: Shailendra Verma
---
drivers/gpu/drm/tegra/sor.c |4
1 file changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/tegra/sor.c b/drivers/gpu/drm/tegra/sor.c
index 74d0540..34f032f 100644
of_match_device could return NULL, and so can cause a NULL
pointer dereference later.
Signed-off-by: Shailendra Verma
---
drivers/regulator/qcom_rpm-regulator.c |4
drivers/regulator/qcom_smd-regulator.c |4
2 files changed, 8 insertions(+)
diff --git a/drivers/regulator/qcom_
of_match_device could return NULL, and so can cause a NULL
pointer dereference later.
Signed-off-by: Shailendra Verma
---
drivers/pwm/pwm-sun4i.c |4
drivers/pwm/pwm-tegra.c |5 +
2 files changed, 9 insertions(+)
diff --git a/drivers/pwm/pwm-sun4i.c b/drivers/pwm/pwm-sun4i.c
in
of_match_device could return NULL, and so can cause a NULL
pointer dereference later.
Signed-off-by: Shailendra Verma
---
drivers/mmc/host/mxs-mmc.c |5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/mmc/host/mxs-mmc.c b/drivers/mmc/host/mxs-mmc.c
index 44ecebd..d12a5b7 100644
-
of_match_device could return NULL, and so can cause a NULL
pointer dereference later.
Signed-off-by: Shailendra Verma
---
drivers/mtd/nand/mxc_nand.c |4
drivers/mtd/nand/vf610_nfc.c |4
2 files changed, 8 insertions(+)
diff --git a/drivers/mtd/nand/mxc_nand.c b/drivers/mtd/n
Ingo,
Please pull the cputime/nsecs-for-tip branch that can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
cputime/nsecs-for-tip
HEAD: 14d889bef71ff808c450f82bcd257b10f05bb061
The patches are the same than on my previous post:
https://lwn.net/Art
of_match_device could return NULL, and so can cause a NULL
pointer dereference later.
Signed-off-by: Shailendra Verma
---
drivers/iio/adc/mxs-lradc.c | 14 ++
drivers/iio/adc/rockchip_saradc.c |4
2 files changed, 14 insertions(+), 4 deletions(-)
diff --git a/driver
Hi Linus,
Today's linux-next merge of the gpio tree got a conflict in:
drivers/staging/greybus/gpio.c
between commit:
1d3dfbd1dd34 ("staging: greybus: fix checkpatch unsigned warnings")
from the staging tree and commit:
2956b5d94a76 ("pinctrl / gpio: Introduce .set_config() callback for
Tyrel Datwyler writes:
> On 01/27/2017 01:03 AM, Michal Suchanek wrote:
>> On 27 January 2017 at 02:50, Benjamin Herrenschmidt
>> wrote:
>>> On Thu, 2017-01-26 at 17:42 -0800, Tyrel Datwyler wrote:
On 01/26/2017 12:22 PM, Michal Suchánek wrote:
> Hello,
>
> building ibmvtpm I no
acpi_processor_ppc_notifier() can live without using CPUFREQ_START
(which is gonna be removed soon), as it is only used while setting
ignore_ppc to 0. This can be done with the help of "ignore_ppc < 0"
check alone. The notifier function anyway ignores all events except
CPUFREQ_ADJUST and dropping C
On Mon, 30 Jan 2017, Michael Schmitz wrote:
> > Michael, Ondrej, can I get you to review/test please?
>
> No regressions during testing on my Falcon both using default settings,
> i.e. can_queue=1 or internal queueing (can_queue=4, cmd_per_lun=2), and
> the legacy IDE driver.
>
> I've seen a
Stephen Rothwell writes:
> Hi Paul,
>
> Today's linux-next merge of the rcu tree got a conflict in:
>
> arch/powerpc/Kconfig
>
> between commit:
>
> f2574030b0e3 ("powerpc: Revert the initial stack protector support")
>
> from the powerpc-fixes tree and commit:
>
> c7327406b3c3 ("rcu: Make
Hi Greg,
Today's linux-next merge of the staging tree got a conflict in:
drivers/staging/greybus/timesync_platform.c
between commit:
b17c1bba9cec ("staging: greybus: timesync: validate platform state callback")
from the staging.current tree and commit:
bdfb95c4baab ("staging: greybus: r
"Gautham R. Shenoy" writes:
> From: "Gautham R. Shenoy"
>
> In the current code for powernv_add_idle_states, there is a lot of code
> duplication while initializing an idle state in powernv_states table.
>
> Add an inline helper function to populate the powernv_states[] table
> for a given idle
Just enable MOVABLE_NODE config option for PPC64 platform by default.
This prevents accidentally building the kernel without the required
config option.
Signed-off-by: Anshuman Khandual
---
arch/powerpc/Kconfig | 4
1 file changed, 4 insertions(+)
diff --git a/arch/powerpc/Kconfig b/arch/p
This is a test script which creates a workload (e.g ebizzy) and go through
it's VMAs (/proc/pid/maps) and initiate migration to random nodes which can
be either system memory node or coherent memory node.
Signed-off-by: Anshuman Khandual
---
tools/testing/selftests/vm/cdm_migration.sh | 77 +
From: Reza Arbab
Onlining memory into ZONE_MOVABLE requires CONFIG_MOVABLE_NODE.
Enable the use of this config option on PPC64 platforms.
Signed-off-by: Reza Arbab
Signed-off-by: Anshuman Khandual
---
mm/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/Kconfig b
zone_names[] is used to identify any zone given it's index which
can be used in many other places. So exporting the definition
through include/linux/mmzone.h header for it's broader access.
Signed-off-by: Anshuman Khandual
---
include/linux/mmzone.h | 1 +
mm/page_alloc.c| 2 +-
2 files
This adds two different drivers inside drivers/char/ directory under two
new kernel config options COHERENT_HOTPLUG_DEMO and COHERENT_MEMORY_DEMO.
1) coherent_hotplug_demo: Detects, hoptlugs the coherent device memory
2) coherent_memory_demo: Exports debugfs interface for VMA migrations
Signed-o
From: Reza Arbab
When scanning the device tree to initialize the system NUMA topology,
process dt elements with compatible id "ibm,hotplug-aperture" to create
memoryless numa nodes.
These nodes will be filled when hotplug occurs within the associated
address range.
Signed-off-by: Reza Arbab
Si
Each individual node in the system has a ZONELIST_FALLBACK zonelist
and a ZONELIST_NOFALLBACK zonelist. These zonelists decide fallback
order of zones during memory allocations. Sometimes it helps to dump
these zonelists to see the priority order of various zones in them.
Particularly platforms wh
Coherent device memory nodes will have "ibm,hotplug-aperture" as one of the
compatible properties in their respective device nodes in the device tree.
Detect them early during NUMA platform initialization and mark them as such
in the node_to_phys_device_map[] array which in turn is used to support
Currently there is no interface to be called by a driver for user process
virtual range migration. This adds one function and exports to be then
used by drivers.
Signed-off-by: Anshuman Khandual
---
include/linux/mempolicy.h | 2 ++
mm/mempolicy.c| 45 +++
__GFP_THISNODE specifically asks the memory to be allocated from the given
node. Not all the requests that end up in __alloc_pages_nodemask() are
originated from the process context where cpuset makes more sense. The
current condition enforces cpuset limitation on every allocation whether
originate
VMA which contains CDM memory pages should be marked with new VM_CDM flag.
These VMAs need to be identified in various core kernel paths for special
handling and this flag will help in their identification.
Signed-off-by: Anshuman Khandual
---
include/linux/mm.h | 5 +
1 file changed, 5 inse
Kernel allocation to CDM node has already been prevented by putting it's
entire memory in ZONE_MOVABLE. But the CDM nodes must also be isolated
from implicit allocations happening on the system.
Any isolation seeking CDM node requires isolation from implicit memory
allocations from user space but
CDM nodes need a way of explicit memory allocation mechanism from the user
space. After the previous FALLBACK zonelist rebuilding process changes, the
mbind(MPOL_BIND) based allocation request fails on the CDM node. This is
because allocation requesting local node's FALLBACK zonelist is selected
fo
Task struct's mems_allowed element decides the final nodemask from which
memory can be allocated in the task context irrespective any applicable
memory policy. CDM nodes should not be used for user allocations, its one
of the overall requirements of it's isolation. So they should not be part
of any
HugeTLB allocation/release/accounting currently spans across all the nodes
under N_MEMORY node mask. Coherent memory nodes should not be part of these
allocations. So use system_ram() call to fetch system RAM only nodes on the
platform which can then be used for HugeTLB allocation purpose instead o
Currently cpusets_enabled() wrongfully returns 0 even if we have a root
cpuset configured on the system. This got missed when jump level was
introduced in place of number_of_cpusets with the commit 664eeddeef65
("mm: page_alloc: use jump labels to avoid checking number_of_cpusets")
. This fixes the
There are certain devices like accelerators, GPU cards, network
cards, FPGA cards, PLD cards etc which might contain on board memory. This
on board memory can be coherent along with system RAM and may be accessible
from either the CPU or from the device. The coherency is usually achieved
th
There are certain devices like specialized accelerator, GPU cards, network
cards, FPGA cards etc which might contain onboard memory which is coherent
along with the existing system RAM while being accessed either from the CPU
or from the device. They share some similar properties with that of norma
This patch fix some spelling typos found in visornic_main.c
Signed-off-by: Masanari Iida
---
drivers/staging/unisys/visornic/visornic_main.c | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/drivers/staging/unisys/visornic/visornic_main.c
b/drivers/sta
1 - 100 of 293 matches
Mail list logo
