From: Jagan Teki
Add support for fec1 node on Engicam Is.IoT variant boards.
Cc: Shawn Guo
Cc: Matteo Lisi
Cc: Michael Trimarchi
Signed-off-by: Jagan Teki
---
From: Jagan Teki
Add support for fec1 node on Engicam Is.IoT variant boards.
Cc: Shawn Guo
Cc: Matteo Lisi
Cc: Michael Trimarchi
Signed-off-by: Jagan Teki
---
Changes for v3:
- none
Changes for v2:
- Newly added patch
arch/arm/boot/dts/imx6ul-isiot.dtsi | 33
From: Jagan Teki
Add support for can1 and can2 nodes on Engicam i.CoreM6 RQS
QDL module boards.
Cc: Shawn Guo
Cc: Matteo Lisi
Cc: Michael Trimarchi
Signed-off-by: Jagan Teki
From: Jagan Teki
Add support for can1 and can2 nodes on Engicam i.CoreM6 RQS
QDL module boards.
Cc: Shawn Guo
Cc: Matteo Lisi
Cc: Michael Trimarchi
Signed-off-by: Jagan Teki
---
Changes for v3:
- none
Changes for v2:
- s/flexcan/can
- s/pinctrl_flexcan/pinctrl_can
From: Jagan Teki
Add support for Sound card and related codec(via i2c1) nodes
on below Engicam module boards.
- i.CoreM6 DualLite/Solo Starter kit
- i.CoreM6 Quad/Dual Starter kit
- i.CoreM6 Quad/Dual OpenFrame Cap touch 10.1
- i.CoreM6 Quad/Dual OpenFrame Cap touch
From: Jagan Teki
Add support for Sound card and related codec(via i2c1) nodes
on below Engicam module boards.
- i.CoreM6 DualLite/Solo Starter kit
- i.CoreM6 Quad/Dual Starter kit
- i.CoreM6 Quad/Dual OpenFrame Cap touch 10.1
- i.CoreM6 Quad/Dual OpenFrame Cap touch 12.3
Cc: Shawn Guo
Cc:
From: Jagan Teki
Add support for Sound card and related codec(via i2c1) nodes
on Engicam GEAM6UL variant module boards.
Cc: Shawn Guo
Cc: Matteo Lisi
Cc: Michael Trimarchi
Signed-off-by:
From: Jagan Teki
Add support for Sound card and related codec(via i2c1) nodes
on Engicam GEAM6UL variant module boards.
Cc: Shawn Guo
Cc: Matteo Lisi
Cc: Michael Trimarchi
Signed-off-by: Jagan Teki
---
Changes for v3:
- Replace fsl,imx-audio-sgtl5000 and use simple-audio-card
Changes for
From: Jagan Teki
- Moved sound card node to imx6qdl-icore-rqs.dtsi
- Added codec node in imx6dl-icore-rqs
- Replace codec: sgtl5000@0a => sgtl5000: codec@a
on imx6q-icore-rqs.dts to [label:] node-name[@unit-address]
according to devicetree specification from
From: Jagan Teki
Add LVDS display support for OpenFrame Capacitive touch 7 inc
display which is supported by Engicam i.CoreM6 DualLite/Solo Starter Kit.
Cc: Shawn Guo
Cc: Matteo Lisi
Cc: Michael Trimarchi
From: Jagan Teki
- Moved sound card node to imx6qdl-icore-rqs.dtsi
- Added codec node in imx6dl-icore-rqs
- Replace codec: sgtl5000@0a => sgtl5000: codec@a
on imx6q-icore-rqs.dts to [label:] node-name[@unit-address]
according to devicetree specification from ePAPER v1.1
Cc: Shawn Guo
Cc:
From: Jagan Teki
Add LVDS display support for OpenFrame Capacitive touch 7 inc
display which is supported by Engicam i.CoreM6 DualLite/Solo Starter Kit.
Cc: Shawn Guo
Cc: Matteo Lisi
Cc: Michael Trimarchi
Signed-off-by: Jagan Teki
---
Changes for v3,v2:
- none
From: Jagan Teki
Add support for Sound card and related codec(via i2c1) nodes
on Engicam Is.IoT MX6UL variant module boards.
Cc: Shawn Guo
Cc: Matteo Lisi
Cc: Michael Trimarchi
From: Jagan Teki
Add support for Sound card and related codec(via i2c1) nodes
on Engicam Is.IoT MX6UL variant module boards.
Cc: Shawn Guo
Cc: Matteo Lisi
Cc: Michael Trimarchi
Signed-off-by: Jagan Teki
---
Changes for v3:
- Replace fsl,imx-audio-sgtl5000 and use simple-audio-card
Changes
From: Jagan Teki
This patchset, add support for LVDS, touchscreen, sound card and related codec
and can nodes all Engicam SOM's which are supporting mainline as of now.
Jagan Teki (9):
ARM: dts: imx6ul-isiot: Add Sound card with codec node
ARM: dts: imx6ul-geam:
From: Jagan Teki
This patchset, add support for LVDS, touchscreen, sound card and related codec
and can nodes all Engicam SOM's which are supporting mainline as of now.
Jagan Teki (9):
ARM: dts: imx6ul-isiot: Add Sound card with codec node
ARM: dts: imx6ul-geam: Add Sound card with codec
On Thu, Apr 06, 2017 at 06:42:16PM +0300, Kirill A. Shutemov wrote:
> Config is attached.
Thanks!
> Looks like fake numa is the key.
...
> NUMA: Warning: node ids are out of bound, from=0 to=1 distance=20
>
On Thu, Apr 06, 2017 at 06:42:16PM +0300, Kirill A. Shutemov wrote:
> Config is attached.
Thanks!
> Looks like fake numa is the key.
...
> NUMA: Warning: node ids are out of bound, from=0 to=1 distance=20
>
On Thu, Apr 06, 2017 at 12:42:41PM -0400, Steven Rostedt wrote:
> From: "Paul E. McKenney"
>
> The tracing subsystem started using rcu_irq_entry() and rcu_irq_exit()
> (with my blessing) to allow the current _rcuidle alternative tracepoint
> name to be dispensed with
On Thu, Apr 06, 2017 at 12:42:41PM -0400, Steven Rostedt wrote:
> From: "Paul E. McKenney"
>
> The tracing subsystem started using rcu_irq_entry() and rcu_irq_exit()
> (with my blessing) to allow the current _rcuidle alternative tracepoint
> name to be dispensed with while still maintaining good
On 2017-04-05 9:45 PM, David Miller wrote:
From: Jarod Wilson
Date: Tue, 4 Apr 2017 17:32:42 -0400
...
Applied, but:
+static inline void bond_hw_addr_copy(u8 *dst, const u8 *src, unsigned int len)
+{
+ if (len == ETH_ALEN) {
+ ether_addr_copy(dst,
On 2017-04-05 9:45 PM, David Miller wrote:
From: Jarod Wilson
Date: Tue, 4 Apr 2017 17:32:42 -0400
...
Applied, but:
+static inline void bond_hw_addr_copy(u8 *dst, const u8 *src, unsigned int len)
+{
+ if (len == ETH_ALEN) {
+ ether_addr_copy(dst, src);
+
On Thu, Apr 06, 2017 at 11:54:04AM -0600, Shuah Khan wrote:
> On 04/06/2017 02:37 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.10.9 release.
> > There are 81 patches in this series, all will be posted as a response
> > to this one. If anyone has any
On Thu, Apr 06, 2017 at 11:54:04AM -0600, Shuah Khan wrote:
> On 04/06/2017 02:37 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.10.9 release.
> > There are 81 patches in this series, all will be posted as a response
> > to this one. If anyone has any
On 04/06/2017 02:37 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.10.9 release.
> There are 81 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 04/06/2017 02:37 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.10.9 release.
> There are 81 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On Fri, Apr 07, 2017 at 01:39:09AM +0800, Fu Wei wrote:
> On 7 April 2017 at 01:24, Mark Rutland wrote:
> > On Fri, Apr 07, 2017 at 12:47:47AM +0800, Fu Wei wrote:
> >> On 6 April 2017 at 02:38, Mark Rutland wrote:
> >> > On Sat, Apr 01, 2017 at
On Fri, Apr 07, 2017 at 01:39:09AM +0800, Fu Wei wrote:
> On 7 April 2017 at 01:24, Mark Rutland wrote:
> > On Fri, Apr 07, 2017 at 12:47:47AM +0800, Fu Wei wrote:
> >> On 6 April 2017 at 02:38, Mark Rutland wrote:
> >> > On Sat, Apr 01, 2017 at 01:51:03AM +0800, fu@linaro.org wrote:
> >
On 04/06/2017 02:38 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.60 release.
> There are 26 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 04/06/2017 02:38 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.60 release.
> There are 26 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On Thu, Apr 06, 2017 at 07:12:42PM +0200, Michal Hocko wrote:
> > ---8<---
> > mm, vmscan: prevent kswapd sleeping prematurely due to mismatched
> > classzone_idx -fix
> >
> > The patch "mm, vmscan: prevent kswapd sleeping prematurely due to mismatched
> > classzone_idx" has different initial
On Thu, Apr 06, 2017 at 07:12:42PM +0200, Michal Hocko wrote:
> > ---8<---
> > mm, vmscan: prevent kswapd sleeping prematurely due to mismatched
> > classzone_idx -fix
> >
> > The patch "mm, vmscan: prevent kswapd sleeping prematurely due to mismatched
> > classzone_idx" has different initial
On 04/06/2017 02:37 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.21 release.
> There are 72 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 04/06/2017 02:37 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.21 release.
> There are 72 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
The patch "mm, vmscan: prevent kswapd sleeping prematurely due to mismatched
classzone_idx" has different initial starting conditions when kswapd
is asleep. kswapd initialises it properly when it starts but the patch
initialises kswapd_classzone_idx early and trips on a warning in
On Thu, 2017-04-06 at 10:38 +0200, Greg Kroah-Hartman wrote:
> 4.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Alexandre Belloni
>
> commit 0b0408745e7ff24757cbfd571d69026c0ddb803c upstream.
>
>
The patch "mm, vmscan: prevent kswapd sleeping prematurely due to mismatched
classzone_idx" has different initial starting conditions when kswapd
is asleep. kswapd initialises it properly when it starts but the patch
initialises kswapd_classzone_idx early and trips on a warning in
On Thu, 2017-04-06 at 10:38 +0200, Greg Kroah-Hartman wrote:
> 4.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Alexandre Belloni
>
> commit 0b0408745e7ff24757cbfd571d69026c0ddb803c upstream.
>
> LPDDR memories can only handle up to
On Thu, Apr 06, 2017 at 02:42:48PM +0200, Peter Zijlstra wrote:
> On Wed, Apr 05, 2017 at 04:52:25PM -0700, Darren Hart wrote:
> > On Wed, Mar 22, 2017 at 11:35:55AM +0100, Peter Zijlstra wrote:
> > > There's a number of 'interesting' problems, all caused by holding
> > > hb->lock while doing the
On Thu, Apr 06, 2017 at 02:42:48PM +0200, Peter Zijlstra wrote:
> On Wed, Apr 05, 2017 at 04:52:25PM -0700, Darren Hart wrote:
> > On Wed, Mar 22, 2017 at 11:35:55AM +0100, Peter Zijlstra wrote:
> > > There's a number of 'interesting' problems, all caused by holding
> > > hb->lock while doing the
Hi Eddie,
[auto build test ERROR on next-20170330]
[cannot apply to linus/master linux/master jeyu/modules-next v4.9-rc8 v4.9-rc7
v4.9-rc6 v4.11-rc5]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Eddie,
[auto build test ERROR on next-20170330]
[cannot apply to linus/master linux/master jeyu/modules-next v4.9-rc8 v4.9-rc7
v4.9-rc6 v4.11-rc5]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On 06/04/17 18:43, Daniel Kiper wrote:
> On Thu, Apr 06, 2017 at 06:22:44PM +0200, Juergen Gross wrote:
>> On 06/04/17 18:06, Daniel Kiper wrote:
>>> Hi Julien,
>>>
>>> On Thu, Apr 06, 2017 at 04:39:13PM +0100, Julien Grall wrote:
Hi Daniel,
On 06/04/17 16:20, Daniel Kiper wrote:
On 06/04/17 18:43, Daniel Kiper wrote:
> On Thu, Apr 06, 2017 at 06:22:44PM +0200, Juergen Gross wrote:
>> On 06/04/17 18:06, Daniel Kiper wrote:
>>> Hi Julien,
>>>
>>> On Thu, Apr 06, 2017 at 04:39:13PM +0100, Julien Grall wrote:
Hi Daniel,
On 06/04/17 16:20, Daniel Kiper wrote:
Hi Mark
On 7 April 2017 at 01:24, Mark Rutland wrote:
> On Fri, Apr 07, 2017 at 12:47:47AM +0800, Fu Wei wrote:
>> On 6 April 2017 at 02:38, Mark Rutland wrote:
>> > On Sat, Apr 01, 2017 at 01:51:03AM +0800, fu@linaro.org wrote:
>> >> + /*
>>
Hi Mark
On 7 April 2017 at 01:24, Mark Rutland wrote:
> On Fri, Apr 07, 2017 at 12:47:47AM +0800, Fu Wei wrote:
>> On 6 April 2017 at 02:38, Mark Rutland wrote:
>> > On Sat, Apr 01, 2017 at 01:51:03AM +0800, fu@linaro.org wrote:
>> >> + /*
>> >> + * Get the GT timer Frame data for
Hi!
> This patch set gives up part of the printk() reliability for bounded
> latency (at least unless we detect we are really in trouble) which is IMHO
> a good trade-off for lots of users (and others can just turn this feature
> off).
If they can ever realize they were bitten by this feature.
Hi!
> This patch set gives up part of the printk() reliability for bounded
> latency (at least unless we detect we are really in trouble) which is IMHO
> a good trade-off for lots of users (and others can just turn this feature
> off).
If they can ever realize they were bitten by this feature.
When mailbox controller provides two or more channels and
they are actively used by mailbox client(s) it's very easy
to trigger the warning in hrtimer_forward():
[ 247.853060] WARNING: CPU: 6 PID: 0 at kernel/time/hrtimer.c:805
hrtimer_forward+0x88/0xd8
[ 247.853549] Modules linked in:
[
When mailbox controller provides two or more channels and
they are actively used by mailbox client(s) it's very easy
to trigger the warning in hrtimer_forward():
[ 247.853060] WARNING: CPU: 6 PID: 0 at kernel/time/hrtimer.c:805
hrtimer_forward+0x88/0xd8
[ 247.853549] Modules linked in:
[
On Thu, Apr 6, 2017 at 9:36 AM, Peter Zijlstra wrote:
>
> Something like the below, which is ugly (because I couldn't be bothered
> to resolve the header recursion and thus duplicates the monitor/mwait
> functions) and broken (because it hard assumes the hardware can do
>
On Thu, Apr 6, 2017 at 9:36 AM, Peter Zijlstra wrote:
>
> Something like the below, which is ugly (because I couldn't be bothered
> to resolve the header recursion and thus duplicates the monitor/mwait
> functions) and broken (because it hard assumes the hardware can do
> monitor/mwait).
Yeah, I
On Thu, Apr 6, 2017 at 7:56 PM, Laxman Dewangan wrote:
> On Thursday 06 April 2017 09:40 PM, Andy Shevchenko wrote:
>> On Thu, Apr 6, 2017 at 4:35 PM, Laxman Dewangan
>> wrote:
>>> Adding different flag for the Open Drain/Open Source which is valid
On Thu, Apr 6, 2017 at 7:56 PM, Laxman Dewangan wrote:
> On Thursday 06 April 2017 09:40 PM, Andy Shevchenko wrote:
>> On Thu, Apr 6, 2017 at 4:35 PM, Laxman Dewangan
>> wrote:
>>> Adding different flag for the Open Drain/Open Source which is valid
>>> only when Single ended flag is enabled.
On 04/06/2017 10:08 AM, Greg KH wrote:
On Thu, Apr 06, 2017 at 08:30:40AM -0700, Greg Hackmann wrote:
On 04/06/2017 07:30 AM, zhangshuxia...@gmail.com wrote:
From: zhangshuxiao
vfs_llseek will check whether the file mode has
FMODE_LSEEK, no return failure. But ashmem
On 04/06/2017 10:08 AM, Greg KH wrote:
On Thu, Apr 06, 2017 at 08:30:40AM -0700, Greg Hackmann wrote:
On 04/06/2017 07:30 AM, zhangshuxia...@gmail.com wrote:
From: zhangshuxiao
vfs_llseek will check whether the file mode has
FMODE_LSEEK, no return failure. But ashmem can be
lseek, so add
On Fri, Apr 07, 2017 at 12:47:47AM +0800, Fu Wei wrote:
> On 6 April 2017 at 02:38, Mark Rutland wrote:
> > On Sat, Apr 01, 2017 at 01:51:03AM +0800, fu@linaro.org wrote:
> >> + /*
> >> + * Get the GT timer Frame data for every GT Block Timer
> >> + */
> >>
On Fri, Apr 07, 2017 at 12:47:47AM +0800, Fu Wei wrote:
> On 6 April 2017 at 02:38, Mark Rutland wrote:
> > On Sat, Apr 01, 2017 at 01:51:03AM +0800, fu@linaro.org wrote:
> >> + /*
> >> + * Get the GT timer Frame data for every GT Block Timer
> >> + */
> >> + for (i = 0; i <
On Thu, Apr 06, 2017 at 02:28:32PM +0200, Peter Zijlstra wrote:
> On Wed, Apr 05, 2017 at 02:18:43PM -0700, Darren Hart wrote:
> > On Wed, Mar 22, 2017 at 11:35:52AM +0100, Peter Zijlstra wrote:
>
> > > + *
> > > + * Serialization and lifetime rules:
> > > + *
> > > + * hb->lock:
> > > + *
> > >
On Thu, Apr 06, 2017 at 02:28:32PM +0200, Peter Zijlstra wrote:
> On Wed, Apr 05, 2017 at 02:18:43PM -0700, Darren Hart wrote:
> > On Wed, Mar 22, 2017 at 11:35:52AM +0100, Peter Zijlstra wrote:
>
> > > + *
> > > + * Serialization and lifetime rules:
> > > + *
> > > + * hb->lock:
> > > + *
> > >
Hi Eddie,
[auto build test WARNING on next-20170330]
[cannot apply to linus/master linux/master jeyu/modules-next v4.9-rc8 v4.9-rc7
v4.9-rc6 v4.11-rc5]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Eddie,
[auto build test WARNING on next-20170330]
[cannot apply to linus/master linux/master jeyu/modules-next v4.9-rc8 v4.9-rc7
v4.9-rc6 v4.11-rc5]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On Wed 2017-03-29 18:25:07, Sergey Senozhatsky wrote:
> It's not always possible/safe to wake_up() printk kernel
> thread. For example, late suspend/early resume may printk()
> while timekeeping is not initialized yet, so calling into the
> scheduler may result in recursive warnings.
>
> Another
On Wed 2017-03-29 18:25:07, Sergey Senozhatsky wrote:
> It's not always possible/safe to wake_up() printk kernel
> thread. For example, late suspend/early resume may printk()
> while timekeeping is not initialized yet, so calling into the
> scheduler may result in recursive warnings.
>
> Another
On Thu, Apr 06, 2017 at 06:09:51PM +0100, Lorenzo Pieralisi wrote:
> On Thu, Apr 06, 2017 at 05:40:16PM +0100, Russell King - ARM Linux wrote:
> > On Thu, Apr 06, 2017 at 05:21:56PM +0100, Lorenzo Pieralisi wrote:
> > > Ok, so:
> > >
> > > (1) I can do asm-generic/ioremap-nopost.h, which I assume
On Thu, Apr 06, 2017 at 06:09:51PM +0100, Lorenzo Pieralisi wrote:
> On Thu, Apr 06, 2017 at 05:40:16PM +0100, Russell King - ARM Linux wrote:
> > On Thu, Apr 06, 2017 at 05:21:56PM +0100, Lorenzo Pieralisi wrote:
> > > Ok, so:
> > >
> > > (1) I can do asm-generic/ioremap-nopost.h, which I assume
On 04/05/2017 05:47 PM, Kees Cook wrote:
While examining output from trial builds with -Wformat-security enabled,
many strings were found that should be defined as "const", or as a char
array instead of char pointer. This makes some static analysis easier,
by producing fewer false positives.
As
On 04/05/2017 05:47 PM, Kees Cook wrote:
While examining output from trial builds with -Wformat-security enabled,
many strings were found that should be defined as "const", or as a char
array instead of char pointer. This makes some static analysis easier,
by producing fewer false positives.
As
On Thursday 06 April 2017 09:40 PM, Andy Shevchenko wrote:
On Thu, Apr 6, 2017 at 4:35 PM, Laxman Dewangan wrote:
Currently, the GPIO interface is said to Open Drain if it is Single
Ended and active LOW. Similarly, it is said as Open Source if it is
Single Ended and
On Thursday 06 April 2017 09:40 PM, Andy Shevchenko wrote:
On Thu, Apr 6, 2017 at 4:35 PM, Laxman Dewangan wrote:
Currently, the GPIO interface is said to Open Drain if it is Single
Ended and active LOW. Similarly, it is said as Open Source if it is
Single Ended and active HIGH.
The active
On 6 April 2017 at 22:28, Alexey Klimov wrote:
> Hi Jassi/Sudeep,
>
> On Wed, Mar 29, 2017 at 07:01:09PM +0100, Sudeep Holla wrote:
>>
>>
>> On 29/03/17 18:43, Jassi Brar wrote:
...
>> > diff --git a/drivers/mailbox/mailbox.c b/drivers/mailbox/mailbox.c
>> > index
On 6 April 2017 at 22:28, Alexey Klimov wrote:
> Hi Jassi/Sudeep,
>
> On Wed, Mar 29, 2017 at 07:01:09PM +0100, Sudeep Holla wrote:
>>
>>
>> On 29/03/17 18:43, Jassi Brar wrote:
...
>> > diff --git a/drivers/mailbox/mailbox.c b/drivers/mailbox/mailbox.c
>> > index 9dfbf7e..e06c50c 100644
>> >
Nicholas Mc Guire writes:
> The redundant init_completion() here seems to be a cut error as
> struct scsi_qla_host only has 4 completion elements to initialize,
> thus the duplicate init_completion(disable_acb_comp) is simply
> removed.
Applied to 4.12/scsi-queue.
--
Martin
Nicholas Mc Guire writes:
> The redundant init_completion() here seems to be a cut error as
> struct scsi_qla_host only has 4 completion elements to initialize,
> thus the duplicate init_completion(disable_acb_comp) is simply
> removed.
Applied to 4.12/scsi-queue.
--
Martin K. Petersen
Hi!
> printk() is quite complex internally and, basically, it does two
> slightly independent things:
> a) adds a new message to a kernel log buffer (log_store())
> b) prints kernel log messages to serial consoles (console_unlock())
>
> while (a) is guaranteed to be executed by printk(), (b)
Hi!
> printk() is quite complex internally and, basically, it does two
> slightly independent things:
> a) adds a new message to a kernel log buffer (log_store())
> b) prints kernel log messages to serial consoles (console_unlock())
>
> while (a) is guaranteed to be executed by printk(), (b)
On Thu 06-04-17 17:55:20, Mel Gorman wrote:
> On Thu, Apr 06, 2017 at 06:21:55PM +0200, Michal Hocko wrote:
> > > This was my first time using your git branch instead of applying the
> > > patches
> > > from this thread to v4.11-rc5 myself.
> >
> > OK, so this looks like another thing to
On Thu 06-04-17 17:55:20, Mel Gorman wrote:
> On Thu, Apr 06, 2017 at 06:21:55PM +0200, Michal Hocko wrote:
> > > This was my first time using your git branch instead of applying the
> > > patches
> > > from this thread to v4.11-rc5 myself.
> >
> > OK, so this looks like another thing to
Hi Rafael,
On Tue, Mar 28, 2017 at 01:30:30PM -0600, Tyler Baicar wrote:
> Tyler Baicar (9):
> acpi: apei: read ack upon ghes record consumption
> ras: acpi/apei: cper: generic error data entry v3 per ACPI 6.1
> efi: parse ARM processor error
> arm64: exception: handle Synchronous
Hi Rafael,
On Tue, Mar 28, 2017 at 01:30:30PM -0600, Tyler Baicar wrote:
> Tyler Baicar (9):
> acpi: apei: read ack upon ghes record consumption
> ras: acpi/apei: cper: generic error data entry v3 per ACPI 6.1
> efi: parse ARM processor error
> arm64: exception: handle Synchronous
Hi Lorenzo,
On 3 April 2017 at 18:45, Lorenzo Pieralisi wrote:
> On Sat, Apr 01, 2017 at 01:51:03AM +0800, fu@linaro.org wrote:
>> From: Fu Wei
>>
>> On platforms booting with ACPI, architected memory-mapped timers'
>> configuration data is
Hi Lorenzo,
On 3 April 2017 at 18:45, Lorenzo Pieralisi wrote:
> On Sat, Apr 01, 2017 at 01:51:03AM +0800, fu@linaro.org wrote:
>> From: Fu Wei
>>
>> On platforms booting with ACPI, architected memory-mapped timers'
>> configuration data is provided by firmware through the ACPI GTDT
>>
On Thu, Apr 06, 2017 at 05:40:16PM +0100, Russell King - ARM Linux wrote:
> On Thu, Apr 06, 2017 at 05:21:56PM +0100, Lorenzo Pieralisi wrote:
> > Ok, so:
> >
> > (1) I can do asm-generic/ioremap-nopost.h, which I assume you want to
> > contain something like
> >
> > static inline void
On Thu, Apr 06, 2017 at 05:40:16PM +0100, Russell King - ARM Linux wrote:
> On Thu, Apr 06, 2017 at 05:21:56PM +0100, Lorenzo Pieralisi wrote:
> > Ok, so:
> >
> > (1) I can do asm-generic/ioremap-nopost.h, which I assume you want to
> > contain something like
> >
> > static inline void
On Thu, Apr 06, 2017 at 08:30:40AM -0700, Greg Hackmann wrote:
> On 04/06/2017 07:30 AM, zhangshuxia...@gmail.com wrote:
> > From: zhangshuxiao
> >
> > vfs_llseek will check whether the file mode has
> > FMODE_LSEEK, no return failure. But ashmem can be
> > lseek, so add
On Thu, Apr 06, 2017 at 02:17:28PM +0200, Peter Zijlstra wrote:
> On Wed, Apr 05, 2017 at 08:02:17AM -0700, Darren Hart wrote:
> > > @@ -1364,20 +1364,18 @@ static int wake_futex_pi(u32 __user *uad
> > > pi_state->owner = new_owner;
> > > raw_spin_unlock(_owner->pi_lock);
> > >
> > > /*
>
On Thu, Apr 06, 2017 at 08:30:40AM -0700, Greg Hackmann wrote:
> On 04/06/2017 07:30 AM, zhangshuxia...@gmail.com wrote:
> > From: zhangshuxiao
> >
> > vfs_llseek will check whether the file mode has
> > FMODE_LSEEK, no return failure. But ashmem can be
> > lseek, so add FMODE_LSEEK to ashmem
On Thu, Apr 06, 2017 at 02:17:28PM +0200, Peter Zijlstra wrote:
> On Wed, Apr 05, 2017 at 08:02:17AM -0700, Darren Hart wrote:
> > > @@ -1364,20 +1364,18 @@ static int wake_futex_pi(u32 __user *uad
> > > pi_state->owner = new_owner;
> > > raw_spin_unlock(_owner->pi_lock);
> > >
> > > /*
>
On Thursday 06 April 2017 08:56 PM, Jon Hunter wrote:
On 06/04/17 15:21, Laxman Dewangan wrote:
In some of NVIDIA Tegra's platform, PWM controller is used to
control the PWM controlled regulators. PWM signal is connected to
the VID pin of the regulator where duty cycle of PWM signal decide
the
On Thursday 06 April 2017 08:56 PM, Jon Hunter wrote:
On 06/04/17 15:21, Laxman Dewangan wrote:
In some of NVIDIA Tegra's platform, PWM controller is used to
control the PWM controlled regulators. PWM signal is connected to
the VID pin of the regulator where duty cycle of PWM signal decide
the
On Thu, 6 Apr 2017 12:01:37 -0500
Timur Tabi wrote:
> Is there a way I can send a "boot" command after ktest connects to the
> console?
>
Not currently, but that is something I've been wanting to add for some
time.
John?
-- Steve
On Thu, 6 Apr 2017 12:01:37 -0500
Timur Tabi wrote:
> Is there a way I can send a "boot" command after ktest connects to the
> console?
>
Not currently, but that is something I've been wanting to add for some
time.
John?
-- Steve
On Thu, 6 Apr 2017 18:53:04 +0200
Auger Eric wrote:
> Hi Alex,
>
> On 06/04/2017 16:53, Alex Williamson wrote:
> > If the mmap_sem is contented then the vfio type1 IOMMU backend will
> > defer locked page accounting updates to a workqueue task. This has
> > a few
On Thu, 6 Apr 2017 18:53:04 +0200
Auger Eric wrote:
> Hi Alex,
>
> On 06/04/2017 16:53, Alex Williamson wrote:
> > If the mmap_sem is contented then the vfio type1 IOMMU backend will
> > defer locked page accounting updates to a workqueue task. This has
> > a few problems and depending on
On 04/05/17 14:02, SeongJae Park wrote:
> Signed-off-by: SeongJae Park
> ---
> Documentation/vm/transhuge.txt | 10 +-
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/vm/transhuge.txt b/Documentation/vm/transhuge.txt
> index
On 04/05/17 14:02, SeongJae Park wrote:
> Signed-off-by: SeongJae Park
> ---
> Documentation/vm/transhuge.txt | 10 +-
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/vm/transhuge.txt b/Documentation/vm/transhuge.txt
> index cd28d5ee5273..4e22578e50d3
Oops, it was actually v2.
On Thursday 06 April 2017 08:47 PM, Jon Hunter wrote:
On 06/04/17 15:21, Laxman Dewangan wrote:
In some of NVIDIA Tegra's platform, PWM controller is used to
control the PWM controlled regulators. PWM signal is connected to
the VID pin of the regulator where duty
Oops, it was actually v2.
On Thursday 06 April 2017 08:47 PM, Jon Hunter wrote:
On 06/04/17 15:21, Laxman Dewangan wrote:
In some of NVIDIA Tegra's platform, PWM controller is used to
control the PWM controlled regulators. PWM signal is connected to
the VID pin of the regulator where duty
On Thu, Apr 06, 2017 at 02:15:05PM +0200, Peter Zijlstra wrote:
> On Fri, Mar 24, 2017 at 05:37:02PM -0700, Darren Hart wrote:
> >
> > But, Peter are you testing this with anything in particular?
>
> Testing? :-)
>
> I ran some of the futex pi tests we have, and have a slightly modified
>
On Thu, Apr 06, 2017 at 02:15:05PM +0200, Peter Zijlstra wrote:
> On Fri, Mar 24, 2017 at 05:37:02PM -0700, Darren Hart wrote:
> >
> > But, Peter are you testing this with anything in particular?
>
> Testing? :-)
>
> I ran some of the futex pi tests we have, and have a slightly modified
>
501 - 600 of 1976 matches
Mail list logo