On Wed, Jan 11, 2017 at 06:14:09PM +0800, Baoyou Xie wrote:
> This patch adds dt-binding documentation for zx2967 family thermal sensor.
>
> Signed-off-by: Baoyou Xie
Reviewed-by: Shawn Guo
Rob already gave his ACK on v1. Since v2 is just an improved version of
v1 (without significant rewriti
This can reduce the backporting efforts.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/segment.c | 30 +-
1 file changed, 17 insertions(+), 13 deletions(-)
diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
index 0738f48293cc..ebfd5cd7619e 100644
--- a/fs/f2fs/segment.c
+++
On 01/11/2017 04:22 PM, Khalid Aziz wrote:
...
> All of the tag coordination can happen in userspace. Once a process sets
> a tag on a physical page mapped in its address space, another process
> that has mapped the same physical page in its address space can only set
> the tag to exact same value.
Hi,
On Tue, Jan 10, 2017 at 11:58 AM, Heiko Stübner wrote:
> Hi Doug,
>
> Am Dienstag, 10. Januar 2017, 20:46:12 schrieb Heiko Stübner:
>> Am Dienstag, 10. Januar 2017, 10:45:48 schrieb Doug Anderson:
>> > Hi,
>> >
>> > On Mon, Jan 9, 2017 at 10:15 PM, Xing Zheng
>>
>> wrote:
>> > > The structur
On 01/12/2017 02:47 AM, Alex Williamson wrote:
> On Thu, 22 Dec 2016 00:10:15 +0800
> Jike Song wrote:
>
>> has_capability() is sometimes needed by modules to test capability
>> for specified task other than current, so export it.
>>
>> Cc: Alex Williamson
>> Cc: Kirti Wankhede
>> Signed-off-by
On Wed, 2017-01-11 at 15:57 -0800, Andrew Morton wrote:
> On Wed, 11 Jan 2017 18:28:07 +0200 Andy Shevchenko
> wrote:
>
> > While resource_size_t is repeating phys_addr_t, allocate %par specifier for
> > that type for sake of consistency.
> >
>
> I'm struggling to see the value in this. A mor
On Wed, Jan 11, 2017 at 06:14:11PM +0800, Baoyou Xie wrote:
> This patch adds thermal driver for ZTE's zx2967 family.
>
> Signed-off-by: Baoyou Xie
Looks fine to me, except a few minor comments below.
> ---
> drivers/thermal/Kconfig | 6 +
> drivers/thermal/Makefile | 1 +
Hi Bjorn,
On 01/12/2017 03:50 AM, Bjorn Helgaas wrote:
> Hi Jaehoon,
>
> On Mon, Dec 19, 2016 at 05:16:11PM +0900, Jaehoon Chung wrote:
>> There is no reason to maintain *_blk/phy/elbi_* as register accessors.
>> It can be replaced to one register accessor.
>>
>> Signed-off-by: Jaehoon Chung
>>
The mm-of-the-moment snapshot 2017-01-11-17-14 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You wi
Hi, Jonathan,
Jonathan Corbet writes:
> On Wed, 11 Jan 2017 15:00:29 -0800
> Andrew Morton wrote:
>
>> hm, bit_spin_lock() is a nasty thing. It is slow and it doesn't have
>> all the lockdep support.
>>
>> Would the world end if we added a spinlock to swap_cluster_info?
>
> FWIW, I asked the
> -Original Message-
> From: Russell King - ARM Linux [mailto:li...@armlinux.org.uk]
> Sent: 2017年1月11日 19:18
> To: Jean-Jacques Hiblot
> Cc: Wenyou Yang - A41535 ; Alexandre Belloni
> ; Mark Rutland ;
> devicetree ; Nicolas Ferre
> ; Linux Kernel Mailing List ker...@vger.kernel.org>; r
Am Mittwoch, 11. Januar 2017, 16:50:10 CET schrieb Doug Anderson:
> Hi,
>
> On Tue, Jan 10, 2017 at 11:58 AM, Heiko Stübner wrote:
> > Hi Doug,
> >
> > Am Dienstag, 10. Januar 2017, 20:46:12 schrieb Heiko Stübner:
> >> Am Dienstag, 10. Januar 2017, 10:45:48 schrieb Doug Anderson:
> >> > Hi,
> >>
Reviewed-by: Yijing Wang
在 2017/1/11 23:44, Bjorn Helgaas 写道:
> PCI: Enumerate switches below PCI-to-PCIe bridges
>
> A PCI-to-PCIe bridge (a "reverse bridge") has a PCI or PCI-X primary
> interface and a PCI Express secondary interface. The PCIe interface is a
> Downstream Port that originates
On 01/11/2017 04:12 PM, Andy Shevchenko wrote:
On Wed, Jan 11, 2017 at 12:52 PM, Guenter Roeck wrote:
On 01/11/2017 01:07 AM, Marc Gonzalez wrote:
Not really. It would just make it more complicated to replace the
call with devm_clk_prepare_enable(), should it ever find its way
into the light of
FYI, we noticed the following commit:
commit: ddb08a630e369fa2e327ece8e406bcdc3285b064 ("blk-mq-sched: fixes")
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git tmp-sched
in testcase: boot
on test machine: qemu-system-i386 -enable-kvm -cpu Haswell,+smep,+smap -m 360M
caused
On Wed, Jan 11, 2017 at 12:02:10PM +0200, Mika Westerberg wrote:
> On Sun, Jan 08, 2017 at 09:41:45AM +0100, Lukas Wunner wrote:
> > Hotplug ports generally block their parents from suspending to D3hot as
> > otherwise their interrupts couldn't be delivered.
> >
> > An exception are Thunderbolt ho
On Tue, Jan 10, 2017 at 10:00:38PM +0100, Peter Zijlstra wrote:
> > +static inline int add_chain_cache_classes(unsigned int prev,
> > + unsigned int next,
> > + unsigned int irq_context,
> > +
Hi, Andrew,
Andrew Morton writes:
> On Wed, 11 Jan 2017 16:07:29 -0700 Jonathan Corbet wrote:
>
>> On Wed, 11 Jan 2017 15:00:29 -0800
>> Andrew Morton wrote:
>>
>> > hm, bit_spin_lock() is a nasty thing. It is slow and it doesn't have
>> > all the lockdep support.
>> >
>> > Would the world
Hi Santosh,
This is a slightly updated patch series for the reset controller nodes for
TI Keystone2 SoCs. The only change is to rename the reset controller nodes
from "psc-reset-controller" to just "reset-controller" following Rob Herring's
comment on the Documentation update patch [1]. There are
The Power Sleep Controller (PSC) module is responsible
for the power and clock management for each of the peripherals
present on the SoC. Represent this as a syscon node so that
multiple users can leverage it for various functionalities.
Signed-off-by: Suman Anna
[a...@ti.com: add simple-mfd comp
The Keystone 2 family of SoCs will use various Reset Controller
drivers for managing the resets of remote processor devices like
DSPs on the SoC, so select the ARCH_HAS_RESET_CONTROLLER option
by default to enable the Reset framework.
Signed-off-by: Suman Anna
Signed-off-by: Nishanth Menon
---
v
The Power Sleep Controller (PSC) module contains specific
memory-mapped registers that can be used to perform reset
management using specific bits for the DSPs available on the
SoC. The PSC is defined using a syscon node, and the reset
functionality is defined using a child syscon reset controller
The Power Sleep Controller (PSC) module contains specific
memory-mapped registers that can be used to perform reset
management using specific bits for the DSPs available on the
SoC. The PSC is defined using a syscon node, and the reset
functionality is defined using a child syscon reset controller
The Power Sleep Controller (PSC) module contains specific
memory-mapped registers that can be used to perform reset
management using specific bits for the DSPs available on the
SoC. The PSC is defined using a syscon node, and the reset
functionality is defined using a child syscon reset controller
On Wednesday 11 January 2017 09:23 PM, Linus Walleij wrote:
On Wed, Jan 11, 2017 at 1:40 PM, Keerthy wrote:
On Wednesday 11 January 2017 04:34 PM, Linus Walleij wrote:
On Wed, Jan 4, 2017 at 9:26 AM, Keerthy wrote:
gpio2regs is written making an assumption that driver supports only
one in
On Wednesday 11 January 2017 11:07 PM, Grygorii Strashko wrote:
On 01/10/2017 11:00 PM, Keerthy wrote:
Remove redundant blank line.
i think it's better to drop this patch ;)
There were already too many things in the second patch so just did not
want to add more lines of code change :-P.
On Thu, 12 Jan 2017 09:47:51 +0800 "Huang\, Ying" wrote:
> >> > 1MB swap space, so for 1TB swap space, the total size will be 80M
> >> > compared with 8M of current implementation.
> >
> > Where did this 80 bytes come from? That swap_cluster_info is 12 bytes
> > and could perhaps be squeezed int
On Wednesday 11 January 2017 11:23 PM, Grygorii Strashko wrote:
On 01/10/2017 11:00 PM, Keerthy wrote:
The Davinci GPIO driver is implemented to work with one monolithic
Davinci GPIO platform device which may have up to Y(144) gpios.
The Davinci GPIO driver instantiates number of GPIO chips
Hi David, Linus,
I am seeing emails being received right now from @vger.kernel.org that
seem to be from this morning according to my mailer. Has anything
changed on vger.kernel.org that could cause that? Other mailing-lists
(e.g: infradead.org) seems to be fine.
Here is an example that seems to b
Hi Andrew,
On Wed, 11 Jan 2017 17:14:57 -0800 a...@linux-foundation.org wrote:
>
> The mm-of-the-moment snapshot 2017-01-11-17-14 has been uploaded to
>
>http://www.ozlabs.org/~akpm/mmotm/
Imported mostly fine ...
> linux-next-git-rejects.patch
That is not correct :-(
I used (more or le
On 1/11/2017 4:22 PM, John Stultz wrote:
> Just wanted to resend my patches for dwc2 controller on the
> HiKey board for consideration for the 4.11 merge window.
>
> This patchset is the same as v2, only rebased against
> John's synopsys-usb/next branch.
>
> This does still exclude my patchset[1]
From: Florian Fainelli
Date: Wed, 11 Jan 2017 18:01:47 -0800
> I am seeing emails being received right now from @vger.kernel.org that
> seem to be from this morning according to my mailer. Has anything
> changed on vger.kernel.org that could cause that? Other mailing-lists
> (e.g: infradead.org)
Just use the bitops api to operate the bit.
Signed-off-by: Jaehoon Chung
Reviewed-by: Pankaj Dubey
Acked-by: Krzysztof Kozlowski
---
Changelog on V2:
- None
drivers/pci/host/pci-exynos.c | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/drivers/pci
There is no reason to maintain *_blk/phy/elbi_* as register accessors.
It can be replaced to one register accessor.
Signed-off-by: Jaehoon Chung
Reviewed-by: Pankaj Dubey
Acked-by: Krzysztof Kozlowski
---
Changelog on V2;
- Changes the all pointer names as "ep" instead of "exynos_pcie"
driver
Remove the unnecessary variables(elbi/phy/block_base).
It needs one resource structure for assigning each resource.
So it replaces with one 'res' variable.
Signed-off-by: Jaehoon Chung
Reviewed-by: Pankaj Dubey
Acked-by: Krzysztof Kozlowski
---
Changelog on V2:
- None
drivers/pci/host/pci-exy
The correct error checking for dma_map_single() is to use
dma_mapping_error().
Signed-off-by: Kevin Hilman
---
Applies to v4.10-rc3
drivers/spi/spi-davinci.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/spi/spi-davinci.c b/drivers/spi/spi-davinci.c
index d36c1
Removed the duplicated codes.
It can use the more simply than now.
Signed-off-by: Jaehoon Chung
Reviewed-by: Pankaj Dubey
Acked-by: Krzysztof Kozlowski
---
Changelog on V2:
- None
drivers/pci/host/pci-exynos.c | 22 --
1 file changed, 8 insertions(+), 14 deletions(-)
diff
Resuming from RPM can happen while already holding
dev->mode_config.mutex. This means we can't actually handle fbcon in
any RPM resume workers, since restoring fbcon requires grabbing
dev->mode_config.mutex again. So move the fbcon suspend/resume code into
it's own worker, and rely on that instead
As it turns out, on cards that actually have CRTCs on them we're already
calling drm_kms_helper_poll_enable(drm_dev) from
nouveau_display_resume() before we call it in
nouveau_pmops_runtime_resume(). This leads us to accidentally trying to
enable polling twice, which results in a potential deadlock
On Wed, Jan 11, 2016 at 04:33:32PM +0800, Greg KH wrote:
> On Wed, Dec 14, 2016 at 04:33:32PM +0800, Yuan Yao wrote:
> > From: Yuan Yao
> >
> > Numbering the ttyLPn space should not depend on the generic name
> > "serial".
> >
> > If don't add the alias node like:"serial0 = &lpuart0;", then lpuart
On 1/11/17 5:48 PM, Suman Anna wrote:
Hi Santosh,
This is a slightly updated patch series for the reset controller nodes for
TI Keystone2 SoCs. The only change is to rename the reset controller nodes
from "psc-reset-controller" to just "reset-controller" following Rob Herring's
comment on the Do
Simplify return logic to avoid unnecessary variable assignments.
These issues were detected using Coccinelle and the following semantic patch:
@@
local idexpression ret;
expression e;
@@
-ret =
+return
e;
-return ret;
Signed-off-by: Gustavo A. R. Silva
---
drivers/power/supply/ab8500_btem
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Tuesday, January 10, 2017 9:27 AM
> To: KY Srinivasan
> Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org;
> o...@aepfle.de; a...@canonical.com; vkuzn...@redhat.com;
> jasow...@redhat.com; leann
Simplify return logic to avoid unnecessary variable assignments.
These issues were detected using Coccinelle and the following semantic patch:
@@
local idexpression ret;
expression e;
@@
-ret =
+return
e;
-return ret;
Signed-off-by: Gustavo A. R. Silva
---
drivers/power/supply/pcf50633-ch
Andrew Morton writes:
> On Thu, 12 Jan 2017 09:47:51 +0800 "Huang\, Ying"
> wrote:
>
>> >> > 1MB swap space, so for 1TB swap space, the total size will be 80M
>> >> > compared with 8M of current implementation.
>> >
>> > Where did this 80 bytes come from? That swap_cluster_info is 12 bytes
>>
Hi,
On Wed, Jan 11, 2017 at 12:44:37PM +1100, Chris Lapa wrote:
> This patch series correctly renames the patch subject prefix to
> 'power: supply: bq27xxx'.
>
> It also fixes up the deprecation of the BQ27500 and BQ27510 definitions.
>
> Otherwise the patch content is the same functionally as t
On Wed, Jan 11, 2017 at 1:10 PM, Dexuan Cui wrote:
>> From: Dexuan Cui
>> Sent: Tuesday, December 20, 2016 11:41
>> To: 'Jens Axboe' ; Ming Lei
>> Cc: Linux Kernel Mailing List ; linux-block
>> ; Christoph Hellwig ;
>> Vitaly Kuznetsov ; Keith Busch
>> ; Hannes Reinecke ; Mike Christie
>> ; Marti
Hi Michal,
On Tue, Jan 10, 2017 at 06:48:12PM +0100, Michal Suchanek wrote:
> Casting of_device_get_match_data return value to int causes warning on 64bit
> architectures.
>
> ../drivers/power/supply/axp20x_usb_power.c: In function
> 'axp20x_usb_power_probe':
> ../drivers/power/supply/axp20x_usb_
Hi Arnd,
On Wed, Jan 11, 2017 at 03:51:55PM +0100, Arnd Bergmann wrote:
> Casting a pointer to 'int' is not always valid:
>
> drivers/power/supply/axp20x_usb_power.c: In function 'axp20x_usb_power_probe':
> drivers/power/supply/axp20x_usb_power.c:297:21: error: cast from pointer to
> integer of
Fix couple of typos in the example given in the TI syscon reset
binding. The ti,reset-bits used for DSP0 are corrected to match
the values that will be used in the actual DT node.
Signed-off-by: Suman Anna
---
v2: Address Rob Herring's comment to change the reset node name
from "psc-reset" to
On Tuesday, January 10, 2017 12:35 AM Mel Gorman wrote:
>
> buffered_rmqueue removes a page from a given zone and uses the per-cpu
> list for order-0. This is fine but a hypothetical caller that wanted
> multiple order-0 pages has to disable/reenable interrupts multiple
> times. This patch struct
On Tuesday, January 10, 2017 12:35 AM Mel Gorman wrote:
>
> alloc_pages_nodemask does a number of preperation steps that determine
> what zones can be used for the allocation depending on a variety of
> factors. This is fine but a hypothetical caller that wanted multiple
> order-0 pages has to do
> From: Ming Lei [mailto:ming@canonical.com]
> Sent: Thursday, January 12, 2017 10:54
> To: Dexuan Cui
> Cc: Jens Axboe ; Linux Kernel Mailing List ker...@vger.kernel.org>; linux-block ;
> Christoph Hellwig ; Vitaly Kuznetsov
> ; Keith Busch ; Hannes
> Reinecke ; Mike Christie ; Martin K.
> P
On 01/12/2017 at 03:35 AM, Robert LeBlanc wrote:
> On Wed, Dec 14, 2016 at 4:17 PM, Xunlei Pang wrote:
>> As I replied in another post, if you really want to detail the behaviour,
>> should mention
>> "crashkernel=size[KMG][@offset[KMG]]" with @offset[KMG] specified
>> explicitly, after
>> all,
Hi Tim,
On 01/11/2017 03:14 PM, Tim Harvey wrote:
Hi Steve,
I took a stab at testing this today on a gw51xx which has an adv7180
hooked up as follows:
- i2c3@0x20
- 8bit data bus from DAT12 to DAT19, HSYNC, VSYNC, PIXCLK on CSI0 pads
(CSI0_IPU1)
- PWRDWN# on MX6QDL_PAD_CSI0_DATA_EN__GPIO5_I
Hi Masami,
On Wed, Jan 11, 2017 at 07:08:40PM +0900, Masami Hiramatsu wrote:
Ping?
Oops, sorry for overlooking your previous email!
BTW, I found that the old toolchain is archived in release.linaro.org.
So I made a patch for that.
So there are gcc 4.9, 5, 6 versions available for aarch64.
BTW, I found that the old toolchain is archived in release.linaro.org.
So I made a patch for that.
Applied the patch, thank you!
Regards,
Fengguang
> "Subhash" == Subhash Jadavani writes:
Subhash> Colin Ian King reported that with
Subhash> commit 7ff5ab473633 ("scsi: ufs: add tracing support") static
Subhash> analysis is reporting that we may have swapped arguments on
Subhash> calls to:
[...]
Applied to 4.11/scsi-queue.
--
Martin K.
Fixes checkpatch CHECK:
Blank lines aren't necessary before a close brace '}'
Please don't use multiple blank lines
Signed-off-by: Scott Matheina
---
drivers/staging/wilc1000/wilc_sdio.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/staging/wilc1000/wilc_sdio.c
b/drivers/staging
Fixes checkpatch warning: braces {} should be used on all arms of
this statement
Signed-off-by: Scott Matheina
---
drivers/staging/wilc1000/host_interface.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/wilc1000/host_interface.c
b/drivers/staging/wilc1000
Fixes checkpatch CHECK: Alignment should match open parenthesis
Signed-off-by: Scott Matheina
---
drivers/staging/wilc1000/wilc_debugfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/wilc1000/wilc_debugfs.c
b/drivers/staging/wilc1000/wilc_debugfs.c
index 0
Fixes checkpatch CHECK: Please don't use multiple blank lines
Signed-off-by: Scott Matheina
---
drivers/staging/wilc1000/wilc_debugfs.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/staging/wilc1000/wilc_debugfs.c
b/drivers/staging/wilc1000/wilc_debugfs.c
index 52aac75..7d32de9 1
Fixes checkpatch CHECK: Alignment should match open parenthesis
Signed-off-by: Scott Matheina
---
drivers/staging/wilc1000/wilc_sdio.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/wilc1000/wilc_sdio.c
b/drivers/staging/wilc1000/wilc_sdio.c
index 3ad7cec..e
Fixed Alignment should match open parenthesis checkpatch CHECK.
Signed-off-by: Scott Matheina
---
drivers/staging/wlan-ng/cfg80211.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/wlan-ng/cfg80211.c
b/drivers/staging/wlan-ng/cfg80211.c
index aa0e5a3..1
Fixes checkpatch CHECK: Alignment should match open parenthesis
Signed-off-by: Scott Matheina
---
drivers/staging/wilc1000/linux_wlan.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/wilc1000/linux_wlan.c
b/drivers/staging/wilc1000/linux_wlan.c
index 185fcd1
Allow drivers to use the new DSA API with platform data. Most of the
code in net/dsa/dsa2.c does not rely so much on device_nodes and can get
the same information from platform_data instead.
We purposely do not support distributed configurations with platform
data, so drivers should be providing a
Hi all,
This is not exactly new, and was sent before, although back then, I did not
have an user of the pre-declared MDIO board information, but now we do. Note
that I have additional changes queued up to have b53 register platform data for
MIPS bcm47xx and bcm63xx.
Yes I know that we should have
Now that the base device driver code provides an identical
implementation of dev_find_class() utilize device_find_class() instead
of our own version of it.
Signed-off-by: Florian Fainelli
---
net/dsa/dsa.c | 22 ++
1 file changed, 2 insertions(+), 20 deletions(-)
diff --git
Allow board support code to collect pre-declarations for MDIO devices by
registering them with mdiobus_register_board_info(). SPI and I2C buses
have a similar feature, we were missing this for MDIO devices, but this
is particularly useful for e.g: MDIO-connected switches which need to
provide their
Utilize the ability to pass board specific MDIO bus information towards a
particular MDIO device thus allowing us to provide the per-port switch layout
to the Marvell 88E6XXX switch driver.
Since we would end-up with conflicting registration paths, do not register the
"dsa" platform device anymore
dev_to_net_device() is moved from net/dsa/dsa.c to net/core/dev.c since
it going to be used by net/dsa/dsa2.c and the namespace of the function
justifies making it available to other users potentially.
Signed-off-by: Florian Fainelli
---
include/linux/netdevice.h | 2 ++
net/core/dev.c
In preparation for allowing platform data, and therefore no valid
device_node pointer, make most DSA functions takes a pointer to a
dsa_port structure whenever possible. While at it, introduce a
dsa_port_is_valid() helper function which checks whether port->dn is
NULL or not at the moment.
Signed-
Add a helper function to lookup a device reference given a class name.
This is a preliminary patch to remove adhoc code from net/dsa/dsa.c and
make it more generic.
Signed-off-by: Florian Fainelli
---
drivers/base/core.c| 19 +++
include/linux/device.h | 1 +
2 files changed
Move the assignment of ports in _dsa_register_switch() closer to where
it is checked, no functional change. Re-order declarations to be
preserve the inverted christmas tree style.
Signed-off-by: Florian Fainelli
---
net/dsa/dsa2.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --g
Make it clear that these functions take a device_node structure pointer
Signed-off-by: Florian Fainelli
---
net/dsa/dsa2.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/net/dsa/dsa2.c b/net/dsa/dsa2.c
index 6e3675220fef..04ab62251fe3 100644
--- a/net/dsa/ds
In preparation for allowing dsa_register_switch() to be supplied with
device/platform data, pass down a struct device pointer instead of a
struct device_node.
Signed-off-by: Florian Fainelli
---
drivers/net/dsa/b53/b53_common.c | 2 +-
drivers/net/dsa/mv88e6xxx/chip.c | 11 ++-
drivers/
Hi Milo,
On Fri, Dec 09, 2016 at 03:28:32PM +0900, Milo Kim wrote:
> Add interrupt specifiers for USB and AC charger input. Interrupt numbers
> are from the datasheet.
> Fix wrong property for compatible string.
>
> Signed-off-by: Milo Kim
> ---
> .../devicetree/bindings/power/supply/tps65217_c
Hi Andrew,
After merging the akpm tree, today's linux-next build (powerpc
allyesconfig) failed like this:
In file included from fs/ocfs2/file.c:49:0:
fs/ocfs2/file.c: In function 'ocfs2_permission':
fs/ocfs2/dlmglue.h:189:29: error: inlining failed in call to always_inline
'ocfs2_is_locked_by_me
Hi all,
Changes since 20170111:
New tree: aspeed
The akpm-current tree gained a build failure for which I applied a patch.
Non-merge commits (relative to Linus' tree): 2953
3790 files changed, 114528 insertions(+), 64138 dele
> "Johannes" == Johannes Thumshirn writes:
Johannes> Set variables initialized in
Johannes> lpfc_sli4_alloc_resource_identifiers() to NULL if an error
Johannes> occurred. Otherwise, lpfc_sli4_driver_resource_unset()
Johannes> attempts to free the memory again.
Applied to 4.10/scsi-fixes.
--
> -Original Message-
> From: Eric Auger [mailto:eric.au...@redhat.com]
> Sent: Wednesday, January 11, 2017 3:12 PM
> To: eric.au...@redhat.com; eric.auger@gmail.com;
> christoffer.d...@linaro.org; marc.zyng...@arm.com;
> robin.mur...@arm.com; alex.william...@redhat.com;
> will.dea...@
On 01/12/2017 05:36 AM, John Stultz wrote:
On Wed, Jan 11, 2017 at 12:48 AM, Archit Taneja wrote:
Hi,
On 01/04/2017 01:11 AM, John Stultz wrote:
Hope everyone had a good newyears!
Wanted to re-send out v3 of this patch set improving the EDID
probing on the adv7511 used on HiKey, for consi
On 01/12/2017 12:59 AM, Jes Sorensen wrote:
On 01/11/17 11:52, Shaohua Li wrote:
On Tue, Jan 10, 2017 at 11:49:04AM -0600, Bruce Dubbs wrote:
Jes Sorensen wrote:
I am pleased to announce the availability of
mdadm version 4.0
It is available at the usual places:
http://www.kernel.o
When memory.move_charge_at_immigrate is enabled and precharges are
depleted during move, mem_cgroup_move_charge_pte_range() will attempt to
increase the size of the precharge.
This livelocks if reclaim fails and if an oom killed process attached to
the destination memcg is trying to exit, which re
On Wed, Jan 11, 2017 at 11:46 AM, Michal Hocko wrote:
> On Wed 11-01-17 20:45:25, Michal Hocko wrote:
>> On Wed 11-01-17 09:37:06, Chas Williams wrote:
>> > On Mon, 2017-01-09 at 18:20 +0100, Andrey Konovalov wrote:
>> > > Hi!
>> > >
>> > > I've got the following error report while running the syz
On 11-01-17, 16:00, Roman Sommer wrote:
> Note that this patch does not fix all checkpatch warnings for the
> affected files.
>
> Signed-off-by: Christian Bewermeyer
> Signed-off-by: Roman Sommer
>
> ---
> drivers/staging/greybus/gpio.c | 24
> drivers/staging/grey
Hi Matthias,
(Trying again to send plain text email)...
On Thu, Aug 4, 2016 at 10:57 AM, Bibby Hsieh wrote:
> To support HDMI 4K resolution, mmsys need clcok
> mm_sel to be 400MHz.
>
> The board .dts file should override the clock rate
> property with the higher VENCPLL frequency the board
> sup
Changed permissions to be in octal style.
Found by checkpatch.
Signed-off-by: Derek Robson
---
drivers/staging/greybus/camera.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/staging/greybus/camera.c b/drivers/staging/greybus/camera.c
index 0ee291ca2c72..a
Hi Stephen,
Thanks for your report and the fix for it. The 0-day project has reported
several days ago,
but this patch set is still in discussion, so I am waiting for more days to see if other
developers
have any other questions.
I am confused that how to deal with your patch if I need to w
Hello,
On Wed, Jan 11, 2017 at 04:52:39PM +0100, Michal Hocko wrote:
> On Wed 11-01-17 08:52:50, Minchan Kim wrote:
> [...]
> > > @@ -2055,8 +2055,8 @@ static bool inactive_list_is_low(struct
> > > if (!file && !total_swap_pages)
> > > return false;
> > >
> > > - inactive = lruvec_lr
Hi Bjorn,
On Thursday 12 January 2017 02:51 AM, Bjorn Helgaas wrote:
> On Fri, Dec 30, 2016 at 03:26:11PM +0530, Kishon Vijay Abraham I wrote:
>> This series contains
>> *) a patch to cleanup dra7xx probe
>> *) a patch to force DRA7xx controller to work in GEN1 mode
>> *) a
Hi, Xiaolong
I noticed the tested version in your the test dmesg: Linux version 4.9.0-rc5
While the commit bisected should be in v4.10-rc1.
Does that mean your test tree doesn't contain some basic lock fixes?
Thanks and best regards
Lv
> From: lkp-developer-requ...@eclists.intel.com
> [mailto:l
From: "Liu, Xinwu"
The schedule policy of thread "kidle_inject" is SCHED_NORMAL:
[ 772.796284] intel_powerclamp: Start idle injection to reduce power
[ 772.825757] [ cut here ]
[ 772.825877] WARNING: CPU: 0 PID: 2140 at
../../../../../../kernel/glv/kernel/sched/idle.c:
On Fri, January 6, 2017 4:10 pm, Logan Gunthorpe wrote:
>
>
> On 06/01/17 11:26 AM, Jason Gunthorpe wrote:
>
>
>> Make a generic API for all of this and you'd have my vote..
>>
>>
>> IMHO, you must support basic pinning semantics - that is necessary to
>> support generic short lived DMA (eg filesys
Hi Linus,
As promised last week, here's some stability fixes from Christoph and
Jan Kara. I think they fall within the guidelines for non-merge window
patches. Could you please pull the changes?
--Darrick
The following changes since commit a121103c922847ba5010819a3f250f1f7fc84ab8:
Linux 4.1
[Resend from the correct email account... sorry for the noise]
Hi Linus,
As promised last week, here's some stability fixes from Christoph and
Jan Kara. I think they fall within the guidelines for non-merge window
patches. Could you please pull the changes?
--Darrick
The following changes sin
On Tuesday 10 January 2017 11:25 PM, Mark Rutland wrote:
On Mon, Jan 02, 2017 at 01:49:37AM -0500, Anurup M wrote:
+The Hisilicon SoC HiP05/06/07 chips consist of various independent system
+device PMU's such as L3 cache(L3C) and Miscellaneous Nodes(MN).
+These PMU devices are independent and
>> @@ -959,6 +990,15 @@ void arch_setup_dma_ops(struct device *dev, u64
>> dma_base, u64 size,
>> if (!dev->archdata.dma_ops)
>> dev->archdata.dma_ops = &swiotlb_dma_ops;
>>
>> + /*
>> +* Whatever the parent bus can set. A device must not set
>> +* a
>> diff --git a/drivers/staging/fsl-mc/bus/fsl-mc-bus.c
>> b/drivers/staging/fsl-mc/bus/fsl-mc-bus.c
>> index 5ac373c..480b644 100644
>> --- a/drivers/staging/fsl-mc/bus/fsl-mc-bus.c
>> +++ b/drivers/staging/fsl-mc/bus/fsl-mc-bus.c
>> @@ -540,7 +540,7 @@ int fsl_mc_device_add(struct dprc_obj_desc
Hi, Lv
On 01/12, Zheng, Lv wrote:
>Hi, Xiaolong
>
>I noticed the tested version in your the test dmesg: Linux version 4.9.0-rc5
>While the commit bisected should be in v4.10-rc1.
>Does that mean your test tree doesn't contain some basic lock fixes?
The reported kernel version is Linux version 4.9
801 - 900 of 934 matches
Mail list logo
