On 11/29/15, 10:23 PM, Daniel J Blueman wrote:
On Mon, Nov 30, 2015 at 11:09 AM, Zheng, Lv wrote:
Hi,
IMO, if you want the new _CRS to be applied during the Linux early
boot stage, you can override the table using initrd override or DSDT
override mechanism.
Please see Documentation/acpi/initrd
On 12/21/2015 03:17 PM, Joonsoo Kim wrote:
On Mon, Dec 21, 2015 at 03:00:08PM +0800, Zhu Guihua wrote:
On 12/21/2015 11:15 AM, Joonsoo Kim wrote:
Hello, memory-hotplug folks.
I found theoretical problems between memory hotplug and pfn iterator.
For example, pfn iterator works something like b
Hi all,
Changes since 20151218:
The orangefs tree gained a conflict against Linus' tree.
The i2c tree still had its build failure for which I applied a patch.
The clockevents tree lost its build failure but gained a conflict against
the tip tree.
The cgroup tree gained conflict against the tip
On 12/2/15, 6:55 PM, John Stultz wrote:
On Wed, Dec 2, 2015 at 3:42 PM, Andy Lutomirski wrote:
On a hunch, are you running chrony instead of ntpd?
Yes, this is indeed chrony.
Ok. I'll have to look closer. The last time that message came up it
was in a report of a bug that chrony uncovered
On 12/19/2015 03:30 PM, Aaro Koskinen wrote:
> Probably DMA support is not that critical. Looks like with DT boot it's
> not even possible to enable it at the moment.
I think by adding 'dma-channel' property is there to enable the DMA mode via DT.
As for stripping out the DMA support: I'm fine wi
On 15/12/2015 at 15:02:49 -0800, Julius Werner wrote :
> In A.D. 1582 Pope Gregory XIII found that the existing Julian calendar
> insufficiently represented reality, and changed the rules about
> calculating leap years to account for this. Similarly, in A.D. 2013
> Rockchip hardware engineers found
On 08/12/2015 at 16:28:39 +, Steve Twiss wrote :
> From: Steve Twiss
>
> This fix alters the ordering of the IRQ and device registrations in the RTC
> driver probe function. This change will apply to the RTC driver that supports
> both DA9063 and DA9062 PMICs.
>
> A problem could occur with
The setup() callback is not used by any in kernel code. Remove it.
Any new code which requires access to the eeprom can use the NVMEM
API.
Signed-off-by: Andrew Lunn
---
drivers/misc/eeprom/at25.c | 26 --
include/linux/spi/eeprom.h | 2 --
2 files changed, 28 deletions(
Add a regmap for accessing the EEPROM, and then use that with the
NVMEM framework. Set the NVMEM config structure to enable backward, so
that the 'eeprom' file in sys is provided by the framework.
Signed-off-by: Andrew Lunn
---
drivers/misc/eeprom/Kconfig | 2 +
drivers/misc/eeprom/at24.c | 1
Add a regmap for accessing the EEPROM, and then use that with the
NVMEM framework. Enable backward compatibility in the MVMEM config
structure, so that the 'eeprom' file in sys is provided by the
framework.
Signed-off-by: Andrew Lunn
---
drivers/misc/eeprom/Kconfig | 2 +
drivers/misc/
Older drivers made an 'eeprom' file available in the /sys device
directory. Have the NVMEM core provide this to retain backwards
compatibility.
Signed-off-by: Andrew Lunn
---
drivers/nvmem/core.c | 77 +-
include/linux/nvmem-provider.h | 4 ++-
This patch set converts the old EEPROM drivers in driver/misc/eeprom to
use the NVMEM framework. These drivers export there content in /sys as
read only to root, since the EEPROM may contain sensitive information.
So the first patch adds a flag so the NVMEM framework will create its
file in /sys as
On 11/30/15, 12:10 PM, Greg Kroah-Hartman wrote:
On Mon, Nov 30, 2015 at 02:53:49PM +0900, Masahiro Yamada wrote:
2015-11-28 9:04 GMT+09:00 Greg Kroah-Hartman :
On Fri, Nov 27, 2015 at 07:21:06PM +0900, Masahiro Yamada wrote:
Hi,
If I add "earlycon" to the kernel parameter, the log message
o
Legacy AT24, AT25 EEPROMs are exported in sys so that only root can
read the contents. The EEPROMs may contain sensitive information. Add
a flag so the provide can indicate that NVMEM should also restrict
access to root only.
Signed-off-by: Andrew Lunn
---
drivers/nvmem/core.c | 57 +++
Add a regmap for accessing the EEPROM, and then use that with the
NVMEM framework. Enable backwards compatibility in the NVMEM config,
so that the 'eeprom' file in sys is provided by the framework.
Signed-off-by: Andrew Lunn
---
drivers/misc/eeprom/Kconfig | 2 +
drivers/misc/eeprom/at25.c |
This text refers to the "first 7 functions", which was correct when
written but became incorrect when Johannes Weiner added another function
to the list in 139e561660fe ("lib: radix_tree: tree node interface").
Change the text to correctly refer to the first 8 functions.
Signed-off-by: Adam Barth
On Fri 18-12-15 20:04:51, Sasha Levin wrote:
> Commit "mm, oom: introduce oom reaper" forgot to initialize the two new fields
> of struct zap_details in unmap_mapping_range(). This caused using stack
> garbage
> on the call to unmap_mapping_range_tree().
>
> Signed-off-by: Sasha Levin
Thanks fo
On Mon, 21 Dec 2015 01:28:08 +0300
Roman Volkov wrote:
> From: Roman Volkov
>
> vt8500 hangs in nanosleep() function, starting from commit
> c6eb3f70d4482806dc2d3e1e3c7736f497b1d418, making the system unusable.
> Per investigation, looks like set_next_event() now receives too small
> delta and
Hi
On Sunday 20 December 2015 09:08 AM, Rob Herring wrote:
> On Tue, Dec 15, 2015 at 02:46:05PM +0530, Kishon Vijay Abraham I wrote:
>> Deprecate using phy-omap-control driver to power on/off the PHY and
>> use *syscon* framework to do the same.
>>
>> Signed-off-by: Kishon Vijay Abraham I
>> ---
Hi Jiri,
On Sun, Dec 20, 2015 at 03:12:45PM +0100, Jiri Olsa wrote:
> On Wed, Dec 16, 2015 at 12:35:39AM +0900, Namhyung Kim wrote:
>
> SNIP
>
> > struct trace_seq seq;
> > + char *str, *pos;
> > + struct format_field *field;
> > + struct pevent_record rec = {
> > + .cpu = h
On Fri 18-12-15 13:14:00, Andrew Morton wrote:
> On Fri, 18 Dec 2015 12:54:55 +0100 Michal Hocko wrote:
>
> > /* Retry the down_read_trylock(mmap_sem) a few times */
> > - while (attempts++ < 10 && !__oom_reap_vmas(mm))
> > - msleep_interruptible(100);
> > + while (attempts++ <
+Viresh
On Mon, Dec 21, 2015 at 2:58 AM, Måns Rullgård wrote:
> Andy Shevchenko writes:
>
>> On Sun, Dec 20, 2015 at 8:49 PM, Måns Rullgård wrote:
>>> Julian Margetson writes:
On 12/20/2015 1:11 PM, Måns Rullgård wrote:
> Julian Margetson writes:
>>
[ 48.769671] ata3.00: faile
Somehow this variable name screwed up in some rebase, fixed it.
Reported-by: Stephen Rothwell
Reported-by: Pramod Kumar
Signed-off-by: Linus Walleij
---
drivers/pinctrl/bcm/pinctrl-iproc-gpio.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pinctrl/bcm/pinctrl-ipro
https://github.com/jsakkine/linux-tpmdd.git tags/tpmdd-next-20151221
for you to fetch changes up to 5beb0c435bdde35a09376566b0e28f7df87c9f68:
keys, trusted: seal with a TPM2 authorization policy (2015-12-20 15:27:13
+0200)
tpmdd update
On Sun, Dec 20, 2015 at 03:58:42PM +0100, Jiri Olsa wrote:
> On Wed, Dec 16, 2015 at 12:35:41AM +0900, Namhyung Kim wrote:
> > The --raw-trace option is to prevent pretty printing by event's
> > print_fmt or plugin. Besides that, each dynamic sort key now receives
> > 'raw' suffix separated by '/'
On Mon, Dec 21, 2015 at 5:58 AM, Stephen Rothwell wrote:
> After merging the pinctrl tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
Argh damned, I pushed a oneliner fix in accordance with Pramod's
report. Sorry about the mess.
Yours,
Linus Walleij
--
To unsubscribe
On Mon, Dec 21, 2015 at 6:02 AM, Stephen Rothwell wrote:
> Hi Linus,
>
> On Wed, 16 Dec 2015 14:37:55 +1100 Stephen Rothwell
> wrote:
>>
>> After merging the gpio tree, today's linux-next build (arm
>> multi_v7_defconfig) failed like this:
>>
>> drivers/pinctrl/bcm/pinctrl-nsp-gpio.c: In functio
Some OMAP interrupt controllers use generic level detection, so
handle_level_irq() is used as the chip type handler.
Allocated IRQ chip type handler doesn't need to set it again because
irq_alloc_domain_generic_chips() has already registered it.
Tested with BeagleBoneBlack Rev C.
Cc: Tony Lindgre
phy-omap-control driver was added when there was no proper
infrastructure for doing control module initializations. The
phy-omap-control driver is not an 'actual' PHY driver and it
was just a hack to do PHY related control module initializations.
phy-omap-control is also getting unmanageable with t
No functional change. Previously omap_control_phy_power() was used to power
off the PHY during probe. But once PIPE3 driver is adapted to use syscon,
omap_control_phy_power() cannot be used. Hence used ti_pipe3_power_off
to power off the PHY.
Signed-off-by: Kishon Vijay Abraham I
Acked-by: Roger
No functional change. Previously omap_control_phy_power() was used to power
off the PHY during probe. But once phy-omap-usb2 driver is adapted to
use syscon, omap_control_phy_power() cannot be used. Hence used
omap_usb_power_off to power off the PHY.
Signed-off-by: Kishon Vijay Abraham I
Acked-by
Deprecate using phy-omap-control driver to power on/off the PHY and
use *syscon* framework to do the same.
Signed-off-by: Kishon Vijay Abraham I
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/phy/ti-phy.txt | 10 ++-
drivers/phy/phy-ti-pipe3.c | 88 +++
Deprecate using phy-omap-control driver to power on/off the PHY,
and use *syscon* framework to do the same. This handles
powering on/off the PHY for the USB2 PHYs used in various TI SoCs.
Signed-off-by: Kishon Vijay Abraham I
---
Documentation/devicetree/bindings/phy/ti-phy.txt |8 +-
driver
Deprecate using phy-omap-control driver to set PCS value of the PHY
and start using *syscon* API to do the same.
Signed-off-by: Kishon Vijay Abraham I
Acked-by: Roger Quadros
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/phy/ti-phy.txt |2 ++
drivers/phy/phy-ti-pipe3.c
No functional change. Moved sysctrl initialization done in probe to a
separate function as part of cleaning up ti_pipe3_probe.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/phy/phy-ti-pipe3.c | 78 +---
1 file changed, 45 insertions(+), 33 deletions(
No functional change. Moved mem resource initialization done in
probe to a separate function as part of cleaning up
ti_pipe3_probe.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/phy/phy-ti-pipe3.c | 52
1 file changed, 33 insertions(+), 19 delet
Hi!
Am 21.12.2015 um 09:49 schrieb Mickaël Salaün:
>
> On 21/12/2015 01:20, Richard Weinberger wrote:
>> Am 21.12.2015 um 01:03 schrieb Mickaël Salaün:
>>> diff --git a/arch/um/kernel/skas/syscall.c b/arch/um/kernel/skas/syscall.c
>>> index 1683b8e..65f0d1a 100644
>>> --- a/arch/um/kernel/skas/sy
No functional change. Moved clock initialization done in probe to a
separate function as part of cleaning up ti_pipe3_probe.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/phy/phy-ti-pipe3.c | 127 +---
1 file changed, 72 insertions(+), 55 deletions(-)
No functional change. Introduce local struct device pointer in
probe and replace using &pdev->dev/phy->dev with the local
device pointer. This is in preparation to split ti_pipe3_probe
and add separate functions for getting mem resource, getting
sysctrl and getting clocks.
Signed-off-by: Kishon Vi
On 19.12.2015 21:50, Cong Wang wrote:
> On Fri, Dec 18, 2015 at 5:13 PM, Sasha Levin wrote:
>> Hi Hannes,
>>
>> I've hit the following out of bounds access while fuzzing on the latest
>> -next kernel.
>>
>> This code was added in 3d1bec9932 ("ipv6: introduce secret_stable to
>> ipv6_devconf").
>
[sending the mail again, Thunderbird crashed :-\]
Am 21.12.2015 um 09:49 schrieb Mickaël Salaün:
>
> On 21/12/2015 01:20, Richard Weinberger wrote:
>> Am 21.12.2015 um 01:03 schrieb Mickaël Salaün:
>>> diff --git a/arch/um/kernel/skas/syscall.c b/arch/um/kernel/skas/syscall.c
>>> index 1683b8e..6
On Sat, Dec 19, 2015 at 04:31:24PM +0100, Julia Lawall wrote:
> The regulator_ops structures are never modified, so declare them as const.
>
> Done with the help of Coccinelle.
>
> Signed-off-by: Julia Lawall
>
> ---
Acked-by: Charles Keepax
Thanks,
Charles
--
To unsubscribe from this list:
This series is basically to deprecate using ctrl-module property and use
corresponding syscon properties to program the control module registers.
Changes from v3:
*) Renamed 'tisyscon@1c24' node to 'scm_conf@1c24'
Changes from v2:
No changes.
Changes from v1:
*) Squashed the patches that replace
The USB2 PHY2 has a different register map compared to USB2 PHY1
to power on/off the PHY. In order to handle it, use the new compatible
string "ti,dra7x-usb2-phy2" for the second instance of USB2 PHY.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/dra7.dtsi |3 ++-
1 file change
Add "syscon-phy-power" property and remove the deprecated "ctrl-module"
property from SATA and USB PHY node. Also remove the unused control
module dt nodes.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/am4372.dtsi | 16 ++--
arch/arm/boot/dts/dra7.dtsi | 34 -
On 21/12/2015 01:20, Richard Weinberger wrote:
> Am 21.12.2015 um 01:03 schrieb Mickaël Salaün:
>> diff --git a/arch/um/kernel/skas/syscall.c b/arch/um/kernel/skas/syscall.c
>> index 1683b8e..65f0d1a 100644
>> --- a/arch/um/kernel/skas/syscall.c
>> +++ b/arch/um/kernel/skas/syscall.c
>> @@ -7,6 +7
Add new device tree node for the control module register space where
PCIe registers are present.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/dra7.dtsi |5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/dra7.dtsi b/arch/arm/boot/dts/dra7.dtsi
index fe992
Add "syscon-phy-power" property and "syscon-pcs" property which can
be used to perform the control module initializations and remove
the deprecated "ctrl-module" property from PCIe PHY dt nodes.
Phandle to "sysclk" clock node is also added to the PCIe PHY node
since some of the syscon initializati
Add "syscon-phy-power" property and "syscon-pcs" property which can
be used to perform the control module initializations and remove
the deprecated "ctrl-module" property from PCIe PHY dt nodes.
Phandle to "sysclk" clock node is also added to the PCIe PHY node
since some of the syscon initializati
Add "syscon-phy-power" property and remove the deprecated "ctrl-module"
property from SATA and USB PHY node. Also remove the unused control
module dt nodes.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/am4372.dtsi | 16 ++--
arch/arm/boot/dts/dra7.dtsi | 34 -
Add new device tree node for the control module register space where
PCIe registers are present.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/dra7.dtsi |5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/dra7.dtsi b/arch/arm/boot/dts/dra7.dtsi
index fe992
This series is basically to deprecate using ctrl-module property and use
corresponding syscon properties to program the control module registers.
Changes from v3:
*) Renamed 'tisyscon@1c24' node to 'scm_conf@1c24'
Changes from v2:
No changes.
Changes from v1:
*) Squashed the patches that replace
The USB2 PHY2 has a different register map compared to USB2 PHY1
to power on/off the PHY. In order to handle it, use the new compatible
string "ti,dra7x-usb2-phy2" for the second instance of USB2 PHY.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/dra7.dtsi |3 ++-
1 file change
> This should be static, yeah.
Would you like to integrate a corresponding small source code change yourself?
(Do you need a separate patch from me?)
Regards,
Markus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
Mo
Hi,
This is the very basic support for the adc introduced with the SAMA5D2 SoC
family.
The goal is to provide something to the user as soon as possible instead of
waiting for a full featured driver.
Only unsigned conversions on a software tigger are supported. Next steps are
signed conversions,
This driver supports the new version of the Atmel ADC device introduced
with the SAMA5D2 SoC family.
Signed-off-by: Ludovic Desroches
---
.../devicetree/bindings/iio/adc/at91_adc8xx.txt| 27 ++
drivers/iio/adc/Kconfig| 11 +
drivers/iio/adc/Makefile
Enable the adc on the sama5d2 Xplained board.
Signed-off-by: Ludovic Desroches
---
arch/arm/boot/dts/at91-sama5d2_xplained.dts | 22 ++
1 file changed, 22 insertions(+)
diff --git a/arch/arm/boot/dts/at91-sama5d2_xplained.dts
b/arch/arm/boot/dts/at91-sama5d2_xplained.dts
in
Signed-off-by: Ludovic Desroches
---
MAINTAINERS | 6 ++
1 file changed, 6 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index a27c660..5971c25 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1927,6 +1927,12 @@ M: Nicolas Ferre
S: Supported
F: drivers/tty/serial/atmel_
Add the ADC device.
Signed-off-by: Ludovic Desroches
---
arch/arm/boot/dts/sama5d2.dtsi | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/sama5d2.dtsi b/arch/arm/boot/dts/sama5d2.dtsi
index 545264b..91c6e42 100644
--- a/arch/arm/boot/dts/sama5d2.dt
Signed-off-by: Ludovic Desroches
---
arch/arm/configs/sama5_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/sama5_defconfig b/arch/arm/configs/sama5_defconfig
index c11bab7..afbda41 100644
--- a/arch/arm/configs/sama5_defconfig
+++ b/arch/arm/configs/sama5_defconfig
On 21-12-15, 10:20, SF Markus Elfring wrote:
> > This should be static, yeah.
>
> Would you like to integrate a corresponding small source code change yourself?
> (Do you need a separate patch from me?)
Since you reported the issue, it will be good if you can send a patch
for this as well.
--
v
On 21/12/2015 10:00, Richard Weinberger wrote:
> [sending the mail again, Thunderbird crashed :-\]
>
> Am 21.12.2015 um 09:49 schrieb Mickaël Salaün:
>>
>> On 21/12/2015 01:20, Richard Weinberger wrote:
>>> Am 21.12.2015 um 01:03 schrieb Mickaël Salaün:
diff --git a/arch/um/kernel/skas/sysca
> In this case, there is indeed a problem. However, just changing the
> type won't fix it.
Would you like to explain your view on the handling of potential
data type mismatches a bit more?
Regards,
Markus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Sun, Dec 20, 2015 at 12:15:52PM +0100, Julia Lawall wrote:
> Add NULL test on call to kzalloc.
>
> The semantic match that finds this problem is as follows:
> (http://coccinelle.lip6.fr/)
>
> //
> @@
> expression x;
> identifier fld;
> @@
>
> * x = kzalloc(...);
> ... when != x == NULL
>
On 12/20/2015 01:15 PM, Julia Lawall wrote:
> Add NULL test on call to devm_kzalloc.
>
> The semantic match that finds this problem is as follows:
> (http://coccinelle.lip6.fr/)
>
> //
> @@
> expression x;
> identifier fld;
> @@
>
> * x = devm_kzalloc(...);
> ... when != x == NULL
> x->fld
On 12/18/2015 05:52 AM, Benjamin Tissoires wrote:
> On Thu, Nov 26, 2015 at 3:21 PM, Jiri Kosina wrote:
>> On Fri, 20 Nov 2015, Allen Hung wrote:
>>
>>> The usage Confidence is mandary to Windows Precision Touchpad devices. The
>>> appearance of this usage is checked in hidinput_connect but the qu
On Sun, Dec 13, 2015 at 08:51:49PM +0200, Aya Mahfouz wrote:
> Constifies hmcdrv_ftp_ops structures in s390's char
> driver since they are not modified after their
> initialization.
>
> Detected and found using Coccinelle.
>
> Suggested-by: Julia Lawall
> Signed-off-by: Aya Mahfouz
> ---
> dri
> Since you reported the issue, it will be good if you can send a patch
> for this as well.
I'm sorry if I become a bit picky for this implementation detail.
In which order would you prefer that the properties of the
function "cpu_set_cclk" will be improved?
* Should the linkage specifier be adde
On 21-12-15, 10:50, SF Markus Elfring wrote:
> In which order would you prefer that the properties of the
> function "cpu_set_cclk" will be improved?
> * Should the linkage specifier be added on a separate source code line?
No, it can be there in the same line.
> * Can this fix be combined with m
ip6addrlbl_get() has never worked. If ip6addrlbl_hold() succeeded,
ip6addrlbl_get() will exit with '-ESRCH'. If ip6addrlbl_hold() failed,
ip6addrlbl_get() will use about to be free ip6addrlbl_entry pointer.
Fix this by inverting ip6addrlbl_hold() check.
Fixes: 2a8cc6c89039 ("[IPV6] ADDRCONF: Supp
Below is the list of build error/warning regressions/improvements in
v4.4-rc6[1] compared to v4.3[2].
Summarized:
- build errors: +10/-11
- build warnings: +174/-104
JFYI, when comparing v4.4-rc6[1] to v4.4-rc5[3], the summaries are:
- build errors: +4/-7
- build warnings: +66/-39
Note t
Roman Volkov mail.ru> writes:
>
> From: Roman Volkov v1ros.org>
>
> vt8500 timer requires special synchronization for accessing some of its
> registers. Define special read and write functions to handle this process
> transparently.
Maybe introduce such accessor functions (conditionally) into
> I think the first patch is already Acked now and can be applied
> as it is. Just send the next patch based on the previous one.
Does it matter to provide the proposed changes as a tiny patch series
with two update steps?
Regards,
Markus
--
To unsubscribe from this list: send the line "unsubscri
On 21-12-15, 11:00, SF Markus Elfring wrote:
> Does it matter to provide the proposed changes as a tiny patch series
> with two update steps?
Yeah, you can do it that way as well :)
--
viresh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to m
On Mon, Dec 21, 2015 at 10:30:27AM +0100, SF Markus Elfring wrote:
> > In this case, there is indeed a problem. However, just changing the
> > type won't fix it.
>
> Would you like to explain your view on the handling of potential
> data type mismatches a bit more?
Yes, I will explain in the pat
Am 21.12.2015 um 10:23 schrieb Mickaël Salaün:
Doesn't this break the support for changing syscall numbers using
PTRACE_SETREGS?
>>>
>>> The logic is unchanged except updating the UPT_SYSCALL_NR before
>>> syscall_trace_enter(). I did my last tests with the x86_32 subarchitecture
>>> a
Andrew Morton writes:
> On Fri, 18 Dec 2015 15:50:24 +0100 Vitaly Kuznetsov
> wrote:
>
>> Out of memory condition is not a bug and while we can't add new memory in
>> such case crashing the system seems wrong. Propagating the return value
>> from register_memory_resource() requires interface ch
On 12/19/2015 10:08 AM, Geliang Tang wrote:
Move lru_to_page() from internal.h to mm_inline.h.
The file already contains functionality related to lru.
Signed-off-by: Geliang Tang
Acked-by: Vlastimil Babka
---
include/linux/mm_inline.h | 2 ++
mm/internal.h | 2 --
mm/rea
On Mon, Dec 21, 2015 at 03:26:27AM +0200, Laurent Pinchart wrote:
> On Friday 18 December 2015 20:20:56 Robin Murphy wrote:
> > On 18/12/15 18:55, Doug Anderson wrote:
> > > 2. We still have the same problem that we're taking away all the
> > > contiguous memory that other users may want. I've got
On 18.12.2015 13:40, Arnd Bergmann wrote:
On Wednesday 16 December 2015 16:16:31 Tomasz Nowicki wrote:
Because of two patch series:
1. Jiang Liu's common interface to support PCI host bridge init
2. MMCONFIG refactoring (part of this patch set)
now we can think about generic ACPI based PCI host
David Vrabel writes:
> On 18/12/15 16:45, Vitaly Kuznetsov wrote:
>> Currently, all newly added memory blocks remain in 'offline' state unless
>> someone onlines them, some linux distributions carry special udev rules
>> like:
>>
>> SUBSYSTEM=="memory", ACTION=="add", ATTR{state}=="offline",
>>
Hi Olof,
On Sun, Dec 20, 2015 at 10:44:53AM -0800, Olof Johansson wrote:
> On Wed, Nov 11, 2015 at 12:39:13PM +0530, Afzal Mohammed wrote:
> > Enable TPS65217 regulator to have rootfs in MMC for Beagle Bone's.
> >
> > Suggested-by: Kishon Vijay Abraham I
> > Signed-off-by: Afzal Mohammed
> Ap
Greetings,
In every tree where 69e5d3f8 is applied, IFF a kvm guest display is set
up for Spice vs VNC, AND IFF I boot straight into runlevel 5 vs
stopping at 3 then telinit 5, the X server starts fine but as KDE is
initializing my session after login, the display hangs. Revert
$subject, and all
As of commit e488ca9f8d4f62c2 ("doc: dt: mtd: partitions: add compatible
property to "partitions" node"), the "partitions" subnode of an SPI
FLASH device node must have a compatible property. The partitions are no
longer detected if it is not present.
Signed-off-by: Geert Uytterhoeven
---
v2:
-
As of commit e488ca9f8d4f62c2 ("doc: dt: mtd: partitions: add compatible
property to "partitions" node"), the "partitions" subnode of an SPI
FLASH device node must have a compatible property. The partitions are no
longer detected if it is not present.
Signed-off-by: Geert Uytterhoeven
Acked-by: B
As of commit e488ca9f8d4f62c2 ("doc: dt: mtd: partitions: add compatible
property to "partitions" node"), the "partitions" subnode of an SPI
FLASH device node must have a compatible property. The partitions are no
longer detected if it is not present.
Signed-off-by: Geert Uytterhoeven
---
v2:
-
On Mon, Dec 21, 2015 at 10:57 AM, Geert Uytterhoeven
wrote:
> JFYI, when comparing v4.4-rc6[1] to v4.4-rc5[3], the summaries are:
> - build errors: +4/-7
Nothing serious to report.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 --
As of commit e488ca9f8d4f62c2 ("doc: dt: mtd: partitions: add compatible
property to "partitions" node"), the "partitions" subnode of an SPI
FLASH device node must have a compatible property. The partitions are no
longer detected if it is not present.
Signed-off-by: Geert Uytterhoeven
Acked-by: B
As of commit e488ca9f8d4f62c2 ("doc: dt: mtd: partitions: add compatible
property to "partitions" node"), the "partitions" subnode of an SPI
FLASH device node must have a compatible property. The partitions are no
longer detected if it is not present.
Signed-off-by: Geert Uytterhoeven
Acked-by: B
As of commit e488ca9f8d4f62c2 ("doc: dt: mtd: partitions: add compatible
property to "partitions" node"), the "partitions" subnode of an SPI
FLASH device node must have a compatible property. The partitions are no
longer detected if it is not present.
Signed-off-by: Geert Uytterhoeven
Acked-by: B
As of commit e488ca9f8d4f62c2 ("doc: dt: mtd: partitions: add compatible
property to "partitions" node"), the "partitions" subnode of an SPI
FLASH device node must have a compatible property. The partitions are no
longer detected if it is not present.
Signed-off-by: Geert Uytterhoeven
Acked-by: B
As of commit e488ca9f8d4f62c2 ("doc: dt: mtd: partitions: add compatible
property to "partitions" node"), the "partitions" subnode of an SPI
FLASH device node must have a compatible property. The partitions are no
longer detected if it is not present.
Signed-off-by: Geert Uytterhoeven
Acked-by: B
As of commit e488ca9f8d4f62c2 ("doc: dt: mtd: partitions: add compatible
property to "partitions" node"), the "partitions" subnode of an SPI
FLASH device node must have a compatible property. The partitions are no
longer detected if it is not present.
Signed-off-by: Geert Uytterhoeven
Acked-by: B
oc: dt: mtd: support
partitions in a special 'partitions' subnode"). Hence all of these are
now broken in -next, and will be broken in upstream during the merge
window.
This series fixes all users in next-20151221.
Tested on r8a7791/koelsch.
Changes since v1:
- Add Acked-by,
-
Hi,
On 20-12-15 22:05, Guenter Roeck wrote:
Reference counting is now implemented in the watchdog core and no longer
required in watchdog drivers.
Signed-off-by: Guenter Roeck
---
drivers/hwmon/sch56xx-common.c | 30 --
1 file changed, 30 deletions(-)
diff --git
On Mon, 21 Dec 2015 11:18:25 +0800
MaJun wrote:
> From: Ma Jun
>
> The current MSI framework can only support 256 platform MSIs.
>
> But on Hisilicon platform, some network related devices has about 500
> wired interrupts.
>
> To support these devices, we need a new maximum value more than 25
On 18.12.2015 19:56, ok...@codeaurora.org wrote:
On 17.12.2015 22:24, Sinan Kaya wrote:
Hi Tomasz,
On 12/16/2015 10:16 AM, Tomasz Nowicki wrote:
From the functionality point of view this series might be split into
the
following logic parts:
1. Make MMCONFIG code arch-agnostic which allows al
On 12/21/2015 07:13 AM, Joonsoo Kim wrote:
There is a performance drop report due to hugepage allocation and in there
half of cpu time are spent on pageblock_pfn_to_page() in compaction [1].
In that workload, compaction is triggered to make hugepage but most of
pageblocks are un-available for com
On 20/12/15 09:25, Michael S. Tsirkin wrote:
>
> I noticed that drivers/xen/xenbus/xenbus_comms.c uses
> full memory barriers to communicate with the other side.
> For example:
>
> /* Must write data /after/ reading the consumer index. * */
> mb();
>
>
On Wed, Dec 16, 2015 at 12:45:15PM -0800, Shi, Yang wrote:
> On 12/16/2015 3:13 AM, Will Deacon wrote:
> >On Tue, Dec 15, 2015 at 04:18:08PM -0800, Yang Shi wrote:
> >>The kernel just send out a SIGTRAP signal when handling ptrace breakpoint in
> >>debug exception, so it sounds safe to have interru
1 - 100 of 854 matches
Mail list logo
