This driver is modified to support RK3366 SoC.
Signed-off-by: Elaine Zhang
---
drivers/soc/rockchip/pm_domains.c | 32
1 file changed, 32 insertions(+)
diff --git a/drivers/soc/rockchip/pm_domains.c
b/drivers/soc/rockchip/pm_domains.c
index 796c46a6cbe7..40b757
On Thu, Jul 13, 2017 at 06:19:53PM +0200, Rafael J. Wysocki wrote:
> On Thu, Jul 13, 2017 at 7:40 AM, Viresh Kumar wrote:
> > There is no limitation in the ondemand or conservative governors which
> > disallow the transition_latency to be greater than 10 ms.
> >
> > The max_transition_latency fiel
LS1012A has one USB 3.0(DWC3) controller and
one USB 2.0 controller.
Signed-off-by: Ran Wang
---
Change in v2:
Move node usb2@860 to the back of sata@320 to keep nodes
sorted in unit-address.
arch/arm64/boot/dts/freescale/fsl-ls1012a.dtsi | 17 +++
On Thu, Jul 13, 2017 at 02:43:14PM -0700, Linus Torvalds wrote:
> On Thu, Jul 13, 2017 at 2:16 PM, Anna Schumaker
> wrote:
> >
> > git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-4.13-1
>
> Btw, your key seems to have expired, and doing a refresh on it doesn't fix it.
>
> I'm
On 07/14/2017 04:19 AM, Michael S. Tsirkin wrote:
On Thu, Jul 13, 2017 at 03:42:35PM +0800, Wei Wang wrote:
On 07/12/2017 09:56 PM, Michael S. Tsirkin wrote:
So the way I see it, there are several issues:
- internal wait - forces multiple APIs like kick/kick_sync
note how kick_sync can fai
> Basically what I was asking is whether I could use i2c_generic_scl_recovery
> in the case where SCL is hung.
The name is a bit misleading, I am afraid. Recovery can only be used when
SDA is stuck low. And to fix this it *uses* SCL toggling to get out of
it. And 'generic_scl' means 'gimme some S
Adding drm_add_modes_noedid_cea API for supporting cea modes
for drm devices which does not have panel framework or edid
support.
Protocols like SDI whic have minimal support in linux kernel can
benifit from this.
There is already a API drm_add_modes_noedid, but that supports only
dmt modes.
Sign
From: Colin Ian King
Trivial fix to spelling mistake in dev_err error message
Signed-off-by: Colin Ian King
---
drivers/infiniband/hw/bnxt_re/ib_verbs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/infiniband/hw/bnxt_re/ib_verbs.c
b/drivers/infiniband/hw/bnxt_re
Hi Jim,
On Friday 14 Jul 2017 09:58:11 Jim Lin wrote:
> On 2017年07月11日 03:47, Laurent Pinchart wrote:
> > On Monday 10 Jul 2017 14:43:49 Jim Lin wrote:
> >> Section 9.2.6.4 of USB 2.0/3.x specification describes that
> >> "device must be able to return the first data packet to host within
> >> 500
On 14/07/17 07:41, Guillaume Tucker wrote:
Hi Brian,
On 12/07/17 18:26, Brian Norris wrote:
Hi Guillaume,
I know this has already been merged, but I figured here was an OK place
to note (inline):
On Wed, May 03, 2017 at 10:56:25AM +0100, Guillaume Tucker wrote:
[...]
diff --git a/Document
在 2017/7/14 14:51, Hannes Reinecke 写道:
> On 07/10/2017 09:06 AM, Yijing Wang wrote:
>> Introduce wait-complete for libsas sas event processing,
>> execute sas port create/destruct in sync.
>>
>> Signed-off-by: Yijing Wang
>> CC: John Garry
>> CC: Johannes Thumshirn
>> CC: Ewan Milne
>> CC: Ch
On Thu, Jul 13, 2017 at 10:13 PM, Maxime Ripard
wrote:
> Huarui Lighting makes display panel, add it to the list of panels.
I could not find any information on "Huarui Lighting" within the
context of LCD panels. The company I found makes LED lighting
fixtures, floodlights, and high power LED driv
Hi peda,
> I don't seem to have this series in my inbox and not in my i2c folder either?
You have been CCed on the patches, but not on the cover-letter. Sorry
about that.
> patchwork and then I found it in the branch too, but in patchwork it has the
> expected "i2c: mux: " prefix so I'm not sure
From: Michal Hocko
build_zonelists gradually builds zonelists from the nearest to the most
distant node. As we do not know how many populated zones we will have in
each node we rely on the _zoneref to terminate initialized part of the
zonelist by a NULL zone. While this is functionally correct it
From: Michal Hocko
build_all_zonelists gets a zone parameter to initialize zone's
pagesets. There is only a single user which gives a non-NULL
zone parameter and that one doesn't really need the rest of the
build_all_zonelists (see 6dcd73d7011b ("memory-hotplug: allocate zone's
pcp before onlinin
From: Michal Hocko
f52407ce2dea ("memory hotplug: alloc page from other node in memory
online") has introduced N_HIGH_MEMORY checks to only use NUMA aware
allocations when there is some memory present because the respective
node might not have any memory yet at the time and so it could fail
or ev
From: Michal Hocko
zonelists_mutex has been introduced by 4eaf3f64397c ("mem-hotplug: fix
potential race while building zonelist for new populated zone") to
protect zonelist building from races. This is no longer needed though
because both memory online and offline are fully serialized. New users
From: Michal Hocko
build_all_zonelists has been (ab)using stop_machine to make sure that
zonelists do not change while somebody is looking at them. This is
is just a gross hack because a) it complicates the context from which
we can call build_all_zonelists (see 3f906ba23689 ("mm/memory-hotplug:
Hi,
this is aimed at cleaning up the zonelists initialization code we have
but the primary motivation was bug report [1] which got resolved but
the usage of stop_machine is just too ugly to live. Most patches are
straightforward but 3 of them need a special consideration.
Patch 1 removes zone orde
From: Michal Hocko
Supporting zone ordered zonelists costs us just a lot of code while
the usefulness is arguable if existent at all. Mel has already made
node ordering default on 64b systems. 32b systems are still using
ZONELIST_ORDER_ZONE because it is considered better to fallback to
a differe
From: Michal Hocko
try_online_node calls hotadd_new_pgdat which already calls
build_all_zonelists. So the additional call is redundant. Even though
hotadd_new_pgdat will only initialize zonelists of the new node this is
the right thing to do because such a node doesn't have any memory so
other z
From: Michal Hocko
boot_pageset is a boot time hack which gets superseded by normal
pagesets later in the boot process. It makes zero sense to reinitialize
it again and again during memory hotplug.
Signed-off-by: Michal Hocko
---
mm/page_alloc.c | 38 +-
1 f
From: Michal Hocko
__build_all_zonelists reinitializes each online cpu local node for
CONFIG_HAVE_MEMORYLESS_NODES. This makes sense because previously memory
less nodes could gain some memory during memory hotplug and so the local
node should be changed for CPUs close to such a node. It makes le
On 07/12/2017 11:00 PM, Andrew Morton wrote:
On Wed, 12 Jul 2017 23:40:53 +0200 "Luis R. Rodriguez"
wrote:
A soft bump to see if this can make it before the merge window closes.
Which is probably too late for already.
I've bounced a copy to Andrew. Andrew can this go through your tree this
Got some -EBUSY from zs_page_migrate that will make migration
slow (retry) or fail (zs_page_putback will schedule_work free_work,
but it cannot ensure the success).
And I didn't find anything that make zs_page_migrate cannot work with
a ZS_EMPTY zspage.
So make the patch to not check inuse if migr
In some scenarios, we should set some pins as input/output/pullup/pulldown
when the specified system goes into deep sleep mode, then when the system
goes into deep sleep mode, these pins will be set automatically by hardware.
That means some pins are not controlled by any specific driver in the OS
This patch adds the pin control driver for Spreadtrum SC9860 platform.
Signed-off-by: Baolin Wang
---
Changes since v4:
- Remove sleep configs.
- Use one standard sleep hardware state config to indicate sleep configs.
Changes since v3:
- Use the generic "bia-pull-up" config.
- Use some gener
This patch adds the binding documentation for Spreadtrum SC9860 pin
controller device.
Signed-off-by: Baolin Wang
---
Changes since v4:
- Remove these sleep related configs and only introduce one sleep
state config to indicate this is sleep state.
Changes since v3:
- Use generic "bias-pull-
Hi, I'm sorry to say that I have to stop the libsas hotplug improvement work, I
will resign from
Huawei, so I have no time and hardware to continue to work at this issue. John
is very familiar with
this work, and provide a lot of good suggestions. So if John like, I am glad he
could join to work
attribute_groups are not supposed to change at runtime.
So mark the non-const structs as const.
Arvind Yadav (4):
[PATCH 1/4] scsi: scsi_transport_iscsi: constify attribute_group structures.
[PATCH 2/4] scsi: iscsi_boot_sysfs: constify attribute_group structures.
[PATCH 3/4] scsi: scsi_trans
attribute_groups are not supposed to change at runtime. All functions
working with attribute_groups provided by work
with const attribute_group. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
40380 10422 44 50846c69e scsi/
attribute_groups are not supposed to change at runtime. All functions
working with attribute_groups provided by
and work with const attribute_group. So mark the non-const
structs as const.
File size before:
textdata bss dec hex filename
154441616 0 1706042a4
attribute_groups are not supposed to change at runtime. All functions
working with attribute_groups provided by work
with const attribute_group. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
25481768 0431610dc drive
attribute_groups are not supposed to change at runtime. All functions
working with attribute_groups provided by
work with const attribute_group. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
341221932 4 360588cda drive
On Thu 13-07-17 15:33:47, Mike Kravetz wrote:
> On 07/13/2017 12:11 PM, Vlastimil Babka wrote:
> > [+CC linux-api]
> >
> > On 07/13/2017 05:58 PM, Mike Kravetz wrote:
> >> mremap will create a 'duplicate' mapping if old_size == 0 is
> >> specified. Such duplicate mappings make no sense for privat
On 14/07/2017 02:44, wangyijing wrote:
在 2017/7/14 0:10, John Garry 写道:
On 10/07/2017 08:06, Yijing Wang wrote:
Disco mutex was introudced to prevent domain rediscovery competing
with ata error handling(87c8331). If we have already hold the lock
in sas_revalidate_domain and sync executing pro
* Josh Poimboeuf wrote:
> For user space stack unwinding, the kernel could emulate what the kernel
> 'guess' unwinder does by scanning the user space stack and returning all
> the text addresses it finds.
User-space stacks tend to be much larger than kernel stacks, the cost of doing
such a ful
* Josh Poimboeuf wrote:
> > > The results wouldn't be 100% accurate, but they could end up being useful
> > > over time.
> >
> > And to expound further on the bad idea, maybe the "bad" addresses could be
> > filtered out somehow in post-processing (insert lots of hand waving).
>
> And some d
2017-06-22 15:21 keltezéssel, Zoltán Böszörményi írta:
Add a new IORESOURCE_ALLOCATED flag that is automatically used
when alloc_resource() is used internally in kernel/resource.c
and free_resource() now takes this flag into account.
The core of __request_region() was factored out into a new fun
2017-06-22 15:21 keltezéssel, Zoltán Böszörményi írta:
This patch uses the previously introduced macro called
request_declared_muxed_region() to synchronize access to
the I/O port pair 0xcd6 / 0xcd7 on SB800.
These I/O ports are also used by i2c-piix4 and sp5100_tco,
so synchronization is necess
2017-06-22 15:21 keltezéssel, Zoltán Böszörményi írta:
Use the new request_declared_muxed_region() macro to synchronize
accesses to the SB800 I/O port pair (0xcd6 / 0xcd7) with the
PCI quirk for isochronous USB transfers and with the i2c-piix4
driver.
At the same time, remove the long lifetime r
On Thu 13-07-17 20:45:21, Joey Lee wrote:
> On Thu, Jul 13, 2017 at 09:06:19AM +0200, Michal Hocko wrote:
> > On Thu 13-07-17 14:58:06, Joey Lee wrote:
[...]
> > > If BIOS emits ejection event for a ACPI0004 container, someone needs
> > > to handle the offline/eject jobs of container. Either kernel
As the comments from Heiko Stuebner that compatible
should not contain any placeholders, this patch fix it for rk3228 SoC.
Note that this is a fix for v4.13, due to fixing the current non-standard
binding name that should not become part of an official kernel release.
Signed-off-by: Frank Wang
On 14/07/2017 07:51, Hannes Reinecke wrote:
#ifdef CONFIG_SCSI_SAS_HOST_SMP
> extern int sas_smp_host_handler(struct Scsi_Host *shost, struct request *req,
>struct request *rsp);
> diff --git a/drivers/scsi/libsas/sas_port.c b/drivers/scsi/libsas/sas_port.c
> index 9
On 12/07/17 07:36, Shawn Guo wrote:
+static int nvmem_cell_read_u32(struct device* dev, const char *cell_id, u32 *val)
+{
+ struct nvmem_cell *cell;
+ void *buf;
+ size_t len;
+
+ cell = nvmem_cell_get(dev, cell_id);
+ if (IS_ERR(cell))
+ return PT
Hi,
On Thu, Jul 13, 2017 at 10:41 PM, Maxime Ripard
wrote:
> In the earlier display engine designs, any register access while a commit
> is pending is forbidden.
>
> One of the symptoms is that reading a register will return another, random,
> register value which can lead to register corruptions
Linus,
please pull sound fixes for v4.13-rc1 from:
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
tags/sound-fix-4.13-rc1
The topmost commit is b9091b1c654953cc9615f282704a6df8e31549cf
sound fixes for 4.13-rc1
The vimc platform drivers define a platform device ID table but these
are not set to the .id_table field in the platform driver structure.
So the platform device ID table is only used to fill the aliases in
the module but are not used for matching (works because the platform
subsystem fallbacks to
Hi Linus,
Very little activity in the befs file system this time since I'm busy
settling into a new job.
Hence the new-car-smell shiny address [0].
Merged one patch from Tommy Nguyen related to documentation.
Thank you very much,
Luis
[0] https://lkml.org/lkml/2017/7/9/37
The following chang
On Thu, 13 Jul 2017, Stéphane Marchesin wrote:
> So, if you think this is wrong, can you fix this warning in a way that
> you'd like?
As I replied previously [1], with more background, fixing the warnings
properly, in a way that actually improves the code instead of making it
worse, would mean a
This macro is not used after commit 3b9ab374a1e6
("ppdev: convert to y2038 safe"), so let's remove
it.
Signed-off-by: Guoqing Jiang
---
drivers/char/ppdev.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/char/ppdev.c b/drivers/char/ppdev.c
index 3e73bcd..d256110 100644
--- a/drive
This patch adds the I2C controller driver for Spreadtrum SC9860 platform.
Signed-off-by: Baolin Wang
Reviewed-by: Andy Shevchenko
---
Changes since v3:
- Use SPDX-License-Identifier tag instead.
Changes since v2:
- Remove some redundant comments and parens.
- Define macros instead of magic n
Looks good,
Reviewed-by: Johannes Thumshirn
--
Johannes Thumshirn Storage
jthumsh...@suse.de+49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG
This patch adds the binding documentation for Spreadtrum I2C
controller device.
Signed-off-by: Baolin Wang
Acked-by: Rob Herring
---
Changes since v3:
- Add Ack from RobH.
Changes since v2:
- Change compatible strings to be SoC specific.
Changes since v1:
- No updates.
---
Documentation/de
On Fri 07-07-17 14:00:03, Vlastimil Babka wrote:
> On 07/04/2017 07:17 AM, Joonsoo Kim wrote:
> >>
> >> Still, backporting b8f1a75d61d8 fixes this:
> >>
> >> [1.538379] allocated 738197504 bytes of page_ext
> >> [1.539340] Node 0, zone DMA: page owner found early allocated 0
> >> pa
Commit-ID: 91b2082ee3382fd58b605f1c75c88dff2fd5769b
Gitweb: http://git.kernel.org/tip/91b2082ee3382fd58b605f1c75c88dff2fd5769b
Author: Justin Ernst
AuthorDate: Thu, 13 Jul 2017 13:33:23 -0500
Committer: Ingo Molnar
CommitDate: Fri, 14 Jul 2017 10:23:04 +0200
x86/platform/uv/BAU: Fix co
Make lcd_panel structure const as it is only copied to some object.
As the only usage of this structure is a copy operation, so it can be
made const.
Signed-off-by: Bhumika Goyal
---
drivers/video/fbdev/omap/lcd_mipid.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/
Commit-ID: 0e4097c3354e2f5a5ad8affd9dc7f7f7d00bb6b9
Gitweb: http://git.kernel.org/tip/0e4097c3354e2f5a5ad8affd9dc7f7f7d00bb6b9
Author: Wanpeng Li
AuthorDate: Sun, 9 Jul 2017 00:40:28 -0700
Committer: Ingo Molnar
CommitDate: Fri, 14 Jul 2017 10:27:15 +0200
sched/cputime: Don't use smp_p
Commit-ID: 193be41e33168a3a06eb9d356d9e39c69de161d2
Gitweb: http://git.kernel.org/tip/193be41e33168a3a06eb9d356d9e39c69de161d2
Author: Joel Fernandes
AuthorDate: Wed, 12 Jul 2017 19:24:29 -0700
Committer: Ingo Molnar
CommitDate: Fri, 14 Jul 2017 10:35:16 +0200
sched/deadline: Fix confu
On 14 July 2017 at 08:42, Chen-Yu Tsai wrote:
> The register for the "new timing mode" also has bit fields for setting
> output and sample timing phases. According to comments in Allwinner's
> BSP kernel, the default values are good enough.
>
> Keep the default values already in the hardware when
Provide a module parameter to request internal loop by the SPI master
controller.
This should make loop testing easier without extra HW modification.
For test automation can be also used logic analyzer.
If some one wish to reproduce my test. Here is used setup:
i.MX6S RIoRBoard Logic A
On 13.07.2017 16:13, Maxime Ripard wrote:
> The LHR050H41 panel is the panel shipped with the BananaPi M2-Magic. Add a
> driver for it.
>
> Signed-off-by: Maxime Ripard
> ---
> drivers/gpu/drm/panel/Kconfig | 9 +-
> drivers/gpu/drm/panel/Makefile | 1 +-
> dr
On 14 July 2017 at 08:42, Chen-Yu Tsai wrote:
> On the SoCs that introduced the new timing mode for MMC controllers,
> both the old (where the clock delays are set in the CCU) and new
> (where the clock delays are set in the MMC controller) timing modes
> are available, and we have to support them
This series should shut up all warnings introduced by gcc-6 or gcc-7 on
today's linux-next, as observed in "allmodconfig" builds on x86,
arm and arm64.
I have sent some of these before, but some others are new, as I had
at some point disabled the -Wint-in-bool-context warning in my
randconfig test
gcc-7 warns about the result of a constant multiplication used as
a boolean:
drivers/ata/libata-core.c: In function 'ata_timing_quantize':
drivers/ata/libata-core.c:3164:30: warning: '*' in boolean context, suggest
'&&' instead [-Wint-in-bool-context]
This slightly rearranges the macro to simpli
gcc-7 warns about slightly suspicious code in vmw_cmd_invalid:
drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c: In function 'vmw_cmd_invalid':
drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c:522:23: error: the omitted middle
operand in ?: will always be 'true', suggest explicit middle operand
[-Werror=parenthes
gcc-7 warns about the result of a constant multiplication used as
a boolean:
drivers/ide/ide-timings.c: In function 'ide_timing_quantize':
drivers/ide/ide-timings.c:112:24: error: '*' in boolean context, suggest '&&'
instead [-Werror=int-in-bool-context]
q->setup = EZ(t->setup * 1000, T);
We test whether a bit is set in a mask here, which is correct
but gcc warns about it as it thinks it might be confusing:
drivers/isdn/isdnloop/isdnloop.c:412:37: error: ?: using integer constants in
boolean context, the expression will always evaluate to 'true'
[-Werror=int-in-bool-context]
Thi
On Thu, Jul 13, 2017 at 12:52:30PM -0500, Alan Tull wrote:
> On Sun, Jun 25, 2017 at 8:52 PM, Wu Hao wrote:
> > From: Xiao Guangrong
> >
> > Device Feature List structure creates a link list of feature headers
> > within the MMIO space to provide an extensible way of adding features.
> >
> > The
FIFO_MODE is an macro expression with a '<<' operator, which
gcc points out could be misread as a '<':
drivers/input/misc/adxl34x.c: In function 'adxl34x_probe':
drivers/input/misc/adxl34x.c:799:36: error: '<<' in boolean context, did you
mean '<' ? [-Werror=int-in-bool-context]
This converts th
gcc warns when MODULES_VADDR/END is defined to the same value as
VMALLOC_START/VMALLOC_END, e.g. on x86-32:
fs/proc/kcore.c: In function ‘add_modules_range’:
fs/proc/kcore.c:622:161: error: self-comparison always evaluates to false
[-Werror=tautological-compare]
if (/*MODULES_VADDR != VMALLOC_S
The setsign() macro gets called with an integer argument in a
few places, leading to a harmless warning in gcc-7:
arch/x86/math-emu/reg_add_sub.c: In function 'FPU_add':
arch/x86/math-emu/reg_add_sub.c:80:48: error: ?: using integer constants in
boolean context [-Werror=int-in-bool-context]
This
In some configurations, topology_physical_package_id() is trivially
defined as '-1' for any input, resulting a comparison that is
always true:
drivers/acpi/processor_thermal.c: In function ‘cpufreq_set_cur_state’:
drivers/acpi/processor_thermal.c:137:36: error: self-comparison always
evaluates to
With ccache in combination with gcc-6, we get a harmless warning for the sfi
subsystem,
as ccache only sees the preprocessed source:
drivers/sfi/sfi_core.c: In function ‘sfi_map_table’:
drivers/sfi/sfi_core.c:175:53: error: self-comparison always evaluates to true
[-Werror=tautological-compare]
On Thu, Jul 13, 2017 at 06:26:28PM -0700, Guenter Roeck wrote:
> On 07/13/2017 08:42 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 3.18.61 release.
> > There are 22 patches in this series, all will be posted as a response
> > to this one. If anyone has any
On Sat, Jul 01, 2017 at 09:40:04AM -0400, Zi Yan wrote:
> From: Zi Yan
>
> If one of callers of page migration starts to handle thp,
> memory management code start to see pmd migration entry, so we need
> to prepare for it before enabling. This patch changes various code
> point which checks the
gcc-7 points out an older regression:
drivers/staging/iio/resolver/ad2s1210.c: In function 'ad2s1210_read_raw':
drivers/staging/iio/resolver/ad2s1210.c:515:42: error: '<<' in boolean context,
did you mean '<' ? [-Werror=int-in-bool-context]
The original code had 'unsigned short' here, but incorr
When using ccache, we get a harmless warning about the fact that
we use the result of a multiplication as a condition:
drivers/infiniband/core/uverbs_main.c: In function 'ib_uverbs_write':
drivers/infiniband/core/uverbs_main.c:787:40: error: '*' in boolean context,
suggest '&&' instead [-Werror=i
When we pass the result of a multiplication as the timeout, we
can get a warning:
drivers/mmc/host/bcm2835.c:596:149: error: '*' in boolean context, suggest '&&'
instead [-Werror=int-in-bool-context]
drivers/mfd/arizona-core.c:247:195: error: '*' in boolean context, suggest '&&'
instead [-Werror
gcc thinks that interpreting a multiplication result as a bool
is confusing:
drivers/gpu/drm/nouveau/nvkm/subdev/clk/gt215.c: In function 'read_pll':
drivers/gpu/drm/nouveau/nvkm/subdev/clk/gt215.c:133:8: error: '*' in boolean
context, suggest '&&' instead [-Werror=int-in-bool-context]
In this i
On 07/14/2017 11:13 AM, Michal Hocko wrote:
> On Fri 07-07-17 14:00:03, Vlastimil Babka wrote:
>> On 07/04/2017 07:17 AM, Joonsoo Kim wrote:
Still, backporting b8f1a75d61d8 fixes this:
[1.538379] allocated 738197504 bytes of page_ext
[1.539340] Node 0, zone DMA
On Fri, Jul 14, 2017 at 09:59:58AM +0200, Michal Hocko wrote:
> From: Michal Hocko
>
> Supporting zone ordered zonelists costs us just a lot of code while
> the usefulness is arguable if existent at all. Mel has already made
> node ordering default on 64b systems. 32b systems are still using
> ZO
On 13.07.17 13:49, Yang Zhang wrote:
On 2017/7/4 22:13, Radim Krčmář wrote:
2017-07-03 17:28+0800, Yang Zhang:
The background is that we(Alibaba Cloud) do get more and more complaints
from our customers in both KVM and Xen compare to bare-mental.After
investigations, the root cause is known t
From: Wanpeng Li
Run kvm-unit-tests/eventinj.flat in L1 w/ ept=0 on both L0 and L1:
Before NMI IRET test
Sending NMI to self
NMI isr running stack 0x461000
Sending nested NMI to self
After nested NMI to self
Nested NMI isr running rip=40038e
After iret
After NMI to self
FAIL: NMI
Reference SDM
From: Shu Wang
When running memory stress tests, kmemleak could be easily disabled in
function create_object as system is out of memory and kmemleak failed to
alloc from object_cache. Since there's no way to enable kmemleak after
it's off, simply ignore the object_cache alloc failure will just lo
On Fri, Jul 14, 2017 at 09:59:59AM +0200, Michal Hocko wrote:
> From: Michal Hocko
>
> boot_pageset is a boot time hack which gets superseded by normal
> pagesets later in the boot process. It makes zero sense to reinitialize
> it again and again during memory hotplug.
>
> Signed-off-by: Michal
On Fri, Jul 14, 2017 at 5:26 PM, Ulf Hansson wrote:
> On 14 July 2017 at 08:42, Chen-Yu Tsai wrote:
>> On the SoCs that introduced the new timing mode for MMC controllers,
>> both the old (where the clock delays are set in the CCU) and new
>> (where the clock delays are set in the MMC controller)
v4l2_subdev_call is a macro returning whatever the callback return
type is, usually 'int'. With gcc-7 and ccache, this can lead to
many wanings like:
media/platform/pxa_camera.c: In function 'pxa_mbus_build_fmts_xlate':
media/platform/pxa_camera.c:766:27: error: ?: using integer constants in
bool
Provide a module parameter to request internal loop by the SPI master
controller.
This should make loop testing easier without extra HW modification.
For test automation a logic analyzer is recommended for host
controller-independent verification.
An example test rig configuration and procedure:
Hi
Today's linux-next fails to boot on ppc bare-metal
Test: Boot
Machine: Power 8 bare-metal
kernel: 4.12.0-next-20170713
gcc: version 4.8.5
config : Tul-NV-config attached.
boot logs:
--
OPAL nvram setup, 1048576 bytes
Zone ranges:
DMA [mem 0x-0x000f]
On Fri, Jul 14, 2017 at 5:16 PM, Ulf Hansson wrote:
> On 14 July 2017 at 08:42, Chen-Yu Tsai wrote:
>> The register for the "new timing mode" also has bit fields for setting
>> output and sample timing phases. According to comments in Allwinner's
>> BSP kernel, the default values are good enough.
On Fri, Jul 14, 2017 at 11:31:04AM +0200, Arnd Bergmann wrote:
> When using ccache, we get a harmless warning about the fact that
> we use the result of a multiplication as a condition:
>
> drivers/infiniband/core/uverbs_main.c: In function 'ib_uverbs_write':
> drivers/infiniband/core/uverbs_main.c
On Fri, Jul 14, 2017 at 10:00:00AM +0200, Michal Hocko wrote:
> From: Michal Hocko
>
> __build_all_zonelists reinitializes each online cpu local node for
> CONFIG_HAVE_MEMORYLESS_NODES. This makes sense because previously memory
> less nodes could gain some memory during memory hotplug and so the
On Thu, Jul 13, 2017 at 06:33:06PM -0700, Guenter Roeck wrote:
> On 07/13/2017 08:42 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.4.77 release.
> > There are 57 patches in this series, all will be posted as a response
> > to this one. If anyone has any i
/linux/commits/Maxime-Ripard/drm-sun4i-Allwinner-MIPI-DSI-support/20170714-123103
config: arm-sunxi_defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
wget
https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O
~/bin
On Thu, Jul 13, 2017 at 02:07:45PM -0700, kernelci.org bot wrote:
> stable-rc/linux-4.4.y boot: 99 boots: 1 failed, 92 passed with 5 offline, 1
> conflict (v4.4.76-58-g1a12e8e8a429)
Any idea how 0-day and Guenter's system found problems with this
release, but you all didn't? Do you not have any
On Thu, Jul 13, 2017 at 07:08:54PM -0700, Guenter Roeck wrote:
> On 07/13/2017 08:40 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.12.2 release.
> > There are 10 patches in this series, all will be posted as a response
> > to this one. If anyone has any i
On Thu, Jul 13, 2017 at 03:07:46PM -0700, kernelci.org bot wrote:
> stable-rc/linux-4.12.y boot: 226 boots: 5 failed, 216 passed with 4 offline,
> 1 conflict (v4.12.1-11-g28917cd49df9)
Should I be concerned about these 5 failures? No other test systems
shows any problems...
thanks,
greg k-h
On Thu, Jul 13, 2017 at 01:47:46PM -0700, kernelci.org bot wrote:
> stable-rc/linux-4.9.y boot: 246 boots: 6 failed, 237 passed with 2 offline, 1
> conflict (v4.9.37-26-g996828f64cac)
Are these 6 failures "ok" to ignore?
thanks,
greg k-h
Hi Linus,
Here are a couple of mmc fixes intended for v4.13 rc1. They are based
on a commit from your tree earlier during the merge window and have
been tested in linux-next for a few days.
Details are as usual found in the signed tag. Please pull this in!
Kind regards
Ulf Hansson
The followin
1 - 100 of 777 matches
Mail list logo
