From: Robin Gong
Add set_pretimeout since our watchdog driver has those interfaces and
obviously, the new common watchdog framework didn't implement this
interface.
Signed-off-by: Robin Gong
[vzapolskiy: rebased, added an inline comment to describe
From: Robin Gong
Add set_pretimeout since our watchdog driver has those interfaces and
obviously, the new common watchdog framework didn't implement this
interface.
Signed-off-by: Robin Gong
[vzapolskiy: rebased, added an inline comment to describe new interface]
Signed-off-by: Vladimir
Noop watchdog pretimeout governor, only an informational message is
added to the kernel log buffer.
Signed-off-by: Vladimir Zapolskiy
---
Changes from v2 to v3:
* temporarily removed tristate option, the governor can be built-in only
Changes from v1 to v2:
*
Noop watchdog pretimeout governor, only an informational message is
added to the kernel log buffer.
Signed-off-by: Vladimir Zapolskiy
---
Changes from v2 to v3:
* temporarily removed tristate option, the governor can be built-in only
Changes from v1 to v2:
* removed #ifdef
There is no point in calculating the residue if state does not
exist to store the value.
Signed-off-by: Peter Griffin
---
drivers/dma/sun6i-dma.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dma/sun6i-dma.c b/drivers/dma/sun6i-dma.c
index
There is no point in calculating the residue if state does not
exist to store the value.
Signed-off-by: Peter Griffin
---
drivers/dma/sun6i-dma.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dma/sun6i-dma.c b/drivers/dma/sun6i-dma.c
index 5065ca4..3835fcd 100644
Hi Vinod,
This series is a bunch of cleanup updates to various
dmaengine drivers, based on some of the review feeback to my fdma series.
regards,
Peter.
Peter Griffin (8):
dmaengine: fsl-edma: Fix clock handling error paths
dmaengine: fsl-edma: print error code in error messages.
Hi Vinod,
This series is a bunch of cleanup updates to various
dmaengine drivers, based on some of the review feeback to my fdma series.
regards,
Peter.
Peter Griffin (8):
dmaengine: fsl-edma: Fix clock handling error paths
dmaengine: fsl-edma: print error code in error messages.
If kzalloc() fails it will issue it's own error message including
a dump_stack(). So remove the site specific error messages.
Signed-off-by: Peter Griffin
---
drivers/dma/amba-pl08x.c| 10 +-
drivers/dma/bestcomm/bestcomm.c | 2 --
drivers/dma/edma.c
There is no point calculating the residue if there is
no txstate to store the value.
Signed-off-by: Peter Griffin
---
drivers/dma/ste_dma40.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dma/ste_dma40.c b/drivers/dma/ste_dma40.c
index
If kzalloc() fails it will issue it's own error message including
a dump_stack(). So remove the site specific error messages.
Signed-off-by: Peter Griffin
---
drivers/dma/amba-pl08x.c| 10 +-
drivers/dma/bestcomm/bestcomm.c | 2 --
drivers/dma/edma.c | 16
There is no point calculating the residue if there is
no txstate to store the value.
Signed-off-by: Peter Griffin
---
drivers/dma/ste_dma40.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dma/ste_dma40.c b/drivers/dma/ste_dma40.c
index 6fb8307..378cc47 100644
---
On Tue, Jun 07, 2016 at 08:45:53PM +0800, Boqun Feng wrote:
> On Tue, Jun 07, 2016 at 02:00:16PM +0200, Peter Zijlstra wrote:
> > On Tue, Jun 07, 2016 at 07:43:15PM +0800, Boqun Feng wrote:
> > > On Mon, Jun 06, 2016 at 06:08:36PM +0200, Peter Zijlstra wrote:
> > > > diff --git
On Tue, Jun 07, 2016 at 08:45:53PM +0800, Boqun Feng wrote:
> On Tue, Jun 07, 2016 at 02:00:16PM +0200, Peter Zijlstra wrote:
> > On Tue, Jun 07, 2016 at 07:43:15PM +0800, Boqun Feng wrote:
> > > On Mon, Jun 06, 2016 at 06:08:36PM +0200, Peter Zijlstra wrote:
> > > > diff --git
Hi Mel,
2016-06-03 14:36 GMT+02:00 Mel Gorman :
> On Fri, Jun 03, 2016 at 01:57:06PM +0200, Marcin Wojtas wrote:
>> >> For the record: the newest kernel I was able to reproduce the dumps
>> >> was v4.6: http://pastebin.com/ekDdACn5. I've just checked v4.7-rc1,
>> >>
Hi Mel,
2016-06-03 14:36 GMT+02:00 Mel Gorman :
> On Fri, Jun 03, 2016 at 01:57:06PM +0200, Marcin Wojtas wrote:
>> >> For the record: the newest kernel I was able to reproduce the dumps
>> >> was v4.6: http://pastebin.com/ekDdACn5. I've just checked v4.7-rc1,
>> >> which comprise a lot (mainly
Hi,
[auto build test WARNING on robh/for-next]
[also build test WARNING on v4.7-rc2 next-20160607]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Peter-Griffin/Add-support-for-FDMA-DMA
Hi,
[auto build test WARNING on robh/for-next]
[also build test WARNING on v4.7-rc2 next-20160607]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Peter-Griffin/Add-support-for-FDMA-DMA
Hi Bart,
> As you know with configfs it is not allowed to create directories in the
> configfs hierarchy from inside the kernel.
Of course you can, and every user of configfs relies on being able
to create directories from the kernel using either the default_groups
list, or through the use of
On Jun 7, 2016, at 1:10 PM, Jeff Layton wrote:
> On Tue, 2016-06-07 at 11:37 -0400, Oleg Drokin wrote:
>> Hello!
>>
>>I've been trying to better understand this problem I was having where
>> sometimes
>>a formerly NFS-exported mountpoint becomes unmountable (after nfsd stop).
>>
>>
On Mon, May 30, 2016 at 10:53:15AM +0100, Jose Abreu wrote:
A few small things but this looks basically fine.
> + if (isr[i] & 0x33)
> + irq_valid = true;
This checks for a mask of 0x33 but...
> +
> + /*
> + * Check if TX fifo is empty.
Hi Bart,
> As you know with configfs it is not allowed to create directories in the
> configfs hierarchy from inside the kernel.
Of course you can, and every user of configfs relies on being able
to create directories from the kernel using either the default_groups
list, or through the use of
On Jun 7, 2016, at 1:10 PM, Jeff Layton wrote:
> On Tue, 2016-06-07 at 11:37 -0400, Oleg Drokin wrote:
>> Hello!
>>
>>I've been trying to better understand this problem I was having where
>> sometimes
>>a formerly NFS-exported mountpoint becomes unmountable (after nfsd stop).
>>
>>
On Mon, May 30, 2016 at 10:53:15AM +0100, Jose Abreu wrote:
A few small things but this looks basically fine.
> + if (isr[i] & 0x33)
> + irq_valid = true;
This checks for a mask of 0x33 but...
> +
> + /*
> + * Check if TX fifo is empty.
On Tue, Jun 07, 2016 at 10:34:01PM +0530, Anchal Jain wrote:
> Modify the return statement.
> The Coccinelle semantic patch used to make this change is as follows:
>
> @@
> expression e, ret;
> @@
>
> -ret =
> +return
> e;
> -return ret;
>
> Delete the declaration of the return variable
On Tue, Jun 07, 2016 at 10:34:01PM +0530, Anchal Jain wrote:
> Modify the return statement.
> The Coccinelle semantic patch used to make this change is as follows:
>
> @@
> expression e, ret;
> @@
>
> -ret =
> +return
> e;
> -return ret;
>
> Delete the declaration of the return variable
On Tue, Jun 07, 2016 at 07:06:00PM +0200, Marc Haber wrote:
> On Fri, Jun 03, 2016 at 08:35:11AM -0700, Greg KH wrote:
> > On Fri, Jun 03, 2016 at 08:53:58AM +0200, Marc Haber wrote:
> > > On Mon, May 30, 2016 at 01:47:12PM -0700, Greg KH wrote:
> > > > On Mon, May 30, 2016 at 09:02:54PM +0200,
On Tue, Jun 07, 2016 at 07:06:00PM +0200, Marc Haber wrote:
> On Fri, Jun 03, 2016 at 08:35:11AM -0700, Greg KH wrote:
> > On Fri, Jun 03, 2016 at 08:53:58AM +0200, Marc Haber wrote:
> > > On Mon, May 30, 2016 at 01:47:12PM -0700, Greg KH wrote:
> > > > On Mon, May 30, 2016 at 09:02:54PM +0200,
On Wed, May 25, 2016 at 11:29:40AM -0500, ttha...@opensource.altera.com wrote:
> From: Thor Thayer
>
> To better support child devices, the ECC manager needs to be
> implemented as an IRQ controller.
>
> Signed-off-by: Thor Thayer
>
On Wed, May 25, 2016 at 11:29:40AM -0500, ttha...@opensource.altera.com wrote:
> From: Thor Thayer
>
> To better support child devices, the ECC manager needs to be
> implemented as an IRQ controller.
>
> Signed-off-by: Thor Thayer
> ---
> drivers/edac/altera_edac.c | 162
>
On Sat, Jun 04, 2016 at 08:24:26AM +0200, Boris Brezillon wrote:
> On Fri, 3 Jun 2016 13:20:06 -0700 Brian Norris
> wrote:
> > On Fri, Jun 03, 2016 at 10:23:02AM +0200, Boris Brezillon wrote:
> > > @@ -75,6 +77,19 @@ static void rockchip_pwm_set_enable_v1(struct
On Sat, Jun 04, 2016 at 08:24:26AM +0200, Boris Brezillon wrote:
> On Fri, 3 Jun 2016 13:20:06 -0700 Brian Norris
> wrote:
> > On Fri, Jun 03, 2016 at 10:23:02AM +0200, Boris Brezillon wrote:
> > > @@ -75,6 +77,19 @@ static void rockchip_pwm_set_enable_v1(struct pwm_chip
> > > *chip,
> > >
On Sat, Jun 04, 2016 at 08:19:55AM +0200, Boris Brezillon wrote:
> On Fri, 3 Jun 2016 13:03:26 -0700
> Brian Norris wrote:
>
> > On Fri, Jun 03, 2016 at 10:23:01AM +0200, Boris Brezillon wrote:
> > > The current implementation always round down the duty and period
> > >
On Sat, Jun 04, 2016 at 08:19:55AM +0200, Boris Brezillon wrote:
> On Fri, 3 Jun 2016 13:03:26 -0700
> Brian Norris wrote:
>
> > On Fri, Jun 03, 2016 at 10:23:01AM +0200, Boris Brezillon wrote:
> > > The current implementation always round down the duty and period
> > > values, while it would be
On Tue, 2016-06-07 at 11:20 -0600, Logan Gunthorpe wrote:
> I'm working on hardware that currently has a limited number of
> scratchpad registers and ntb_ndev fails with no clue as to why. I
> feel it is better to fail early and provide a reasonable error
> message
> then to fail later on.
>
>
On Tue, 2016-06-07 at 11:20 -0600, Logan Gunthorpe wrote:
> I'm working on hardware that currently has a limited number of
> scratchpad registers and ntb_ndev fails with no clue as to why. I
> feel it is better to fail early and provide a reasonable error
> message
> then to fail later on.
>
>
On Tue, Jun 07, 2016 at 03:45:43PM +0200, Max Staudt wrote:
> When using efifb with a 16-bit (5:6:5) visual, fbcon's text is rendered
> in the wrong colors - e.g. text gray (#aa) is rendered as green
> (#50bc50) and neighboring pixels have slightly different values
> (such as #50bc78).
>
>
On Tue, Jun 07, 2016 at 03:45:43PM +0200, Max Staudt wrote:
> When using efifb with a 16-bit (5:6:5) visual, fbcon's text is rendered
> in the wrong colors - e.g. text gray (#aa) is rendered as green
> (#50bc50) and neighboring pixels have slightly different values
> (such as #50bc78).
>
>
On Mon, 6 Jun 2016 13:24:21 +0300
Aleksei Mamlin wrote:
> From: Boris Brezillon
>
> Add NAND Flash controller node definition to the A20 SoC.
>
> Signed-off-by: Boris Brezillon
> Signed-off-by:
On Mon, 6 Jun 2016 13:24:21 +0300
Aleksei Mamlin wrote:
> From: Boris Brezillon
>
> Add NAND Flash controller node definition to the A20 SoC.
>
> Signed-off-by: Boris Brezillon
> Signed-off-by: Aleksei Mamlin
> ---
> arch/arm/boot/dts/sun7i-a20.dtsi | 11 +++
> 1 file changed, 11
On Tue, Jun 07, 2016 at 04:12:29PM +0200, Heiko Stübner wrote:
> Hi Guenter,
>
> Am Dienstag, 7. Juni 2016, 06:19:45 schrieb Guenter Roeck:
> > On Tue, Jun 7, 2016 at 2:54 AM, Heiko Stübner wrote:
> > > Hi Frank,
> > >
> > > Am Montag, 6. Juni 2016, 17:20:04 schrieb Frank Wang:
On Tue, May 24, 2016 at 6:31 AM, Hoan Tran wrote:
> Hi Rob,
>
> Thanks for your review !
>
> On Mon, May 23, 2016 at 1:30 PM, Rob Herring wrote:
>>
>> On Mon, May 16, 2016 at 09:17:25AM -0700, Hoan Tran wrote:
>> > This patch adds the APM X-Gene hwmon device tree
On Tue, May 24, 2016 at 6:31 AM, Hoan Tran wrote:
> Hi Rob,
>
> Thanks for your review !
>
> On Mon, May 23, 2016 at 1:30 PM, Rob Herring wrote:
>>
>> On Mon, May 16, 2016 at 09:17:25AM -0700, Hoan Tran wrote:
>> > This patch adds the APM X-Gene hwmon device tree node documentation.
>> >
>> >
On Tue, Jun 07, 2016 at 04:12:29PM +0200, Heiko Stübner wrote:
> Hi Guenter,
>
> Am Dienstag, 7. Juni 2016, 06:19:45 schrieb Guenter Roeck:
> > On Tue, Jun 7, 2016 at 2:54 AM, Heiko Stübner wrote:
> > > Hi Frank,
> > >
> > > Am Montag, 6. Juni 2016, 17:20:04 schrieb Frank Wang:
> > >> The newer
Hi Jon,
Thanks for the feedback. I'll send an updated patch in a moment.
On 04/06/16 09:40 AM, Jon Mason wrote:
> Nit, please add spaces around '*' (per checkpatch)
I'll change this, but I did run it through checkpatch and it did not
warn about this.
> Please explicitly point out that this is
Hi Jon,
Thanks for the feedback. I'll send an updated patch in a moment.
On 04/06/16 09:40 AM, Jon Mason wrote:
> Nit, please add spaces around '*' (per checkpatch)
I'll change this, but I did run it through checkpatch and it did not
warn about this.
> Please explicitly point out that this is
On Tue, Jun 7, 2016 at 1:14 AM, Li, Yong B wrote:
> Thanks Tony.
>
> I checked the DTS/overlays using linux-yocto-4.1 kernel(Ostro OS). It seems
> to me that the kernel/u-boot do not include the latest overlay support patch.
> And I also tested the latest Debian 8.4 using
On Tue, Jun 7, 2016 at 1:14 AM, Li, Yong B wrote:
> Thanks Tony.
>
> I checked the DTS/overlays using linux-yocto-4.1 kernel(Ostro OS). It seems
> to me that the kernel/u-boot do not include the latest overlay support patch.
> And I also tested the latest Debian 8.4 using BBB boards, the I2C1
On Tue, 2016-06-07 at 12:43 -0400, George Spelvin wrote:
> Andy Shevchenko wrote:
> > To be sure it faster we need the measurements. Sometimes it's not
> > obvious.
[]
> Speaking pedantically, you're right. But as a practical matter, it's
> very unlikely, and what makes it truly insignificant is
On Tue, 2016-06-07 at 12:43 -0400, George Spelvin wrote:
> Andy Shevchenko wrote:
> > To be sure it faster we need the measurements. Sometimes it's not
> > obvious.
[]
> Speaking pedantically, you're right. But as a practical matter, it's
> very unlikely, and what makes it truly insignificant is
On Tue, 2016-06-07 at 11:37 -0400, Oleg Drokin wrote:
> Hello!
>
> I've been trying to better understand this problem I was having where
> sometimes
> a formerly NFS-exported mountpoint becomes unmountable (after nfsd stop).
>
> I finally traced it to a leaked filedescriptor that was
On Tue, 2016-06-07 at 11:37 -0400, Oleg Drokin wrote:
> Hello!
>
> I've been trying to better understand this problem I was having where
> sometimes
> a formerly NFS-exported mountpoint becomes unmountable (after nfsd stop).
>
> I finally traced it to a leaked filedescriptor that was
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 analogix_dp driver would export six hooks.
>
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 analogix_dp driver would export six hooks.
>
On Fri, Jun 03, 2016 at 08:35:11AM -0700, Greg KH wrote:
> On Fri, Jun 03, 2016 at 08:53:58AM +0200, Marc Haber wrote:
> > On Mon, May 30, 2016 at 01:47:12PM -0700, Greg KH wrote:
> > > On Mon, May 30, 2016 at 09:02:54PM +0200, Marc Haber wrote:
> > > > Hi,
> > > >
> > > > on my Bananapis, in
On Fri, Jun 03, 2016 at 08:35:11AM -0700, Greg KH wrote:
> On Fri, Jun 03, 2016 at 08:53:58AM +0200, Marc Haber wrote:
> > On Mon, May 30, 2016 at 01:47:12PM -0700, Greg KH wrote:
> > > On Mon, May 30, 2016 at 09:02:54PM +0200, Marc Haber wrote:
> > > > Hi,
> > > >
> > > > on my Bananapis, in
On 30/05/16 05:19, HS Liao wrote:
This patch is first version of Mediatek Command Queue(CMDQ) driver. The
CMDQ is used to help read/write registers with critical time limitation,
such as updating display configuration during the vblank. It controls
Global Command Engine (GCE) hardware to
On 30/05/16 05:19, HS Liao wrote:
This patch is first version of Mediatek Command Queue(CMDQ) driver. The
CMDQ is used to help read/write registers with critical time limitation,
such as updating display configuration during the vblank. It controls
Global Command Engine (GCE) hardware to
Modify the return statement.
The Coccinelle semantic patch used to make this change is as follows:
@@
expression e, ret;
@@
-ret =
+return
e;
-return ret;
Delete the declaration of the return variable rc, as it is no longer used.
Signed-off-by: Anchal Jain
---
Modify the return statement.
The Coccinelle semantic patch used to make this change is as follows:
@@
expression e, ret;
@@
-ret =
+return
e;
-return ret;
Delete the declaration of the return variable rc, as it is no longer used.
Signed-off-by: Anchal Jain
---
changes in v2
Since nothing's really happened with this patch for a while I figured I'd take
over trying to get this upstream.
Regarding testing: This seems to work fine on the 60 series laptops, and works
fine on previous generations. The one thing I haven't been able to test is an X1
carbon with an adaptive
Since nothing's really happened with this patch for a while I figured I'd take
over trying to get this upstream.
Regarding testing: This seems to work fine on the 60 series laptops, and works
fine on previous generations. The one thing I haven't been able to test is an X1
carbon with an adaptive
On 06/06/2016 02:22 PM, Christoph Hellwig wrote:
The target is configured using configfs, and configurable entities are:
- NVMe subsystems and namespaces
- NVMe over Fabrics ports and referrals
- Host ACLs for primitive access control - NVMe over Fabrics access
control is still work in
On 06/06/2016 02:22 PM, Christoph Hellwig wrote:
The target is configured using configfs, and configurable entities are:
- NVMe subsystems and namespaces
- NVMe over Fabrics ports and referrals
- Host ACLs for primitive access control - NVMe over Fabrics access
control is still work in
On 03/06/16 15:11, Matthias Brugger wrote:
[...]
+
+smp_mb(); /* modify jump before enable thread */
+}
+
+cmdq_thread_writel(thread, task->pa_base +
task->command_size,
+ CMDQ_THR_END_ADDR);
+cmdq_thread_resume(thread);
+}
+
On 03/06/16 15:11, Matthias Brugger wrote:
[...]
+
+smp_mb(); /* modify jump before enable thread */
+}
+
+cmdq_thread_writel(thread, task->pa_base +
task->command_size,
+ CMDQ_THR_END_ADDR);
+cmdq_thread_resume(thread);
+}
+
On Mon, Jun 06, 2016 at 04:28:08PM +0300, Heikki Krogerus wrote:
[ ... ]
>
> I would prefer lower case letters. I don't know the SIDs there are at
> them moment, other then Display Port. Do you know them?
>
SIDs:
0xff00 - power delivery
0xff01 - displayport
0xff02 - MHL
On Mon, Jun 06, 2016 at 04:28:08PM +0300, Heikki Krogerus wrote:
[ ... ]
>
> I would prefer lower case letters. I don't know the SIDs there are at
> them moment, other then Display Port. Do you know them?
>
SIDs:
0xff00 - power delivery
0xff01 - displayport
0xff02 - MHL
Attention Owner Of Atm Card,
We here by wish to notify you that this office {BCEAO BANK BURKINA FASO} has
been mandated to issue out your payment of $1.5m USD through an ATM MASTER
CARD. You have to stop further communication with any other person(s) or
offices to avoid any hitch in receiving
Attention Owner Of Atm Card,
We here by wish to notify you that this office {BCEAO BANK BURKINA FASO} has
been mandated to issue out your payment of $1.5m USD through an ATM MASTER
CARD. You have to stop further communication with any other person(s) or
offices to avoid any hitch in receiving
From: Borislav Petkov
A simple data structure for collecting correctable errors along with
accessors. More detailed description in the code itself.
Signed-off-by: Borislav Petkov
---
arch/x86/kernel/cpu/mcheck/mce.c | 120 +--
arch/x86/ras/Kconfig
From: Borislav Petkov
So this set cannot have a bigger "RFC" tag:
It attempts to revive the correctable errors collector. In this version,
the thing gets counters in debugfs:
(debugfs)/ras/cec/
|-- array
`-- pfn
which give some stats on the CEC like how many CEs it caught and
From: Borislav Petkov
A simple data structure for collecting correctable errors along with
accessors. More detailed description in the code itself.
Signed-off-by: Borislav Petkov
---
arch/x86/kernel/cpu/mcheck/mce.c | 120 +--
arch/x86/ras/Kconfig | 11 +
From: Borislav Petkov
So this set cannot have a bigger "RFC" tag:
It attempts to revive the correctable errors collector. In this version,
the thing gets counters in debugfs:
(debugfs)/ras/cec/
|-- array
`-- pfn
which give some stats on the CEC like how many CEs it caught and the
number of
From: Tony Luck
Move all code relating to /dev/mcelog to own source file. /dev/mcelog
driver can now operate from the machine check notifier with lowest prio.
Boris:
* Move the mce_helper and trigger functionality behind
CONFIG_X86_MCELOG.
Signed-off-by: Tony Luck
From: Borislav Petkov
We're reusing mce_amd_inj's debugfs interface so that mce-inject can
benefit from it too. The old functionality is still preserved under
CONFIG_X86_MCELOG.
Signed-off-by: Borislav Petkov
---
arch/x86/Kconfig| 2 +-
From: Tony Luck
Move all code relating to /dev/mcelog to own source file. /dev/mcelog
driver can now operate from the machine check notifier with lowest prio.
Boris:
* Move the mce_helper and trigger functionality behind
CONFIG_X86_MCELOG.
Signed-off-by: Tony Luck
Signed-off-by: Borislav
From: Borislav Petkov
We're reusing mce_amd_inj's debugfs interface so that mce-inject can
benefit from it too. The old functionality is still preserved under
CONFIG_X86_MCELOG.
Signed-off-by: Borislav Petkov
---
arch/x86/Kconfig| 2 +-
From: Borislav Petkov
... and simplify a bit.
No functionality change.
Signed-off-by: Borislav Petkov
---
arch/x86/kernel/cpu/mcheck/mce-inject.c | 30 --
1 file changed, 12 insertions(+), 18 deletions(-)
diff --git
From: Borislav Petkov
... and simplify a bit.
No functionality change.
Signed-off-by: Borislav Petkov
---
arch/x86/kernel/cpu/mcheck/mce-inject.c | 30 --
1 file changed, 12 insertions(+), 18 deletions(-)
diff --git a/arch/x86/kernel/cpu/mcheck/mce-inject.c
On Thu, May 26, 2016 at 08:45:03AM +0200, Vincent Guittot wrote:
> On 25 May 2016 at 11:12, Morten Rasmussen wrote:
> > On Tue, May 24, 2016 at 05:53:27PM +0200, Vincent Guittot wrote:
> >> On 24 May 2016 at 17:02, Morten Rasmussen wrote:
> >>
On Thu, May 26, 2016 at 08:45:03AM +0200, Vincent Guittot wrote:
> On 25 May 2016 at 11:12, Morten Rasmussen wrote:
> > On Tue, May 24, 2016 at 05:53:27PM +0200, Vincent Guittot wrote:
> >> On 24 May 2016 at 17:02, Morten Rasmussen wrote:
> >> > On Tue, May 24, 2016 at 03:52:00PM +0200, Vincent
We use similar structured code to read and write the kmapped
firmware pages. The only difference is read copies from the kmap
region and write copies to it. Consolidate this into one function
to reduce duplication.
Cc: Vikram Mulukutla
Signed-off-by: Stephen Boyd
We use similar structured code to read and write the kmapped
firmware pages. The only difference is read copies from the kmap
region and write copies to it. Consolidate this into one function
to reduce duplication.
Cc: Vikram Mulukutla
Signed-off-by: Stephen Boyd
---
On 06/07/2016 10:32 AM, Shaun Tancheff wrote:
submit_bio_wait() gives the caller an opportunity to examine
struct bio and so expects the caller to issue the put_bio()
This fixes a memory leak reported by a few people in 4.7-rc2
kmemleak report after 9082e87bfbf8 ("block: remove struct
Some systems are memory constrained but they need to load very
large firmwares. The firmware subsystem allows drivers to request
this firmware be loaded from the filesystem, but this requires
that the entire firmware be loaded into kernel memory first
before it's provided to the driver. This can
On 06/07/2016 10:32 AM, Shaun Tancheff wrote:
submit_bio_wait() gives the caller an opportunity to examine
struct bio and so expects the caller to issue the put_bio()
This fixes a memory leak reported by a few people in 4.7-rc2
kmemleak report after 9082e87bfbf8 ("block: remove struct
Some systems are memory constrained but they need to load very
large firmwares. The firmware subsystem allows drivers to request
this firmware be loaded from the filesystem, but this requires
that the entire firmware be loaded into kernel memory first
before it's provided to the driver. This can
Some systems are memory constrained but they need to load very
large firmwares. The firmware subsystem allows drivers to request
this firmware be loaded from the filesystem, but this requires
that the entire firmware be loaded into kernel memory first
before it's provided to the driver. This can
Some systems are memory constrained but they need to load very
large firmwares. The firmware subsystem allows drivers to request
this firmware be loaded from the filesystem, but this requires
that the entire firmware be loaded into kernel memory first
before it's provided to the driver. This can
From: Vikram Mulukutla
Some low memory systems with complex peripherals cannot afford to
have the relatively large firmware images taking up valuable
memory during suspend and resume. Change the internal
implementation of firmware_class to disallow caching based on a
From: Vikram Mulukutla
Some low memory systems with complex peripherals cannot afford to
have the relatively large firmware images taking up valuable
memory during suspend and resume. Change the internal
implementation of firmware_class to disallow caching based on a
configurable option. In the
Ah sorry, I seem to have missed updating that one place (it was in
multiple places). I'll resend properly.
On 7 June 2016 at 01:45, Russell King - ARM Linux wrote:
> And you're still doing it, after I've already pointed out that you
> posted these to linux-arm and not
Looks fine,
Reviewed-by: Christoph Hellwig
Looks fine,
Reviewed-by: Christoph Hellwig
Ah sorry, I seem to have missed updating that one place (it was in
multiple places). I'll resend properly.
On 7 June 2016 at 01:45, Russell King - ARM Linux wrote:
> And you're still doing it, after I've already pointed out that you
> posted these to linux-arm and not linux-arm-kernel. By
On 6/7/2016 3:23 AM, Krzysztof Kozlowski wrote:
> On 06/06/2016 06:56 PM, Rhyland Klein wrote:
>> Add check to power_supply_read_temp() to only use the power_supply
>> get_property() callback if the use_cnt is > 0. The use_cnt will
>> be incremented at the end of __power_supply_register, so this
On 6/7/2016 3:23 AM, Krzysztof Kozlowski wrote:
> On 06/06/2016 06:56 PM, Rhyland Klein wrote:
>> Add check to power_supply_read_temp() to only use the power_supply
>> get_property() callback if the use_cnt is > 0. The use_cnt will
>> be incremented at the end of __power_supply_register, so this
Andy Shevchenko wrote:
> Something wrong with mail configuration?
Oops, sorry, I forgot to delete the header.
> On Sun, 2016-06-05 at 15:25 -0400, George Spelvin wrote:
>> It's also faster, as hex_to_bin() *is* inlined within hex2bin()
>> (if you compile with -O).
> To be sure it faster
Andy Shevchenko wrote:
> Something wrong with mail configuration?
Oops, sorry, I forgot to delete the header.
> On Sun, 2016-06-05 at 15:25 -0400, George Spelvin wrote:
>> It's also faster, as hex_to_bin() *is* inlined within hex2bin()
>> (if you compile with -O).
> To be sure it faster
901 - 1000 of 2408 matches
Mail list logo