From: Rik van Riel
The CONFIG_VIRT_CPU_ACCOUNTING_GEN irq time tracking code does not
appear to currently work right.
On CPUs that are nohz_full, people typically do not assign IRQs.
On the housekeeping CPU (when a system is booted up with nohz_full),
sampling should work ok to
From: Rik van Riel
Currently, if there was any irq or softirq time during 'ticks'
jiffies, the entire period will be accounted as irq or softirq
time.
This is inaccurate if only a subset of 'ticks' jiffies was
actually spent handling irqs, and could conceivably mis-count
all of
From: Rik van Riel
Currently, if there was any irq or softirq time during 'ticks'
jiffies, the entire period will be accounted as irq or softirq
time.
This is inaccurate if only a subset of 'ticks' jiffies was
actually spent handling irqs, and could conceivably mis-count
all of the ticks during
From: Rik van Riel
The CONFIG_VIRT_CPU_ACCOUNTING_GEN irq time tracking code does not
appear to currently work right.
On CPUs that are nohz_full, people typically do not assign IRQs.
On the housekeeping CPU (when a system is booted up with nohz_full),
sampling should work ok to determine irq
The i.MX 7 series currently consists of two SoCs: i.MX 7Solo and
7Dual. The i.MX 7Solo implements a subset of features available on
i.MX 7Dual, hence create imx7s.dtsi as the base device tree. The
i.MX 7Dual's additional features over i.MX 7Solo are:
- Second Cortex-A7 core
- Second Gigabit
The i.MX 7 series currently consists of two SoCs: i.MX 7Solo and
7Dual. The i.MX 7Solo implements a subset of features available on
i.MX 7Dual, hence create imx7s.dtsi as the base device tree. The
i.MX 7Dual's additional features over i.MX 7Solo are:
- Second Cortex-A7 core
- Second Gigabit
Add support for the Computer on Module Colibri iMX7S/iMX7D along
with the development/evaluation carrier board device trees. Follow
the usual hierarchic include model, maintaining shared configuration
in imx7-colibri.dtsi and imx7-colibri-eval-v3.dtsi respectively.
Signed-off-by: Stefan Agner
Add support for the Computer on Module Colibri iMX7S/iMX7D along
with the development/evaluation carrier board device trees. Follow
the usual hierarchic include model, maintaining shared configuration
in imx7-colibri.dtsi and imx7-colibri-eval-v3.dtsi respectively.
Signed-off-by: Stefan Agner
The base device tree uses KEY_POWER in the snvs-powerkey node,
hence include the input.h header file in the base device tree.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx7d-cl-som-imx7.dts | 1 -
arch/arm/boot/dts/imx7d-nitrogen7.dts | 1 -
The two SoC's i.MX 7Solo and i.MX 7Dual are very similar, but there
are some differences worth dividing the current i.MX 7Dual base device
tree. This patchset adds new base device tree imx7s.dtsi which is meant
to be used for i.MX 7Solo boards. Note that the SoC _family_ is called
imx7d/IMX7D
The base device tree uses KEY_POWER in the snvs-powerkey node,
hence include the input.h header file in the base device tree.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx7d-cl-som-imx7.dts | 1 -
arch/arm/boot/dts/imx7d-nitrogen7.dts | 1 -
arch/arm/boot/dts/imx7d-sdb.dts | 1
The two SoC's i.MX 7Solo and i.MX 7Dual are very similar, but there
are some differences worth dividing the current i.MX 7Dual base device
tree. This patchset adds new base device tree imx7s.dtsi which is meant
to be used for i.MX 7Solo boards. Note that the SoC _family_ is called
imx7d/IMX7D
On 2016/6/7 22:01, Ganapatrao Kulkarni wrote:
> On Tue, Jun 7, 2016 at 6:27 PM, Leizhen (ThunderTown)
> wrote:
>>
>>
>> On 2016/6/7 16:31, Ganapatrao Kulkarni wrote:
>>> On Tue, Jun 7, 2016 at 1:38 PM, Zhen Lei wrote:
Some numa nodes
On Jun 7, 2016, at 8:03 PM, Jeff Layton wrote:
>>> That said, this code is quite subtle. I'd need to look over it in more
>>> detail before I offer up any fixes. I'd also appreciate it if anyone
>>> else wants to sanity check my analysis there.
>>>
> Yeah, I think you're right. It's fine since
On 2016/6/7 22:01, Ganapatrao Kulkarni wrote:
> On Tue, Jun 7, 2016 at 6:27 PM, Leizhen (ThunderTown)
> wrote:
>>
>>
>> On 2016/6/7 16:31, Ganapatrao Kulkarni wrote:
>>> On Tue, Jun 7, 2016 at 1:38 PM, Zhen Lei wrote:
Some numa nodes may have no memory. For example:
1. cpu0 on node0
On Jun 7, 2016, at 8:03 PM, Jeff Layton wrote:
>>> That said, this code is quite subtle. I'd need to look over it in more
>>> detail before I offer up any fixes. I'd also appreciate it if anyone
>>> else wants to sanity check my analysis there.
>>>
> Yeah, I think you're right. It's fine since
> -Original Message-
> From: Neil Horman [mailto:nhor...@redhat.com]
> Sent: Tuesday, June 07, 2016 9:23 AM
> To: Kershner, David A
> Cc: cor...@lwn.net; t...@linutronix.de; mi...@redhat.com;
> h...@zytor.com; gre...@linuxfoundation.org; Arfvidson, Erik
>
> -Original Message-
> From: Neil Horman [mailto:nhor...@redhat.com]
> Sent: Tuesday, June 07, 2016 9:23 AM
> To: Kershner, David A
> Cc: cor...@lwn.net; t...@linutronix.de; mi...@redhat.com;
> h...@zytor.com; gre...@linuxfoundation.org; Arfvidson, Erik
> ; Sell, Timothy C ;
>
Hi,
On 2016/6/8 9:33, Weidong Wang wrote:
Test 32 progress and 64 progress on the 64bit system with
this progress:
int main(int argc, char **argv)
{
int fd = 0;
int i, ret = 0;
char buf[512];
unsigned long count = -1;
fd = open("/tmp", O_RDONLY);
Hi,
On 2016/6/8 9:33, Weidong Wang wrote:
Test 32 progress and 64 progress on the 64bit system with
this progress:
int main(int argc, char **argv)
{
int fd = 0;
int i, ret = 0;
char buf[512];
unsigned long count = -1;
fd = open("/tmp", O_RDONLY);
On Mon, May 30, 2016 at 05:14:22PM +0200, Tomasz Nowicki wrote:
> This patch implements pci_acpi_scan_root call so that ARM64 can start
> using ACPI to setup and enumerate PCI buses.
>
> The implementation of pci_acpi_scan_root() looks up config space regions
> through MCFG interface. Then ECAM
On Tue, Jun 07, 2016 at 10:09:14AM +0200, Vincent Guittot wrote:
> >> A much more simple solution would be
> >> to prevent last_update_time to be initialized with this special value.
> >> We can initialize the last_update_time of a sched_entity to 1 as an
> >> example which is easier than these
On Tue, Jun 07, 2016 at 10:09:14AM +0200, Vincent Guittot wrote:
> >> A much more simple solution would be
> >> to prevent last_update_time to be initialized with this special value.
> >> We can initialize the last_update_time of a sched_entity to 1 as an
> >> example which is easier than these
On Mon, May 30, 2016 at 05:14:22PM +0200, Tomasz Nowicki wrote:
> This patch implements pci_acpi_scan_root call so that ARM64 can start
> using ACPI to setup and enumerate PCI buses.
>
> The implementation of pci_acpi_scan_root() looks up config space regions
> through MCFG interface. Then ECAM
Fixes for crap of assorted ages: EOPENSTALE one is 4.2+, autofs
one is 4.6, d_walk - 3.2+, atomic_open() and coredump ones are this window
regressions.
The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
are available
Fixes for crap of assorted ages: EOPENSTALE one is 4.2+, autofs
one is 4.6, d_walk - 3.2+, atomic_open() and coredump ones are this window
regressions.
The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
are available
Hi Mark, thank for comment.
On Tue, 2016-06-07 at 16:54 +0100, Mark Brown wrote:
> On Fri, Jun 03, 2016 at 12:56:17PM +0800, Garlic Tseng wrote:
>
> > + /*enable agent*/
>
> Lots of comments with missing spaces in them, there's quite a few
> examples of that in here.
I'll check all the code
Hi Mark, thank for comment.
On Tue, 2016-06-07 at 16:54 +0100, Mark Brown wrote:
> On Fri, Jun 03, 2016 at 12:56:17PM +0800, Garlic Tseng wrote:
>
> > + /*enable agent*/
>
> Lots of comments with missing spaces in them, there's quite a few
> examples of that in here.
I'll check all the code
Ping. Any comment is appreciate.
Thanks
Minfei
On 05/17/16 at 03:58P, Minfei Huang wrote:
> It's more elegant to use MACRO UINT_MAX to represent the max value of
> type unsigned int. So replace the actual value by using this MACRO.
>
> Signed-off-by: Minfei Huang
> ---
> v1:
Ping. Any comment is appreciate.
Thanks
Minfei
On 05/17/16 at 03:58P, Minfei Huang wrote:
> It's more elegant to use MACRO UINT_MAX to represent the max value of
> type unsigned int. So replace the actual value by using this MACRO.
>
> Signed-off-by: Minfei Huang
> ---
> v1:
> - fix typo
> ---
Hi Herbert,
On 7 June 2016 at 22:16, Herbert Xu wrote:
> On Tue, Jun 07, 2016 at 08:17:05PM +0800, Baolin Wang wrote:
>> Now some cipher hardware engines prefer to handle bulk block rather than one
>> sector (512 bytes) created by dm-crypt, cause these cipher engines
Hi Herbert,
On 7 June 2016 at 22:16, Herbert Xu wrote:
> On Tue, Jun 07, 2016 at 08:17:05PM +0800, Baolin Wang wrote:
>> Now some cipher hardware engines prefer to handle bulk block rather than one
>> sector (512 bytes) created by dm-crypt, cause these cipher engines can handle
>> the
On 06/07/2016 06:40 PM, Ji-Ze Hong (Peter Hong) wrote:
Hi Guenter,
Guenter Roeck 於 2016/6/7 下午 10:06 寫道:
On 06/05/2016 11:58 PM, Ji-Ze Hong (Peter Hong) wrote:
+#define SIO_REG_PORT_SEL0x27/* F81866 Multi-Function Register */
+#define SIO_REG_GPIO10x2c/*
+
On 06/07/2016 06:40 PM, Ji-Ze Hong (Peter Hong) wrote:
Hi Guenter,
Guenter Roeck 於 2016/6/7 下午 10:06 寫道:
On 06/05/2016 11:58 PM, Ji-Ze Hong (Peter Hong) wrote:
+#define SIO_REG_PORT_SEL0x27/* F81866 Multi-Function Register */
+#define SIO_REG_GPIO10x2c/*
+
On Mon, May 30, 2016 at 05:14:20PM +0200, Tomasz Nowicki wrote:
> In order to handle PCI config space regions properly in ACPI, new MCFG
> interface is defined which does sanity checks on MCFG table and keeps its
> root pointer. The user is able to lookup MCFG regions based on
> host bridge root
On Mon, May 30, 2016 at 05:14:20PM +0200, Tomasz Nowicki wrote:
> In order to handle PCI config space regions properly in ACPI, new MCFG
> interface is defined which does sanity checks on MCFG table and keeps its
> root pointer. The user is able to lookup MCFG regions based on
> host bridge root
Hi, Minchan:
2016-06-08 8:16 GMT+08:00 Minchan Kim :
> Hello Ganesh,
>
> On Tue, Jun 07, 2016 at 04:56:44PM +0800, Ganesh Mahendran wrote:
>> Currently zsmalloc is widely used in android device.
>> Sometimes, we want to see how frequently zs_compact is
>> triggered or how may
Hi, Minchan:
2016-06-08 8:16 GMT+08:00 Minchan Kim :
> Hello Ganesh,
>
> On Tue, Jun 07, 2016 at 04:56:44PM +0800, Ganesh Mahendran wrote:
>> Currently zsmalloc is widely used in android device.
>> Sometimes, we want to see how frequently zs_compact is
>> triggered or how may pages freed by
I'm announcing the release of the 3.14.72 kernel.
All users of the 3.14 kernel series must upgrade.
The updated 3.14.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.14.y
and can be browsed at the normal kernel.org git web
diff --git a/Makefile b/Makefile
index 98282e65bb46..6155aaf6342a 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 14
-SUBLEVEL = 71
+SUBLEVEL = 72
EXTRAVERSION =
NAME = Remembering Coco
diff --git a/arch/mips/ath79/early_printk.c b/arch/mips/ath79/early_printk.c
I'm announcing the release of the 3.14.72 kernel.
All users of the 3.14 kernel series must upgrade.
The updated 3.14.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.14.y
and can be browsed at the normal kernel.org git web
diff --git a/Makefile b/Makefile
index 98282e65bb46..6155aaf6342a 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 14
-SUBLEVEL = 71
+SUBLEVEL = 72
EXTRAVERSION =
NAME = Remembering Coco
diff --git a/arch/mips/ath79/early_printk.c b/arch/mips/ath79/early_printk.c
On Tue, 2016-06-07 at 17:15 +0100, Mark Brown wrote:
> On Fri, Jun 03, 2016 at 12:56:20PM +0800, Garlic Tseng wrote:
>
> > +void mt2701_init_clock(struct mtk_base_afe *afe)
> > +{
> > + struct mt2701_afe_private *afe_priv = afe->platform_priv;
> > + int i = 0;
> > +
> > + for (i = 0; i <
I'm announcing the release of the 4.4.13 kernel.
All users of the 4.4 kernel series must upgrade.
The updated 4.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.4.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Documentation/devicetree/bindings/clock/imx35-clock.txt
b/Documentation/devicetree/bindings/clock/imx35-clock.txt
index a70356452a82..f49783213c56 100644
--- a/Documentation/devicetree/bindings/clock/imx35-clock.txt
+++ b/Documentation/devicetree/bindings/clock/imx35-clock.txt
@@
On Tue, 2016-06-07 at 17:15 +0100, Mark Brown wrote:
> On Fri, Jun 03, 2016 at 12:56:20PM +0800, Garlic Tseng wrote:
>
> > +void mt2701_init_clock(struct mtk_base_afe *afe)
> > +{
> > + struct mt2701_afe_private *afe_priv = afe->platform_priv;
> > + int i = 0;
> > +
> > + for (i = 0; i <
I'm announcing the release of the 4.4.13 kernel.
All users of the 4.4 kernel series must upgrade.
The updated 4.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.4.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Documentation/devicetree/bindings/clock/imx35-clock.txt
b/Documentation/devicetree/bindings/clock/imx35-clock.txt
index a70356452a82..f49783213c56 100644
--- a/Documentation/devicetree/bindings/clock/imx35-clock.txt
+++ b/Documentation/devicetree/bindings/clock/imx35-clock.txt
@@
diff --git a/Documentation/devicetree/bindings/clock/imx35-clock.txt
b/Documentation/devicetree/bindings/clock/imx35-clock.txt
index a70356452a82..f49783213c56 100644
--- a/Documentation/devicetree/bindings/clock/imx35-clock.txt
+++ b/Documentation/devicetree/bindings/clock/imx35-clock.txt
@@
diff --git a/Documentation/devicetree/bindings/clock/imx35-clock.txt
b/Documentation/devicetree/bindings/clock/imx35-clock.txt
index a70356452a82..f49783213c56 100644
--- a/Documentation/devicetree/bindings/clock/imx35-clock.txt
+++ b/Documentation/devicetree/bindings/clock/imx35-clock.txt
@@
NOTE: This is the LAST 4.5.y stable kernel release. It is now
end-of-life, please move to the 4.6.y kernel tree now as this tree will
not be getting any more updates.
I'm announcing the release of the 4.5.7 kernel.
All users of the 4.5 kernel series must
NOTE: This is the LAST 4.5.y stable kernel release. It is now
end-of-life, please move to the 4.6.y kernel tree now as this tree will
not be getting any more updates.
I'm announcing the release of the 4.5.7 kernel.
All users of the 4.5 kernel series must
I'm announcing the release of the 4.6.2 kernel.
All users of the 4.6 kernel series must upgrade.
The updated 4.6.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.6.y
and can be browsed at the normal kernel.org git web browser:
I'm announcing the release of the 4.6.2 kernel.
All users of the 4.6 kernel series must upgrade.
The updated 4.6.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.6.y
and can be browsed at the normal kernel.org git web browser:
Hi Guenter,
Guenter Roeck 於 2016/6/7 下午 10:06 寫道:
On 06/05/2016 11:58 PM, Ji-Ze Hong (Peter Hong) wrote:
+#define SIO_REG_PORT_SEL0x27/* F81866 Multi-Function Register */
+#define SIO_REG_GPIO10x2c/*
+ * GPIO1 Control Register when 27h
+
Hi Guenter,
Guenter Roeck 於 2016/6/7 下午 10:06 寫道:
On 06/05/2016 11:58 PM, Ji-Ze Hong (Peter Hong) wrote:
+#define SIO_REG_PORT_SEL0x27/* F81866 Multi-Function Register */
+#define SIO_REG_GPIO10x2c/*
+ * GPIO1 Control Register when 27h
+
Hi Rob
On 06/07/2016 09:46 PM, Rob Herring wrote:
On Mon, Jun 6, 2016 at 7:33 PM, Chris Zhong wrote:
Hi Rob
On 06/06/2016 10:27 PM, Rob Herring wrote:
On Fri, Jun 03, 2016 at 11:15:08PM +0800, Chris Zhong wrote:
This patch adds a binding that describes the Rockchip
Hi Rob
On 06/07/2016 09:46 PM, Rob Herring wrote:
On Mon, Jun 6, 2016 at 7:33 PM, Chris Zhong wrote:
Hi Rob
On 06/06/2016 10:27 PM, Rob Herring wrote:
On Fri, Jun 03, 2016 at 11:15:08PM +0800, Chris Zhong wrote:
This patch adds a binding that describes the Rockchip USB Type-C PHY
for
On Wed, Jun 8, 2016 at 4:41 AM, Maxime Ripard
wrote:
> Introduce a new binding with its documentation for the brand new clock
> sub-framework.
>
> Signed-off-by: Maxime Ripard
> ---
>
On Wed, Jun 8, 2016 at 4:41 AM, Maxime Ripard
wrote:
> Introduce a new binding with its documentation for the brand new clock
> sub-framework.
>
> Signed-off-by: Maxime Ripard
> ---
> Documentation/devicetree/bindings/clock/sunxi-ccu.txt | 17 +
> 1 file changed, 17
On 2016/5/24 8:04, Yury Norov wrote:
Here new aarch32 ptrace syscall handler is introsuced to avoid run-time
detection of the task type.
Signed-off-by: Yury Norov
---
arch/arm64/include/asm/unistd32.h | 2 +-
arch/arm64/kernel/ptrace.c| 50
On 2016/5/24 8:04, Yury Norov wrote:
Here new aarch32 ptrace syscall handler is introsuced to avoid run-time
detection of the task type.
Signed-off-by: Yury Norov
---
arch/arm64/include/asm/unistd32.h | 2 +-
arch/arm64/kernel/ptrace.c| 50 ++-
Test 32 progress and 64 progress on the 64bit system with
this progress:
int main(int argc, char **argv)
{
int fd = 0;
int i, ret = 0;
char buf[512];
unsigned long count = -1;
fd = open("/tmp", O_RDONLY);
if (fd < -1) {
printf("Pls
Test 32 progress and 64 progress on the 64bit system with
this progress:
int main(int argc, char **argv)
{
int fd = 0;
int i, ret = 0;
char buf[512];
unsigned long count = -1;
fd = open("/tmp", O_RDONLY);
if (fd < -1) {
printf("Pls
Hi Javier,
On 06/08/2016 01:06 AM, Javier Martinez Canillas wrote:
Hello Yakir,
On 03/17/2016 05:47 PM, Heiko Stübner wrote:
Split the dp core driver from exynos directory to bridge directory,
and rename the core driver to analogix_dp_*, rename the platform
code to exynos_dp.
Beside the new
Hi Javier,
On 06/08/2016 01:06 AM, Javier Martinez Canillas wrote:
Hello Yakir,
On 03/17/2016 05:47 PM, Heiko Stübner wrote:
Split the dp core driver from exynos directory to bridge directory,
and rename the core driver to analogix_dp_*, rename the platform
code to exynos_dp.
Beside the new
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
net/sched/act_police.c
between commit:
53eb440f4ada ("net sched actions: introduce timestamp for firsttime use")
from the net tree and commit:
a03e6fe56971 ("act_police: fix a crash during removal")
from the
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
net/sched/act_police.c
between commit:
53eb440f4ada ("net sched actions: introduce timestamp for firsttime use")
from the net tree and commit:
a03e6fe56971 ("act_police: fix a crash during removal")
from the
On Thu, 2 Jun 2016 23:26:16 -0400
David Long wrote:
> @@ -367,6 +402,7 @@ bool aarch32_insn_is_wide(u32 insn);
> #define A32_RT_OFFSET12
> #define A32_RT2_OFFSET0
>
> +u32 aarch64_extract_system_register(u32 insn);
This exported symbol is incorrect (see
On Thu, 2 Jun 2016 23:26:16 -0400
David Long wrote:
> @@ -367,6 +402,7 @@ bool aarch32_insn_is_wide(u32 insn);
> #define A32_RT_OFFSET12
> #define A32_RT2_OFFSET0
>
> +u32 aarch64_extract_system_register(u32 insn);
This exported symbol is incorrect (see below)
> u32
On Tue, Jun 07, 2016 at 06:40:54AM -0700, Guenter Roeck wrote:
> On 06/05/2016 02:42 PM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.6.2 release.
> > There are 121 patches in this series, all will be posted as a response
> > to this one. If anyone has any
On Tue, Jun 07, 2016 at 06:40:54AM -0700, Guenter Roeck wrote:
> On 06/05/2016 02:42 PM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.6.2 release.
> > There are 121 patches in this series, all will be posted as a response
> > to this one. If anyone has any
On Thu, 2 Jun 2016 23:26:19 -0400
David Long wrote:
> From: Sandeepa Prabhu
>
> Add support for basic kernel probes(kprobes) and jump probes
> (jprobes) for ARM64.
>
> Kprobes utilizes software breakpoint and single step debug
> exceptions
On Thu, 2 Jun 2016 23:26:19 -0400
David Long wrote:
> From: Sandeepa Prabhu
>
> Add support for basic kernel probes(kprobes) and jump probes
> (jprobes) for ARM64.
>
> Kprobes utilizes software breakpoint and single step debug
> exceptions supported on ARM v8.
>
> A software breakpoint is
On Mon, Jun 06, 2016 at 09:07:10PM -0700, Guenter Roeck wrote:
> mips failures (affecting 4.4, 4.5, 4,6):
>
> arch/mips/mm/cache.c: In function '__update_cache':
> arch/mips/mm/cache.c:134:4: error: implicit declaration of function
> 'kmap_atomic' [-Werror=implicit-function-declaration]
>
On Mon, Jun 06, 2016 at 09:07:10PM -0700, Guenter Roeck wrote:
> mips failures (affecting 4.4, 4.5, 4,6):
>
> arch/mips/mm/cache.c: In function '__update_cache':
> arch/mips/mm/cache.c:134:4: error: implicit declaration of function
> 'kmap_atomic' [-Werror=implicit-function-declaration]
>
Use the PMIC's repower capability for reboots. Register a restart
handler with use a default priority of 128.
Reviewed-by: Marcel Ziswiler
Signed-off-by: Stefan Agner
---
drivers/mfd/rn5t618.c | 40 ++--
1 file
Use the PMIC's repower capability for reboots. Register a restart
handler with use a default priority of 128.
Reviewed-by: Marcel Ziswiler
Signed-off-by: Stefan Agner
---
drivers/mfd/rn5t618.c | 40 ++--
1 file changed, 34 insertions(+), 6 deletions(-)
diff
Only register power off if the PMIC is defined as system power
controller (see Documentation/devicetree/bindings/power/
power-controller.txt).
Reviewed-by: Marcel Ziswiler
Signed-off-by: Stefan Agner
---
drivers/mfd/rn5t618.c | 10 +++---
1
Only register power off if the PMIC is defined as system power
controller (see Documentation/devicetree/bindings/power/
power-controller.txt).
Reviewed-by: Marcel Ziswiler
Signed-off-by: Stefan Agner
---
drivers/mfd/rn5t618.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
The PMIC driver used to register itself as poweroff controller by
default, hence assuming that this device is using the PMIC as
system power controller.
Reviewed-by: Marcel Ziswiler
Signed-off-by: Stefan Agner
---
The PMIC driver used to register itself as poweroff controller by
default, hence assuming that this device is using the PMIC as
system power controller.
Reviewed-by: Marcel Ziswiler
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/meson8-minix-neo-x8.dts | 1 +
1 file changed, 1 insertion(+)
Extend the driver to support Ricoh RN5T567. Support the additional
DCDC and slightly different voltage range of LDORTC1.
Reviewed-by: Marcel Ziswiler
Acked-by: Mark Brown
Signed-off-by: Stefan Agner
---
Extend the driver to support Ricoh RN5T567. Support the additional
DCDC and slightly different voltage range of LDORTC1.
Reviewed-by: Marcel Ziswiler
Acked-by: Mark Brown
Signed-off-by: Stefan Agner
---
drivers/regulator/Kconfig | 5 +++--
drivers/regulator/rn5t618-regulator.c |
This patchset adds RN5T567 PMIC support which is used on the
Toradex Colibri iMX7S/iMX7D modules. The existing RN5T618 is from
the same family, hence this patchset uses the same driver and adds
variant support.
The Colibris currently do not use the PMIC's power off capabilities,
hence this
The Ricoh RN5T567 is from the same family as the Ricoh RN5T618 is,
the differences are:
+ DCDC4
+ Slightly different output voltage/currents
+ 32kHz Output
- ADC/Charger capabilities
Reviewed-by: Marcel Ziswiler
Signed-off-by: Stefan Agner
---
This patchset adds RN5T567 PMIC support which is used on the
Toradex Colibri iMX7S/iMX7D modules. The existing RN5T618 is from
the same family, hence this patchset uses the same driver and adds
variant support.
The Colibris currently do not use the PMIC's power off capabilities,
hence this
The Ricoh RN5T567 is from the same family as the Ricoh RN5T618 is,
the differences are:
+ DCDC4
+ Slightly different output voltage/currents
+ 32kHz Output
- ADC/Charger capabilities
Reviewed-by: Marcel Ziswiler
Signed-off-by: Stefan Agner
---
Documentation/devicetree/bindings/mfd/rn5t618.txt
On 06/07/2016 02:57 PM, Kees Cook wrote:
This adds a function that lives in the .rodata section. The section
flags are corrected using objcopy since there is no way with gcc to
declare section flags in an architecture-agnostic way.
Permit me to be the bearer of bad architecture news once
On 06/07/2016 02:57 PM, Kees Cook wrote:
This adds a function that lives in the .rodata section. The section
flags are corrected using objcopy since there is no way with gcc to
declare section flags in an architecture-agnostic way.
Permit me to be the bearer of bad architecture news once
On Mon, Jun 06, 2016 at 09:07:10PM -0700, Guenter Roeck wrote:
>
> arm failures:
> drivers/gpio/gpio-davinci.c: In function 'davinci_gpio_probe':
> drivers/gpio/gpio-davinci.c:257:16: error: 'struct gpio_chip' has no member
> named 'parent'
>
> Culprit is 'gpio: davinci: fix missed parent
This patch adds USART3 pin configuration on PB10/PA11 pins
for STM32F469I-DISCO board.
Signed-off-by: Bruno Herrera
---
arch/arm/boot/dts/stm32f429.dtsi | 13 +
arch/arm/boot/dts/stm32f469-disco.dts | 2 ++
2 files changed, 15 insertions(+)
diff --git
On Mon, Jun 06, 2016 at 09:07:10PM -0700, Guenter Roeck wrote:
>
> arm failures:
> drivers/gpio/gpio-davinci.c: In function 'davinci_gpio_probe':
> drivers/gpio/gpio-davinci.c:257:16: error: 'struct gpio_chip' has no member
> named 'parent'
>
> Culprit is 'gpio: davinci: fix missed parent
This patch adds USART3 pin configuration on PB10/PA11 pins
for STM32F469I-DISCO board.
Signed-off-by: Bruno Herrera
---
arch/arm/boot/dts/stm32f429.dtsi | 13 +
arch/arm/boot/dts/stm32f469-disco.dts | 2 ++
2 files changed, 15 insertions(+)
diff --git
On Mon, Jun 06, 2016 at 04:33:14PM -0700, Greg Kroah-Hartman wrote:
> On Mon, Jun 06, 2016 at 06:43:47PM -0400, Javier Martinez Canillas wrote:
> > Hello,
> >
> > On 06/06/2016 06:32 PM, Tyler Baker wrote:
> > > On 6 June 2016 at 06:55, Kevin Hilman wrote:
> > >>
On Mon, Jun 06, 2016 at 04:33:14PM -0700, Greg Kroah-Hartman wrote:
> On Mon, Jun 06, 2016 at 06:43:47PM -0400, Javier Martinez Canillas wrote:
> > Hello,
> >
> > On 06/06/2016 06:32 PM, Tyler Baker wrote:
> > > On 6 June 2016 at 06:55, Kevin Hilman wrote:
> > >> kernelci.org bot writes:
> > >>
On 06/07/2016 10:49 AM, Willy Tarreau wrote:
Hi Guenter,
On Tue, Jun 07, 2016 at 08:54:53AM +0200, Willy Tarreau wrote:
Jiri provides a branch for 3.12, exactly as you suggested. In his case it is
named stable-3.12-queue. Sasha does the same, with linux-3.18.y-queue and
linux-4.1.y-queue. Both
On 06/07/2016 10:49 AM, Willy Tarreau wrote:
Hi Guenter,
On Tue, Jun 07, 2016 at 08:54:53AM +0200, Willy Tarreau wrote:
Jiri provides a branch for 3.12, exactly as you suggested. In his case it is
named stable-3.12-queue. Sasha does the same, with linux-3.18.y-queue and
linux-4.1.y-queue. Both
On Tue, Jun 7, 2016 at 6:47 PM, Joe Perches wrote:
> On Tue, 2016-06-07 at 18:41 -0600, Reinoud Koornstra wrote:
>> Hello Everybody,
>>
>> A small patch that doesn't really do anything other than getting rid
>> of a warning in gcc 6.1.0.
>>
>>
On Tue, Jun 7, 2016 at 6:47 PM, Joe Perches wrote:
> On Tue, 2016-06-07 at 18:41 -0600, Reinoud Koornstra wrote:
>> Hello Everybody,
>>
>> A small patch that doesn't really do anything other than getting rid
>> of a warning in gcc 6.1.0.
>>
>> drivers/gpu/drm/i915/i915_debugfs.c: In function
101 - 200 of 2408 matches
Mail list logo