piaojun wrote on Fri, Aug 03, 2018:
> We'd better reach an agreement about the patch fix.
The way I read Greg's comment was that he agreed to the proposed changes
and is waiting for a new version.
I'm writing a longer reply than I should because I don't like people
saying strncmp is safe just be
Dominique Martinet wrote on Fri, Aug 03, 2018:
> (the code is currently not safe if it returns an error, I'm sending
> another mail about it right after this one as we already have a partial
> fix)
I take that one back, ksys_mount() does check for error properly so just
the null checks we have in
On Fri, Aug 03, 2018 at 10:00:48AM +0800, Dou Liyang wrote:
>
>
>At 07/23/2018 05:29 PM, Chao Fan wrote:
>> Imitate the ACPI code to parse ACPI tables. Functions are simplified
>> cause some operations are not needed here.
>> And also, this method won't influence the initialization of ACPI.
>>
>>
add zstd compression support")
I have used the pstore tree from next-20180802 for today.
--
Cheers,
Stephen Rothwell
pgpqkh2PNeXBK.pgp
Description: OpenPGP digital signature
Since we switched to using SRCU for tracepoints used in the idle path,
we can no longer use rcu_dereference_sched for dereferencing points in
trace-event hooks.
Since tracepoints can now use either SRCU or sched-RCU, just use
rcu_dereference_raw for traceevents just like we're doing when
dereferen
On (08/02/18 14:13), Andrew Morton wrote:
[..]
> That changelog is rather hard to follow. Please review my edits:
>
> : If zram supports writeback feature, it's no longer a BD_CAP_SYNCHRONOUS_IO
^BDI_CAP_SYNCHRONOUS_IO
[..]
> A reader look
Hi Andrew,
On Thu, Aug 02, 2018 at 02:13:04PM -0700, Andrew Morton wrote:
> On Thu, 2 Aug 2018 14:11:12 +0900 Minchan Kim wrote:
>
> > If zram supports writeback feature, it's no more syncrhonous
> > device beause zram does synchronous IO opeation for
> > incompressible page.
> >
> > Do not pr
On (08/03/18 11:39), Sergey Senozhatsky wrote:
> [..]
>
> > A reader looking at this would wonder "why the heck are we doing that".
> > Adding a code comment would help them.
>
> The interesting thing here is that include/linux/backing-dev.h
> BDI_CAP_SYNCHRONOUS_IO comment says
>
> "Device
On Thu, Aug 2, 2018 at 6:00 PM, Stephen Rothwell wrote:
> Hi Kees,
>
> After merging the pstore tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> fs/pstore/platform.o: In function `zbufsize_zstd':
> platform.c:(.text+0x172): undefined reference to `ZSTD_compressBound'
>
Hi Masami,
On Thu, Aug 2, 2018 at 7:55 AM, Masami Hiramatsu wrote:
> Hi Joel,
>
> I found this caused several issues when testing ftrace.
>
> #1) ftrace boottest (FTRACE_STARTUP_TEST) fails
This sadly appears to be a real issue. The startup test for
"preemptirqsoff" tracer fails, however it pass
Hi Sergey,
On Fri, Aug 03, 2018 at 11:39:29AM +0900, Sergey Senozhatsky wrote:
> On (08/02/18 14:13), Andrew Morton wrote:
> [..]
> > That changelog is rather hard to follow. Please review my edits:
> >
> > : If zram supports writeback feature, it's no longer a BD_CAP_SYNCHRONOUS_IO
>
From: Yixin Zhu
This driver provides PLL clock registration as well as various clock
branches, e.g. MUX clock, gate clock, divider clock and so on.
PLLs that provide clock to DDR, CPU and peripherals are shown below:
+-+
|--->| LCPLL3 0|--PCIe clk-->
XO
From: Hua Ma
Add initial support for Intel MIPS interAptiv SoCs made by Intel.
This series will add support for the grx500 family.
The series allows booting a minimal system using a initramfs.
Signed-off-by: Hua Ma
Signed-off-by: Songjun Wu
---
Changes in v2:
- Remove unused _END macros
- Re
This patch series is for adding the support for Intel MIPS
interAptiv SoC GRX500 family. It includes CCF support, serial
driver optimization and DTS modification.
This patch series is applied on top of linux v4.18-rc7.
Basic verification is performed on GRX500 board.
We propose merging this patch
From: Hua Ma
This patch adds binding documentation for the
compatible values of the Intel MIPS SoCs.
Signed-off-by: Hua Ma
Signed-off-by: Songjun Wu
---
Changes in v2:
- New patch split from previous patch
- Add the board and chip compatible in dt document
Documentation/devicetree/bindings/
From: Yixin Zhu
This patch adds binding documentation for grx500 clock controller.
Signed-off-by: YiXin Zhu
Signed-off-by: Songjun Wu
---
Changes in v2:
- Rewrite clock driver's dt-binding document according to Rob Herring's
comments.
- Simplify device tree docoment, remove some clock descr
From: Hua Ma
Add dts files to support Intel MIPS SoCs:
- xrx500.dtsi is the chip dts
- easy350_anywan.dts is the board dts
Signed-off-by: Hua Ma
Signed-off-by: Songjun Wu
---
Changes in v2:
- New patch split from previous patch
- The memory address is changed to @2000
- Update to obj-$(CO
Reorder the head files according to the coding style.
Signed-off-by: Songjun Wu
---
Changes in v2:
- New patch to reorder the head files according to the coding style.
drivers/tty/serial/lantiq.c | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/dri
All the upper case in unit-address and hex constants are
changed to lower case according to the Linux conventions.
Signed-off-by: Songjun Wu
---
Changes in v2: None
arch/mips/boot/dts/lantiq/danube.dtsi | 42 -
arch/mips/boot/dts/lantiq/easy50712.dts | 14
The clk driver has introduced new clock APIs that replace
the existing clk_enable and clk_disable.
-clk_enable() APIs is replaced with clk_prepare_enable().
-clk_disable() API is replaced with clk_disable_unprepare().
Signed-off-by: Songjun Wu
---
Changes in v2: None
drivers/tty/serial/lanti
SWAP_IO_SPACE macro prevents serial driver /drivers/tty/serial/lantiq.c
to use readl/writel to replace ltq_r32/w32 which are SoC or platform
specific APIs.
readl/writel are used for this serial driver to support multiple
platforms and multiple architectures. The legacy lantiq platform(Danube)
enab
Previous implementation uses platform-dependent API to get the clock.
Those functions are not available for other SoC which uses the same IP.
The CCF (Common Clock Framework) have an abstraction based APIs for
clock. In future, the platform specific code will be removed when the
legacy soc use CCF
Previous implementation uses a hard-coded register value to check
if the current serial entity is the console entity.
Now the lantiq serial driver uses the aliases for the index of the
serial port.
The lantiq danube serial dts are updated with aliases to support this.
Signed-off-by: Songjun Wu
--
ltq prefix is platform specific function, asc prefix
is more generic.
Signed-off-by: Songjun Wu
---
Changes in v2: None
drivers/tty/serial/lantiq.c | 33 -
1 file changed, 20 insertions(+), 13 deletions(-)
diff --git a/drivers/tty/serial/lantiq.c b/drivers/tty/
Support more platform.
Signed-off-by: Songjun Wu
---
Changes in v2: None
drivers/tty/serial/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/tty/serial/Kconfig b/drivers/tty/serial/Kconfig
index df8bd0c7b97d..564c71fc24bb 100644
--- a/drivers/tty/serial/Kconf
Get serial id from dts.
"#ifdef CONFIG_LANTIQ" preprocessor is used because LTQ_EARLY_ASC
macro is defined in lantiq_soc.h.
lantiq_soc.h is in arch path for legacy product support.
arch/mips/include/asm/mach-lantiq/xway/lantiq_soc.h
If "#ifdef preprocessor" is changed to
"if (IS_ENABLED(CONFIG_L
Previous implementation uses platform-dependent functions
ltq_w32()/ltq_r32() to access registers. Those functions are not
available for other SoC which uses the same IP.
Change to OS provided readl()/writel() and readb()/writeb(), so
that different SoCs can use the same driver.
Signed-off-by: Son
init_lqasc() is only used internally, change to static declaration.
Signed-off-by: Songjun Wu
---
Changes in v2: None
drivers/tty/serial/lantiq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/tty/serial/lantiq.c b/drivers/tty/serial/lantiq.c
index 804aad60ed80..2b
Clocks and clock-names are updated in device tree binding.
Signed-off-by: Songjun Wu
---
Changes in v2: None
Documentation/devicetree/bindings/serial/lantiq_asc.txt | 15 +++
1 file changed, 15 insertions(+)
diff --git a/Documentation/devicetree/bindings/serial/lantiq_asc.txt
b/D
Rename fpiclk to freqclk.
Signed-off-by: Songjun Wu
---
Changes in v2: None
drivers/tty/serial/lantiq.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/tty/serial/lantiq.c b/drivers/tty/serial/lantiq.c
index 2e1b35b1cf4d..28086d52e980 100644
--- a/drivers
Hi,
On 08/02/2018 09:23 AM, Christopher Lameter wrote:
On Wed, 1 Aug 2018, Jeremy Linton wrote:
diff --git a/mm/slub.c b/mm/slub.c
index 51258eff4178..e03719bac1e2 100644
--- a/mm/slub.c
+++ b/mm/slub.c
@@ -2519,6 +2519,8 @@ static void *___slab_alloc(struct kmem_cache *s, gfp_t
gfpflags, int
On Thu, Aug 02, 2018 at 11:40:55AM +0200, Thomas Gleixner wrote:
> On Thu, 2 Aug 2018, Marc Zyngier wrote:
> > On Thu, 02 Aug 2018 07:55:49 +0100,
> > Thomas Gleixner wrote:
> > >
> > > On Thu, 2 Aug 2018, Marc Zyngier wrote:
> > > >
> > > > If we need to distinguish between the two, then we nee
Hi,
On 08/01/2018 07:14 PM, Andrew Morton wrote:
On Wed, 1 Aug 2018 17:56:46 -0500 Jeremy Linton wrote:
Hi,
On 08/01/2018 04:50 PM, Andrew Morton wrote:
On Wed, 1 Aug 2018 15:04:16 -0500 Jeremy Linton wrote:
The thread "avoid alloc memory on offline node"
https://lkml.org/lkml/2018/6/7
Hi,
On 08/02/2018 02:31 AM, Michal Hocko wrote:
On Wed 01-08-18 15:04:18, Jeremy Linton wrote:
Its possible to crash __alloc_pages_nodemask by passing it
bogus node ids. This is caused by NODE_DATA() returning null
(hopefully) when the requested node is offline. We can
harded against the basic
Hi,
On 08/02/2018 04:15 AM, Michal Hocko wrote:
On Wed 01-08-18 15:04:17, Jeremy Linton wrote:
[...]
@@ -2519,6 +2519,8 @@ static void *___slab_alloc(struct kmem_cache *s, gfp_t
gfpflags, int node,
if (unlikely(!node_match(page, searchnode))) {
stat(s, A
On Thu, 2 Aug 2018 at 21:04, Paolo Bonzini wrote:
>
> On 23/07/2018 08:39, Wanpeng Li wrote:
> > +Returns 0 if successfully delivery the IPIs and 1 if discarded.
>
> I'm changing this to
>
> "Returns the number of CPUs to which the IPIs were delivered successfully"
>
> with an obvious change to x8
Hi Minchan,
On (08/03/18 12:00), Minchan Kim wrote:
> > "Device is so fast that asynchronous IO would be inefficient."
> >
> > Which is not the reason why BDI_CAP_SYNCHRONOUS_IO is used by ZRAM.
> > Probably, the comment needs to be updated as well.
>
> I couldn't catch your point. Could you
Hi Mark,
After merging the spi tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
drivers/spi/spi-mem.c: In function 'spi_mem_probe':
drivers/spi/spi-mem.c:375:13: warning: assignment discards 'const' qualifier
from pointer target type [-Wdiscarded-qualifiers]
mem-
Refactored rtl_get_tcb_desc slightly to stay within the 80 character
line limit.
Signed-off-by: Luke Triantafyllidis
---
Changes in v2:
- Fixed the formatting of the comments
- Unwrapped some of the lines that were originally wrapped over multiple
lines to stay within the 80 character limit
Hi Wolfran,
Thanks for the review.
I will update the patch with a small comment section above
len --;
so that there is no confusion.
On 08/01/2018 02:35 AM, Wolfram Sang wrote:
--- a/drivers/i2c/busses/i2c-xlp9xx.c
+++ b/drivers/i2c/busses/i2c-xlp9xx.c
@@ -191,28 +191,30 @@ static void xlp9xx_
On Fri, Aug 03, 2018 at 01:13:02PM +0900, Sergey Senozhatsky wrote:
> Hi Minchan,
>
> On (08/03/18 12:00), Minchan Kim wrote:
> > > "Device is so fast that asynchronous IO would be inefficient."
> > >
> > > Which is not the reason why BDI_CAP_SYNCHRONOUS_IO is used by ZRAM.
> > > Probably, the
On (08/03/18 13:51), Minchan Kim wrote:
>
> AFAIK, onging writeback page couldn't freed so it was not writeabck problem.
>
> What I'm tryig to fix is read part.
> If we use swapcache, it shouldn't be a problem either because swapcache
> has a reference count and we should wait PG_lock release bef
On Fri, 27 Jul 2018 21:20:47 +0900
Masami Hiramatsu wrote:
> Add a testcase for max stack tracer, which checks basic
> max stack usage tracing and its filter feature.
>
Hmm, this test sometimes fails. (not always)
Let me check what happens.
Thank you,
> Signed-off-by: Masami Hiramatsu
> ---
On Fri, Aug 03, 2018 at 09:45:21AM +0800, Zhang Ning wrote:
> when firmware is in filesystem, request_firmware will load it,
> and copy it to vmalloc memory, that is page align memory.
>
> but when firmware is builtin, it is 8 bytes or 4 bytes alignment.
>
> make sure builtin firmware is page alg
On Thu, Aug 02, 2018 at 06:21:39PM -0700, Guenter Roeck wrote:
> On 08/02/2018 12:45 PM, Greg Kroah-Hartman wrote:
> [ ... ]
> >
> > I've pushed out -rc2 releases for all of these with that patch removed.
> >
>
> Boot tests with updated images passed for all three releases.
Wonderful, thanks fo
On Fri, Aug 03, 2018 at 11:02:27AM +0800, Songjun Wu wrote:
> Get serial id from dts.
>
> "#ifdef CONFIG_LANTIQ" preprocessor is used because LTQ_EARLY_ASC
> macro is defined in lantiq_soc.h.
> lantiq_soc.h is in arch path for legacy product support.
>
> arch/mips/include/asm/mach-lantiq/xway/lan
On (08/03/18 14:23), Sergey Senozhatsky wrote:
>
> Hmm, any chance a WB device can be async on its own? We add a page
> to a new bio and submit it to another async device driver. Then we
> return back to the upper layer (swap), which can free a page before
> the device picks up a request. Can this
for the soft_limit reclaim has more directivity than global reclaim, we
have current memcg be skipped to avoid potential page thrashing.
Signed-off-by: Zhaoyang Huang
---
mm/memcontrol.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/mm/memcontrol.c b/mm/memcontr
On Fri, Aug 03, 2018 at 11:02:33AM +0800, Songjun Wu wrote:
> Previous implementation uses platform-dependent API to get the clock.
> Those functions are not available for other SoC which uses the same IP.
> The CCF (Common Clock Framework) have an abstraction based APIs for
> clock. In future, the
On Fri, Aug 03, 2018 at 11:02:34AM +0800, Songjun Wu wrote:
> Support more platform.
>
> Signed-off-by: Songjun Wu
> ---
Your changelog text makes no sense, sorry.
greg k-h
Hi all,
Today's linux-next merge of the scsi-mkp tree got conflicts in:
drivers/scsi/qla2xxx/qla_gs.c
between commit:
b5f3bc39a0e8 ("scsi: qla2xxx: Fix inconsistent DMA mem alloc/free")
from Linus' tree and commit:
8777e4314d39 ("scsi: qla2xxx: Migrate NVME N2N handling into state machi
Code is emitting the following error message during boot on systems
without PMU hardware support while probing NMI capability.
NMI watchdog: Perf event create on CPU 0 failed with -2
This error is coming from this path:
lockup_detector_init
watchdog_nmi_probe
hardlockup_detector_perf_init
On Fri, Aug 3, 2018 at 1:48 PM Zhaoyang Huang wrote:
>
> for the soft_limit reclaim has more directivity than global reclaim, we40960
> have current memcg be skipped to avoid potential page thrashing.
>
The patch is tested in our android system with 2GB ram. The case
mainly focus on the smooth sl
On 2.8.2018 22:59, Stephen Boyd wrote:
> Quoting Michal Simek (2018-07-30 05:50:42)
>> On 26.7.2018 18:36, Stephen Boyd wrote:
>>> Quoting Michal Simek (2018-07-25 02:51:14)
On 24.7.2018 20:14, Jolly Shah wrote:
>>> create mode 100644 drivers/firmware/xilinx/zynqmp-debug.h
>>> create
If numa improvement from the task migration is going to be very
minimal, then avoid task migration.
specjbb2005 / bops/JVM / higher bops are better
on 2 Socket/2 Node Intel
JVMS PrevCurrent %Change
4 200892 210118 4.59252
1 325766 313171 -3.86627
on 2 Socket/4 Node Power8 (Po
Task migration under numa balancing can happen in parallel. More than
one task might choose to migrate to the same cpu at the same time. This
can result in
- During task swap, choosing a task that was not part of the evaluation.
- During task swap, task which just got moved into its preferred node,
This patchset based on current tip/sched/core, provides left out patches
from the previous series. This version handles the comments given to some of
the patches. It drops "sched/numa: Restrict migrating in parallel to the same
node." It adds an additional patch from Mel Gorman.
It also provides sp
This additional parameter (new_cpu) is used later for identifying if
task migration is across nodes.
No functional change.
Signed-off-by: Srikar Dronamraju
---
kernel/sched/core.c | 2 +-
kernel/sched/deadline.c | 2 +-
kernel/sched/fair.c | 2 +-
kernel/sched/sched.h| 2 +-
4 files
Since this spinlock will only serialize migrate rate limiting,
convert the spinlock to a trylock. If another task races ahead of this task
then this task can simply move on.
While here, add correct two abnormalities.
- Avoid time being stretched for every interval.
- Use READ/WRITE_ONCE with next
Currently task scan rate is reset when numa balancer migrates the task
to a different node. If numa balancer initiates a swap, reset is only
applicable to the task that initiates the swap. Similarly no scan rate
reset is done if the task is migrated across nodes by traditional load
balancer.
Inste
From: Mel Gorman
migrate_task_rq_fair resets the scan rate for NUMA balancing on every
cross-node migration. In the event of excessive load balancing due to
saturation, this may result in the scan rate being pegged at maximum and
further overloading the machine.
This patch only resets the scan i
On Fri 03-08-18 13:48:05, Zhaoyang Huang wrote:
> for the soft_limit reclaim has more directivity than global reclaim, we
> have current memcg be skipped to avoid potential page thrashing.
a) this changelog doesn't really explain the problem nor does it explain
why the proposed solution is reas
On Fri 03-08-18 07:05:54, Tetsuo Handa wrote:
> On 2018/07/31 14:09, Michal Hocko wrote:
> > On Tue 31-07-18 06:01:48, Tetsuo Handa wrote:
> >> On 2018/07/31 4:10, Michal Hocko wrote:
> >>> Since should_reclaim_retry() should be a natural reschedule point,
> >>> let's do the short sleep for PF_WQ_W
On Fri 03-08-18 14:11:26, Zhaoyang Huang wrote:
> On Fri, Aug 3, 2018 at 1:48 PM Zhaoyang Huang wrote:
> >
> > for the soft_limit reclaim has more directivity than global reclaim, we40960
> > have current memcg be skipped to avoid potential page thrashing.
> >
> The patch is tested in our android
On Thu 02-08-18 22:21:53, Jeremy Linton wrote:
> Hi,
>
> On 08/02/2018 04:15 AM, Michal Hocko wrote:
> > On Wed 01-08-18 15:04:17, Jeremy Linton wrote:
> > [...]
> > > @@ -2519,6 +2519,8 @@ static void *___slab_alloc(struct kmem_cache *s,
> > > gfp_t gfpflags, int node,
> > > if
Hi all,
Today's linux-next merge of the scsi-mkp tree got a conflict in:
drivers/scsi/qla2xxx/qla_init.c
between commit:
36eb8ff672fa ("scsi: qla2xxx: Fix NULL pointer dereference for fcport search")
from Linus' tree and commit:
48acad099074 ("scsi: qla2xxx: Fix N2N link re-connect")
f
> I've pushed out -rc2 releases for all of these with that patch removed.
Results from Linaro’s test farm.
No regressions on arm64, arm and x86_64.
Summary
kernel: 4.14.60-rc2
git repo:
https://git.kernel.org/pub/scm/linux
On Thu 02-08-18 22:17:49, Jeremy Linton wrote:
> Hi,
>
> On 08/02/2018 02:31 AM, Michal Hocko wrote:
> > On Wed 01-08-18 15:04:18, Jeremy Linton wrote:
> > > Its possible to crash __alloc_pages_nodemask by passing it
> > > bogus node ids. This is caused by NODE_DATA() returning null
> > > (hopeful
dma_pool_destroy will do NULL check,thus the check before
the call is not needed.
Signed-off-by: YueHaibing
---
arch/arm/common/dmabounce.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/arch/arm/common/dmabounce.c b/arch/arm/common/dmabounce.c
index 9a92de6..dcdd80c 1
On 2 August 2018 at 12:33, Greg Kroah-Hartman
wrote:
> On Thu, Aug 02, 2018 at 12:27:24PM +0530, Naresh Kamboju wrote:
>> On 1 August 2018 at 22:15, Greg Kroah-Hartman
>> wrote:
>> > This is the start of the stable review cycle for the 4.17.12 release.
>> > There are 336 patches in this series, a
I'm announcing the release of the 4.17.12 kernel.
All users of the 4.17 kernel series must upgrade.
The updated 4.17.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.17.y
and can be browsed at the normal kernel.org git web browser:
I'm announcing the release of the 4.14.60 kernel.
All users of the 4.14 kernel series must upgrade.
The updated 4.14.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.14.y
and can be browsed at the normal kernel.org git web browser:
On 2 August 2018 at 12:29, Naresh Kamboju wrote:
> On 1 August 2018 at 22:20, Greg Kroah-Hartman
> wrote:
>> This is the start of the stable review cycle for the 4.9.117 release.
>> There are 144 patches in this series, all will be posted as a response
>> to this one. If anyone has any issues wi
diff --git a/Documentation/devicetree/bindings/net/dsa/qca8k.txt
b/Documentation/devicetree/bindings/net/dsa/qca8k.txt
index 9c67ee4890d7..bbcb255c3150 100644
--- a/Documentation/devicetree/bindings/net/dsa/qca8k.txt
+++ b/Documentation/devicetree/bindings/net/dsa/qca8k.txt
@@ -2,7 +2,10 @@
Req
On Fri, Aug 03, 2018 at 11:53:53AM +0530, Naresh Kamboju wrote:
> > I've pushed out -rc2 releases for all of these with that patch removed.
>
> Results from Linaro’s test farm.
> No regressions on arm64, arm and x86_64.
Great!
I'm announcing the release of the 4.9.117 kernel.
All users of the 4.9 kernel series must upgrade.
The updated 4.9.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.9.y
and can be browsed at the normal kernel.org git web browser:
On 08/03/2018 12:58 AM, Mauro Carvalho Chehab wrote:
> Em Tue, 24 Jul 2018 11:35:59 +0200
> Arnd Bergmann escreveu:
>
>> Without the MFD driver, we run into a link error:
>
> Weird... I'm not seeing this driver at the media tree... was it merged via
> some other tree?
Yes, it's going via the mf
When hot-removing memory release_mem_region_adjustable() splits
iomem resources if they are not the exact size of the memory being
hot-deleted. Adding this memory back to the kernel adds a new
resource.
Eg a node has memory 0x0 - 0xf. Offlining and hot-removing
1GB from 0xf4000 results
On Thu, 2 Aug 2018, Matt Sealey wrote:
> The easiest explanation for this would be that the memory isn?t mapped
> correctly. You can?t use PCIe memory spaces with anything other than
> Device-nGnRE or stricter mappings. That?s just differences between the
> AMBA and PCIe (posted/unposted) me
On Fri, Aug 03, 2018 at 09:21:00AM +1000, Stephen Rothwell wrote:
> I fixed it up (see below)
I can't find any fixup below..
kfree(NULL) is safe,so this removes NULL check before freeing the mem
Signed-off-by: YueHaibing
---
arch/um/drivers/vector_kern.c | 15 +--
arch/um/drivers/vector_user.c | 6 ++
arch/um/kernel/irq.c | 3 +--
3 files changed, 8 insertions(+), 16 deletions(-)
diff --git
Hi Christoph,
On Fri, 3 Aug 2018 08:41:28 +0200 Christoph Hellwig wrote:
>
> On Fri, Aug 03, 2018 at 09:21:00AM +1000, Stephen Rothwell wrote:
> > I fixed it up (see below)
>
> I can't find any fixup below..
Sorry about that - see below.
--
Cheers,
Stephen Rothwell
fdd83c534b114febc41ec115
When hot-removing memory release_mem_region_adjustable() splits
iomem resources if they are not the exact size of the memory being
hot-deleted. Adding this memory back to the kernel adds a new
resource.
Eg a node has memory 0x0 - 0xf. Offlining and hot-removing
1GB from 0xf4000 results
Hi Alan,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.18-rc7 next-20180802]
[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
On Wed, Aug 01, 2018 at 10:52:57AM -0700, Nathan Chancellor wrote:
> On Wed, Aug 01, 2018 at 06:50:27PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.9.117 release.
> > There are 144 patches in this series, all will be posted as a response
> > to this o
On 1 August 2018 at 22:20, Greg Kroah-Hartman
wrote:
> This is the start of the stable review cycle for the 4.9.117 release.
> There are 144 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Respons
On Wed, 1 Aug 2018 at 22:45, Linus Torvalds
wrote:
>
> I'd like to get this sorted out asap, although at this point I still
> think that I'll have to do an rc8 even though I feel like we may have
> caught everything.
No AOSP regressions in my limited smoke testing so far with
current HEAD: 6b4703
On Wed, Aug 01, 2018 at 05:35:29PM -0600, Shuah Khan wrote:
> On 08/01/2018 10:45 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.17.12 release.
> > There are 336 patches in this series, all will be posted as a response
> > to this one. If anyone has any is
Hi Greg,
On 2018/8/2 14:15, Greg KH wrote:
> On Wed, Aug 01, 2018 at 05:09:13PM +0800, Chao Yu wrote:
>> Hi Stephen,
>>
>> On 2018/7/30 14:31, Gao Xiang wrote:
>>> Hi Stephen,
>>>
>>> On 2018/7/30 14:16, Stephen Rothwell wrote:
Hi Greg,
After merging the staging tree, today's linux-
Add DEPENDS_ON QCOM_APR for SND_SOC_SDM845 to fix the
warning: unmet direct dependencies detected for
SND_SOC_QDSP6.
Reported-by: Stephen Rothwell
Signed-off-by: Rohit kumar
---
sound/soc/qcom/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/sound/soc/qcom/Kconfig b/sound/soc/qcom/Kc
Hi Alan,
Thanks for the review...
> On Fri, Jul 27, 2018 at 1:22 AM, Appana Durga Kedareswara rao
> wrote:
>
> Hi Appana,
>
> There should be some documentation for the debugfs added under
> Documentation/driver-api/fpga/
>
> Also there are a lot of #ifdefs that were added due to th
On Thu, Aug 02, 2018 at 12:27:24PM +0530, Naresh Kamboju wrote:
> On 1 August 2018 at 22:15, Greg Kroah-Hartman
> wrote:
> > This is the start of the stable review cycle for the 4.17.12 release.
> > There are 336 patches in this series, all will be posted as a response
> > to this one. If anyone
On 8/2/2018 12:04 PM, Thomas Gleixner wrote:
On Thu, 2 Aug 2018, Gaurav Kohli wrote:
Timer wheel base->must_forward_clock is indicating that
the base clock might be stale due to a long idle sleep.
The forwarding of base clock takes place in softirq of timer
of the base clock takes place in
On Thu, 2 Aug 2018, Chao Fan wrote:
> On Thu, Aug 02, 2018 at 11:47:13AM +0800, Dou Liyang wrote:
Removed 70 lines of complete useless information
> >> + table = (struct acpi_subtable_header *)
> >> + ((unsigned long)table_header + sizeof(struct acpi_table_srat));
> >> +
> >> + tab
On Wed, 2018-07-04 at 16:18 +0300, Mike Rapoport wrote:
> Remove bootmem bitmap initialization and replace reserve_bootmem()
> with
> memblock_reserve().
>
> Signed-off-by: Mike Rapoport
> ---
> arch/nios2/Kconfig| 2 ++
> arch/nios2/kernel/prom.c | 7 ---
> arch/nios2/kernel/setu
On Wed, 2018-07-04 at 16:18 +0300, Mike Rapoport wrote:
> All we have to do is to enable memblock, the generic FDT code will
> take
> care of the rest.
>
> Signed-off-by: Mike Rapoport
> ---
> arch/nios2/Kconfig| 1 +
> arch/nios2/kernel/prom.c | 10 --
> arch/nios2/kernel/setu
On Thu, Aug 02, 2018 at 03:01:59PM +0800, Chao Yu wrote:
> Hi Greg,
>
> On 2018/8/2 14:15, Greg KH wrote:
> > On Wed, Aug 01, 2018 at 05:09:13PM +0800, Chao Yu wrote:
> >> Hi Stephen,
> >>
> >> On 2018/7/30 14:31, Gao Xiang wrote:
> >>> Hi Stephen,
> >>>
> >>> On 2018/7/30 14:16, Stephen Rothwell
On 02.08.2018 04:00, Andy Duan wrote:
> From: Stefan Agner Sent: 2018年8月1日 19:45
>> Check DMA addressing limitations as suggested by the DMA API how-to.
>> This does not fix a particular issue seen but is considered good style.
>>
>> Signed-off-by: Stefan Agner
>> ---
>> drivers/net/ethernet/fre
There are two bugs here. First the error codes weren't set on several
paths. And second, if the call to request_threaded_irq() inside
uio_register_device() fails then it would lead to a double free when
we call uio_unregister_device() inside pruss_cleanup().
Signed-off-by: Dan Carpenter
diff -
At 08/02/2018 03:05 PM, Thomas Gleixner wrote:
[...]
Folks. Can you please both stop this annoying habit of keeping the full
context of the mail and then sprinkling a random sentence into the middle?
I see. won’t do this stupid thing again.
Thanks,
dou
301 - 400 of 689 matches
Mail list logo
