On Wed, 2016-07-13 at 15:47 +1000, alast...@au1.ibm.com wrote:
> From: Alastair D'Silva
> > This series allows the vmx_crypto module to be detected and
> automatically
> loaded via UDEV if the CPU supports the vector crypto feature.
> > Alastair D'Silva (2):
> powerpc: Add
On Wed, 2016-07-13 at 15:47 +1000, alast...@au1.ibm.com wrote:
> From: Alastair D'Silva
> > This series allows the vmx_crypto module to be detected and
> automatically
> loaded via UDEV if the CPU supports the vector crypto feature.
> > Alastair D'Silva (2):
> powerpc: Add module autoloading
From: Alastair D'Silva
This patch utilises the GENERIC_CPU_AUTOPROBE infrastructure
to automatically load the vmx_crypto module if the CPU supports
it.
Signed-off-by: Alastair D'Silva
---
drivers/crypto/vmx/Kconfig | 2 +-
drivers/crypto/vmx/vmx.c
On Tue, Jul 12, 2016 at 12:18:05PM +0100, Mel Gorman wrote:
> On Tue, Jul 12, 2016 at 09:06:04PM +1000, Balbir Singh wrote:
> > > diff --git a/Documentation/cgroup-v1/memory.txt
> > > b/Documentation/cgroup-v1/memory.txt
> > > index b14abf217239..946e69103cdd 100644
> > > ---
From: Alastair D'Silva
This patch utilises the GENERIC_CPU_AUTOPROBE infrastructure
to automatically load the vmx_crypto module if the CPU supports
it.
Signed-off-by: Alastair D'Silva
---
drivers/crypto/vmx/Kconfig | 2 +-
drivers/crypto/vmx/vmx.c
From: Alastair D'Silva
This series allows the vmx_crypto module to be detected and automatically
loaded via UDEV if the CPU supports the vector crypto feature.
Alastair D'Silva (2):
powerpc: Add module autoloading based on CPU features
crypto: vmx - Convert to CPU
From: Alastair D'Silva
This series allows the vmx_crypto module to be detected and automatically
loaded via UDEV if the CPU supports the vector crypto feature.
Alastair D'Silva (2):
powerpc: Add module autoloading based on CPU features
crypto: vmx - Convert to CPU feature based module
From: Alastair D'Silva
This patch utilises the GENERIC_CPU_AUTOPROBE infrastructure
to automatically load the vmx_crypto module if the CPU supports
it.
Signed-off-by: Alastair D'Silva
---
drivers/crypto/vmx/Kconfig | 2 +-
drivers/crypto/vmx/vmx.c | 6 ++
2 files changed, 3
On Tue, Jul 12, 2016 at 12:18:05PM +0100, Mel Gorman wrote:
> On Tue, Jul 12, 2016 at 09:06:04PM +1000, Balbir Singh wrote:
> > > diff --git a/Documentation/cgroup-v1/memory.txt
> > > b/Documentation/cgroup-v1/memory.txt
> > > index b14abf217239..946e69103cdd 100644
> > > ---
From: Alastair D'Silva
This patch utilises the GENERIC_CPU_AUTOPROBE infrastructure
to automatically load the vmx_crypto module if the CPU supports
it.
Signed-off-by: Alastair D'Silva
---
drivers/crypto/vmx/Kconfig | 2 +-
drivers/crypto/vmx/vmx.c | 6 ++
2 files changed, 3
From: Alastair D'Silva
This patch provides the necessary infrastructure to allow drivers
to be automatically loaded via UDEV. It implements the minimum
required to be able to use module_cpu_feature_match to trigger
the GENERIC_CPU_AUTOPROBE mechanisms.
The features exposed
From: Alastair D'Silva
This patch provides the necessary infrastructure to allow drivers
to be automatically loaded via UDEV. It implements the minimum
required to be able to use module_cpu_feature_match to trigger
the GENERIC_CPU_AUTOPROBE mechanisms.
The features exposed
From: Alastair D'Silva
This patch provides the necessary infrastructure to allow drivers
to be automatically loaded via UDEV. It implements the minimum
required to be able to use module_cpu_feature_match to trigger
the GENERIC_CPU_AUTOPROBE mechanisms.
The features exposed are a mirror of the
From: Alastair D'Silva
This patch provides the necessary infrastructure to allow drivers
to be automatically loaded via UDEV. It implements the minimum
required to be able to use module_cpu_feature_match to trigger
the GENERIC_CPU_AUTOPROBE mechanisms.
The features exposed are a mirror of the
Hi Felipe:
Could you please give me some suggestions if you have already reviewed
some codes.
Thanks a lot.
On Wed, 2016-06-15 at 11:07 +0800, Chunfeng Yun wrote:
> From 48552e96e4e33f8830cb6a59154fe148425532fd Mon Sep 17 00:00:00 2001
> From: Chunfeng Yun
> Date:
Cc Petr Mladek.
On (07/12/16 16:19), Viresh Kumar wrote:
[..]
> Okay, we have tracked this BUG and its really interesting.
good find!
> I hacked the platform's serial driver to implement a putchar() routine
> that simply writes to the FIFO in polling mode, that helped us in
> tracing on where
Hi Felipe:
Could you please give me some suggestions if you have already reviewed
some codes.
Thanks a lot.
On Wed, 2016-06-15 at 11:07 +0800, Chunfeng Yun wrote:
> From 48552e96e4e33f8830cb6a59154fe148425532fd Mon Sep 17 00:00:00 2001
> From: Chunfeng Yun
> Date: Wed, 15 Jun 2016 10:58:10
Cc Petr Mladek.
On (07/12/16 16:19), Viresh Kumar wrote:
[..]
> Okay, we have tracked this BUG and its really interesting.
good find!
> I hacked the platform's serial driver to implement a putchar() routine
> that simply writes to the FIFO in polling mode, that helped us in
> tracing on where
On Fri, Jul 08, 2016 at 04:35:45PM +0200, Bastien Nocera wrote:
> On Wed, 2016-06-29 at 19:28 +1000, Peter Hutterer wrote:
> > +static int hidpp_battery_get_property(struct power_supply *psy,
> > + enum power_supply_property psp,
> > +
On Fri, Jul 08, 2016 at 04:35:45PM +0200, Bastien Nocera wrote:
> On Wed, 2016-06-29 at 19:28 +1000, Peter Hutterer wrote:
> > +static int hidpp_battery_get_property(struct power_supply *psy,
> > + enum power_supply_property psp,
> > +
Commit 6d07b68ce16a ("ipc/sem.c: optimize sem_lock()") introduced a
race:
sem_lock has a fast path that allows parallel simple operations.
There are two reasons why a simple operation cannot run in parallel:
- a non-simple operations is ongoing (sma->sem_perm.lock held)
- a complex operation is
With 2c610022711 (locking/qspinlock: Fix spin_unlock_wait() some more),
memory barriers were added into spin_unlock_wait().
Thus another barrier is not required.
And as explained in 055ce0fd1b8 (locking/qspinlock: Add comments),
spin_lock() provides a barrier so that reads within the critical
Hi Andrew, Hi Peter,
next version of the sem_lock() fixes:
The patches are again vs. tip.
Patch 1 is ready for merging, Patch 2 is for review.
- Patch 1 is the patch as in -next since January
It fixes the race that was found by Felix.
- Patch 2 removes the memory barriers that are part of the
Commit 6d07b68ce16a ("ipc/sem.c: optimize sem_lock()") introduced a
race:
sem_lock has a fast path that allows parallel simple operations.
There are two reasons why a simple operation cannot run in parallel:
- a non-simple operations is ongoing (sma->sem_perm.lock held)
- a complex operation is
With 2c610022711 (locking/qspinlock: Fix spin_unlock_wait() some more),
memory barriers were added into spin_unlock_wait().
Thus another barrier is not required.
And as explained in 055ce0fd1b8 (locking/qspinlock: Add comments),
spin_lock() provides a barrier so that reads within the critical
Hi Andrew, Hi Peter,
next version of the sem_lock() fixes:
The patches are again vs. tip.
Patch 1 is ready for merging, Patch 2 is for review.
- Patch 1 is the patch as in -next since January
It fixes the race that was found by Felix.
- Patch 2 removes the memory barriers that are part of the
Russell King - ARM Linux writes:
> On Tue, Jul 12, 2016 at 10:58:05PM +0200, Petr Tesarik wrote:
>> I'm not an expert on DTB, so I can't provide an example of code
>> execution, but you have already mentioned the /chosen/linux,stdout-path
>> property. If an attacker
Russell King - ARM Linux writes:
> On Tue, Jul 12, 2016 at 10:58:05PM +0200, Petr Tesarik wrote:
>> I'm not an expert on DTB, so I can't provide an example of code
>> execution, but you have already mentioned the /chosen/linux,stdout-path
>> property. If an attacker redirects the bootloader to an
Instant cash Loan with same day payout on all kinds of Loan are available at
Quick Financial Home were loan is offered at 2% per annul. Email:
quickloa...@foxmail.com
Instant cash Loan with same day payout on all kinds of Loan are available at
Quick Financial Home were loan is offered at 2% per annul. Email:
quickloa...@foxmail.com
On Fri, Jun 24, 2016 at 5:40 PM, Andrew Duggan wrote:
> On 06/10/2016 10:25 PM, Bjorn Andersson wrote:
>>
>> From: Bjorn Andersson
>>
>> Support the two supplies - vdd and vio - to make it possible to control
>> power to the Synaptics chip.
On Fri, Jun 24, 2016 at 5:40 PM, Andrew Duggan wrote:
> On 06/10/2016 10:25 PM, Bjorn Andersson wrote:
>>
>> From: Bjorn Andersson
>>
>> Support the two supplies - vdd and vio - to make it possible to control
>> power to the Synaptics chip.
>>
>> Signed-off-by: Bjorn Andersson
>> Signed-off-by:
Hi all:
We found that guests such as RHEL6, they occasionally got stuck after
migration.
The stack of the stuck guest kernel is as follows:
PID: 18 TASK: 88007de61500 CPU: 1 COMMAND: "xenwatch"
#0 [88007de62e40] schedule at 8150d692
#1 [88007de62f08] io_schedule at
Hi all:
We found that guests such as RHEL6, they occasionally got stuck after
migration.
The stack of the stuck guest kernel is as follows:
PID: 18 TASK: 88007de61500 CPU: 1 COMMAND: "xenwatch"
#0 [88007de62e40] schedule at 8150d692
#1 [88007de62f08] io_schedule at
Dear Rob,
On 2016/7/11 23:13, Rob Herring wrote:
On Thu, Jul 07, 2016 at 10:58:44AM +0800, William Wu wrote:
This patch adds the devicetree documentation required for Rockchip
USB3.0 core wrapper consisting of USB3.0 IP from Synopsys.
It supports DRD mode, and could operate in device mode
Dear Rob,
On 2016/7/11 23:13, Rob Herring wrote:
On Thu, Jul 07, 2016 at 10:58:44AM +0800, William Wu wrote:
This patch adds the devicetree documentation required for Rockchip
USB3.0 core wrapper consisting of USB3.0 IP from Synopsys.
It supports DRD mode, and could operate in device mode
Dear Rob,
On 2016/7/11 22:58, Rob Herring wrote:
On Thu, Jul 07, 2016 at 10:54:24AM +0800, William Wu wrote:
Add a quirk to configure the core to support the
UTMI+ PHY with an 8- or 16-bit interface. UTMI+ PHY
interface is hardware property, and it's platform
dependent. Normall, the PHYIf can
Dear Rob,
On 2016/7/11 22:58, Rob Herring wrote:
On Thu, Jul 07, 2016 at 10:54:24AM +0800, William Wu wrote:
Add a quirk to configure the core to support the
UTMI+ PHY with an 8- or 16-bit interface. UTMI+ PHY
interface is hardware property, and it's platform
dependent. Normall, the PHYIf can
This patch fix a double word "is is" found in in
Documentation/DocBook/device-drivers.xml.
It is because the file was created from comments in sources,
so I have to fix the double words in include/linux/input.h
Signed-off-by: Masanari Iida
---
include/linux/input.h | 2 +-
On Tue, Jul 12, 2016 at 05:08:43PM -0700, Andrew Vagin wrote:
> Here is a patch to get an owning user namespace:
> https://github.com/avagin/linux-task-diag/commit/7fad8ff3fc4110bebf0920cec2388390b3bd2238
> https://github.com/avagin/linux-task-diag/commit/2663bc803d324785e328261f3c07a0fef37d2088
>
This patch fix a double word "is is" found in in
Documentation/DocBook/device-drivers.xml.
It is because the file was created from comments in sources,
so I have to fix the double words in include/linux/input.h
Signed-off-by: Masanari Iida
---
include/linux/input.h | 2 +-
1 file changed, 1
On Tue, Jul 12, 2016 at 05:08:43PM -0700, Andrew Vagin wrote:
> Here is a patch to get an owning user namespace:
> https://github.com/avagin/linux-task-diag/commit/7fad8ff3fc4110bebf0920cec2388390b3bd2238
> https://github.com/avagin/linux-task-diag/commit/2663bc803d324785e328261f3c07a0fef37d2088
>
On Sat, Jul 09, 2016 at 01:29:20PM -0500, Eric W. Biederman wrote:
> ebied...@xmission.com (Eric W. Biederman) writes:
>
> > Andrew Vagin writes:
> >
> >> All these thoughts about security make me thinking that kcmp is what we
> >> should use here. It's maybe something like
On Sat, Jul 09, 2016 at 01:29:20PM -0500, Eric W. Biederman wrote:
> ebied...@xmission.com (Eric W. Biederman) writes:
>
> > Andrew Vagin writes:
> >
> >> All these thoughts about security make me thinking that kcmp is what we
> >> should use here. It's maybe something like this:
> >>
> >>
Dear Rob,
On 2016/7/11 22:54, Rob Herring wrote:
On Fri, Jul 08, 2016 at 02:33:09PM +0200, Heiko Stuebner wrote:
Hi William,
Am Donnerstag, 7. Juli 2016, 10:54:24 schrieb William Wu:
Add a quirk to configure the core to support the
UTMI+ PHY with an 8- or 16-bit interface. UTMI+ PHY
Dear Rob,
On 2016/7/11 22:54, Rob Herring wrote:
On Fri, Jul 08, 2016 at 02:33:09PM +0200, Heiko Stuebner wrote:
Hi William,
Am Donnerstag, 7. Juli 2016, 10:54:24 schrieb William Wu:
Add a quirk to configure the core to support the
UTMI+ PHY with an 8- or 16-bit interface. UTMI+ PHY
Read data fails sometimes because of a timeout that PMIC cannot transfer data
to PMIC wrap on time, extend the waiting time to 10ms to reduce the failed
rate.
Signed-off-by: Henry Chen
---
Resend to fixed the typo on commit message
---
Daniel,
On 07/12/2016 08:38 PM, Daniel Vetter wrote:
On Fri, Jul 01, 2016 at 02:00:00PM -0400, Sean Paul wrote:
On Fri, Jul 1, 2016 at 5:19 AM, Yakir Yang wrote:
The PSR driver have exported four symbols for specific device driver:
- rockchip_drm_psr_register()
-
Read data fails sometimes because of a timeout that PMIC cannot transfer data
to PMIC wrap on time, extend the waiting time to 10ms to reduce the failed
rate.
Signed-off-by: Henry Chen
---
Resend to fixed the typo on commit message
---
drivers/soc/mediatek/mtk-pmic-wrap.c | 2 +-
1 file
Daniel,
On 07/12/2016 08:38 PM, Daniel Vetter wrote:
On Fri, Jul 01, 2016 at 02:00:00PM -0400, Sean Paul wrote:
On Fri, Jul 1, 2016 at 5:19 AM, Yakir Yang wrote:
The PSR driver have exported four symbols for specific device driver:
- rockchip_drm_psr_register()
-
I send this email to test the connection to linux-kernel maillist. Just
ignore.
在 7/11/2016 4:11 PM, Songshan Gong 写道:
在 7/8/2016 11:18 PM, Jiri Olsa 写道:
On Thu, Jul 07, 2016 at 09:49:36AM +0800, Song Shan Gong wrote:
At preset, when creating module's map, perf gets 'start' address by
I send this email to test the connection to linux-kernel maillist. Just
ignore.
在 7/11/2016 4:11 PM, Songshan Gong 写道:
在 7/8/2016 11:18 PM, Jiri Olsa 写道:
On Thu, Jul 07, 2016 at 09:49:36AM +0800, Song Shan Gong wrote:
At preset, when creating module's map, perf gets 'start' address by
Dear Heiko,
On 2016/7/10 7:47, Heiko Stuebner wrote:
Am Samstag, 9. Juli 2016, 11:38:00 schrieb William.wu:
Dear Heiko & Balbi,
On 2016/7/8 21:29, Felipe Balbi wrote:
Hi,
Heiko Stuebner writes:
Am Donnerstag, 7. Juli 2016, 10:54:24 schrieb William Wu:
Add a quirk to
Dear Heiko,
On 2016/7/10 7:47, Heiko Stuebner wrote:
Am Samstag, 9. Juli 2016, 11:38:00 schrieb William.wu:
Dear Heiko & Balbi,
On 2016/7/8 21:29, Felipe Balbi wrote:
Hi,
Heiko Stuebner writes:
Am Donnerstag, 7. Juli 2016, 10:54:24 schrieb William Wu:
Add a quirk to configure the core
Now there are several locks which are marked as
no_validate, so name of the lock class can be
different with the no_validate lock.
This patch avoids this warning for this case, and
fix the following warning:
[ 14.413292] [ cut here ]
[ 14.413297] WARNING: CPU: 1 PID:
Now there are several locks which are marked as
no_validate, so name of the lock class can be
different with the no_validate lock.
This patch avoids this warning for this case, and
fix the following warning:
[ 14.413292] [ cut here ]
[ 14.413297] WARNING: CPU: 1 PID:
On Tue, Jul 12, 2016 at 9:00 PM, Greg KH wrote:
> On Tue, Jul 12, 2016 at 02:42:22PM -0400, Kees Cook wrote:
>> On Thu, Jul 7, 2016 at 2:14 PM, Kees Cook wrote:
>> > Hi,
>> >
>> > Please pull these lkdtm changes for next.
>>
>> Friendly ping...
Stephen Rothwell writes:
> On Mon, 11 Jul 2016 16:07:39 -0300 Paulo Flabiano Smorigo
> wrote:
>>
>> diff --git a/drivers/crypto/vmx/aesp8-ppc.pl
>> b/drivers/crypto/vmx/aesp8-ppc.pl
>> index 2280539..813ffcc 100644
>> ---
On Tue, Jul 12, 2016 at 9:00 PM, Greg KH wrote:
> On Tue, Jul 12, 2016 at 02:42:22PM -0400, Kees Cook wrote:
>> On Thu, Jul 7, 2016 at 2:14 PM, Kees Cook wrote:
>> > Hi,
>> >
>> > Please pull these lkdtm changes for next.
>>
>> Friendly ping... I'd like this refactor to make it in time for the
Stephen Rothwell writes:
> On Mon, 11 Jul 2016 16:07:39 -0300 Paulo Flabiano Smorigo
> wrote:
>>
>> diff --git a/drivers/crypto/vmx/aesp8-ppc.pl
>> b/drivers/crypto/vmx/aesp8-ppc.pl
>> index 2280539..813ffcc 100644
>> --- a/drivers/crypto/vmx/aesp8-ppc.pl
>> +++
22.155003] evbug: Connected device: input0 (Power Button at
>>LNXPWRBN/button/input0)
>>
>>
>>FYI, raw QEMU command line is:
>>
>> qemu-system-x86_64 -enable-kvm -cpu Nehalem -kernel /pkg/linux/x86_64-
>>randconfig-s0-07121340/gcc-
>>6/9696ef14ded07fb
Hi Chanwoo Choi
On 07/13/2016 10:05 AM, Chanwoo Choi wrote:
Hi Chris,
On 2016년 07월 13일 10:39, Chris Zhong wrote:
Hi Chanwoo Choi
On 07/13/2016 09:11 AM, Chanwoo Choi wrote:
Hi Chris,
I'm now developing the extcon property on extcon-test branch.
But, it has not been completed.
On next
>>
>>
>>FYI, raw QEMU command line is:
>>
>> qemu-system-x86_64 -enable-kvm -cpu Nehalem -kernel /pkg/linux/x86_64-
>>randconfig-s0-07121340/gcc-
>>6/9696ef14ded07fb0847f8e1cdda6d98a89ecd4f2/vmlinuz-4.7.0-rc4-00110-g9696ef1
>>-append 'root=/dev/ram0 u
Hi Chanwoo Choi
On 07/13/2016 10:05 AM, Chanwoo Choi wrote:
Hi Chris,
On 2016년 07월 13일 10:39, Chris Zhong wrote:
Hi Chanwoo Choi
On 07/13/2016 09:11 AM, Chanwoo Choi wrote:
Hi Chris,
I'm now developing the extcon property on extcon-test branch.
But, it has not been completed.
On next
On 07/12/16 at 03:50pm, Mark Rutland wrote:
> On Tue, Jul 12, 2016 at 04:24:10PM +0200, Arnd Bergmann wrote:
> > On Tuesday, July 12, 2016 10:18:11 AM CEST Vivek Goyal wrote:
> > > >
> > > > On Open Firmware, the DT is extracted from running firmware and copied
> > > > into dynamically allocated
Hi all,
Today's linux-next merge of the drm-misc tree got a conflict in:
drivers/gpu/drm/rockchip/rockchip_drm_drv.c
between commit:
062993b15e8e ("drm: convert DT component matching to
component_match_add_release()")
from the arm tree and commit:
6d5fa28c13b9 ("gpu: drm:
On 07/12/16 at 03:50pm, Mark Rutland wrote:
> On Tue, Jul 12, 2016 at 04:24:10PM +0200, Arnd Bergmann wrote:
> > On Tuesday, July 12, 2016 10:18:11 AM CEST Vivek Goyal wrote:
> > > >
> > > > On Open Firmware, the DT is extracted from running firmware and copied
> > > > into dynamically allocated
Hi all,
Today's linux-next merge of the drm-misc tree got a conflict in:
drivers/gpu/drm/rockchip/rockchip_drm_drv.c
between commit:
062993b15e8e ("drm: convert DT component matching to
component_match_add_release()")
from the arm tree and commit:
6d5fa28c13b9 ("gpu: drm:
On Tue, Jul 12 2016 at 10:18pm -0400,
Eric Wheeler wrote:
> On Tue, 12 Jul 2016, NeilBrown wrote:
>
> > On Tue, Jul 12 2016, Lars Ellenberg wrote:
> >
> > >
> > > Instead, I suggest to distinguish between recursive calls to
> > > generic_make_request(), and
On Tue, Jul 12 2016 at 10:18pm -0400,
Eric Wheeler wrote:
> On Tue, 12 Jul 2016, NeilBrown wrote:
>
> > On Tue, Jul 12 2016, Lars Ellenberg wrote:
> >
> > >
> > > Instead, I suggest to distinguish between recursive calls to
> > > generic_make_request(), and pushing back the remainder part
When I tested vmscale in mmtest in 32bit, I found the benchmark
was slow down 0.5 times.
basenode
1global-1
User 12.98 16.04
System147.61 166.42
Elapsed26.48 38.08
With vmstat, I found IO wait avg is much
If we use sc->reclaim_idx for accounting pgstall, it can increase
the count on unpopulated zone, for example, movable zone(but
my system doesn't have movable zone) if allocation request were
GFP_HIGHUSER_MOVABLE. It doesn't make no sense.
This patch fixes it so that it can account it on first
On Wed, Jul 13, 2016 at 3:14 AM, Nicolas Dufresne
wrote:
> Le mardi 12 juillet 2016 à 15:08 -0400, Nicolas Dufresne a écrit :
>> Le mardi 12 juillet 2016 à 16:16 +0800, Wu-Cheng Li (李務誠) a écrit :
>> > Decoder hardware produces MT21 (compressed). Image processor can
>>
Hi Dave,
Today's linux-next merge of the drm tree got a conflict in:
drivers/media/platform/omap/omap_voutdef.h
between commit:
77430f0396af ("[media] omap_vout: use control framework")
from the v4l-dvb tree and commit:
781a162244a2 ("[media] omap_vout: Switch to use the
When I tested vmscale in mmtest in 32bit, I found the benchmark
was slow down 0.5 times.
basenode
1global-1
User 12.98 16.04
System147.61 166.42
Elapsed26.48 38.08
With vmstat, I found IO wait avg is much
If we use sc->reclaim_idx for accounting pgstall, it can increase
the count on unpopulated zone, for example, movable zone(but
my system doesn't have movable zone) if allocation request were
GFP_HIGHUSER_MOVABLE. It doesn't make no sense.
This patch fixes it so that it can account it on first
On Wed, Jul 13, 2016 at 3:14 AM, Nicolas Dufresne
wrote:
> Le mardi 12 juillet 2016 à 15:08 -0400, Nicolas Dufresne a écrit :
>> Le mardi 12 juillet 2016 à 16:16 +0800, Wu-Cheng Li (李務誠) a écrit :
>> > Decoder hardware produces MT21 (compressed). Image processor can
>> > convert it to a format
Hi Dave,
Today's linux-next merge of the drm tree got a conflict in:
drivers/media/platform/omap/omap_voutdef.h
between commit:
77430f0396af ("[media] omap_vout: use control framework")
from the v4l-dvb tree and commit:
781a162244a2 ("[media] omap_vout: Switch to use the
On Tue, 12 Jul 2016, NeilBrown wrote:
> On Tue, Jul 12 2016, Lars Ellenberg wrote:
>
> >
> > Instead, I suggest to distinguish between recursive calls to
> > generic_make_request(), and pushing back the remainder part in
> > blk_queue_split(), by pointing current->bio_lists to a
> >
On Tue, 12 Jul 2016, NeilBrown wrote:
> On Tue, Jul 12 2016, Lars Ellenberg wrote:
>
> >
> > Instead, I suggest to distinguish between recursive calls to
> > generic_make_request(), and pushing back the remainder part in
> > blk_queue_split(), by pointing current->bio_lists to a
> >
2016-07-13 9:58 GMT+08:00 Xunlei Pang :
> On 2016/07/13 at 09:50, Wanpeng Li wrote:
>> 2016-07-13 1:25 GMT+08:00 :
>>> Konstantin Khlebnikov writes:
>>>
On 11.07.2016 15:12, Xunlei Pang wrote:
> On 2016/07/11 at 17:54,
There is no need to call devm_free_irq when driver detach.
devres_release_all which is called after 'drv->remove' will
release all managed resources.
Signed-off-by: Peng Fan
Reviewed-by: Robin Murphy
Cc: Will Deacon
---
V2:
2016-07-13 9:58 GMT+08:00 Xunlei Pang :
> On 2016/07/13 at 09:50, Wanpeng Li wrote:
>> 2016-07-13 1:25 GMT+08:00 :
>>> Konstantin Khlebnikov writes:
>>>
On 11.07.2016 15:12, Xunlei Pang wrote:
> On 2016/07/11 at 17:54, Wanpeng Li wrote:
>> Hi Konstantin, Xunlei,
>> 2016-07-11
There is no need to call devm_free_irq when driver detach.
devres_release_all which is called after 'drv->remove' will
release all managed resources.
Signed-off-by: Peng Fan
Reviewed-by: Robin Murphy
Cc: Will Deacon
---
V2:
Fix compile warning. Add Robin's Reviewed-by TAG.
On Tue, Jul 12 2016 at 6:22pm -0400,
Kani, Toshimitsu wrote:
> On Fri, 2016-06-24 at 14:29 -0400, Mike Snitzer wrote:
> >
> > BTW, if in your testing you could evaluate/quantify any extra overhead
> > from DM that'd be useful to share. It could be there are bottlenecks
> >
Found and fixed few very minor coding style nits, will resubmit in few days,
now still waiting for comments to v4.
https://github.com/bluecherrydvr/linux/commits/tw5864
commit 31f7c98a144cb3fb8a94662f002d9b6142d1f390
Author: Andrey Utkin
Date: Wed Jul 13
On 07/12/16 at 02:49am, 河合英宏 / KAWAI,HIDEHIRO wrote:
> Hi Dave,
>
> Thanks for the comments.
>
> > From: Dave Young [mailto:dyo...@redhat.com]
> > Sent: Monday, July 11, 2016 5:35 PM
> >
> > On 07/05/16 at 08:33pm, Hidehiro Kawai wrote:
> > > This patch fixes one of the problems reported by
On 2016/07/13 at 09:50, Wanpeng Li wrote:
> 2016-07-13 1:25 GMT+08:00 :
>> Konstantin Khlebnikov writes:
>>
>>> On 11.07.2016 15:12, Xunlei Pang wrote:
On 2016/07/11 at 17:54, Wanpeng Li wrote:
> Hi Konstantin, Xunlei,
> 2016-07-11
On Tue, Jul 12 2016 at 6:22pm -0400,
Kani, Toshimitsu wrote:
> On Fri, 2016-06-24 at 14:29 -0400, Mike Snitzer wrote:
> >
> > BTW, if in your testing you could evaluate/quantify any extra overhead
> > from DM that'd be useful to share. It could be there are bottlenecks
> > that need to be
Found and fixed few very minor coding style nits, will resubmit in few days,
now still waiting for comments to v4.
https://github.com/bluecherrydvr/linux/commits/tw5864
commit 31f7c98a144cb3fb8a94662f002d9b6142d1f390
Author: Andrey Utkin
Date: Wed Jul 13 05:00:28 2016 +0300
Fix
On 07/12/16 at 02:49am, 河合英宏 / KAWAI,HIDEHIRO wrote:
> Hi Dave,
>
> Thanks for the comments.
>
> > From: Dave Young [mailto:dyo...@redhat.com]
> > Sent: Monday, July 11, 2016 5:35 PM
> >
> > On 07/05/16 at 08:33pm, Hidehiro Kawai wrote:
> > > This patch fixes one of the problems reported by
On 2016/07/13 at 09:50, Wanpeng Li wrote:
> 2016-07-13 1:25 GMT+08:00 :
>> Konstantin Khlebnikov writes:
>>
>>> On 11.07.2016 15:12, Xunlei Pang wrote:
On 2016/07/11 at 17:54, Wanpeng Li wrote:
> Hi Konstantin, Xunlei,
> 2016-07-11 16:42 GMT+08:00 Xunlei Pang :
>> On 2016/07/11
Hi Nicolas,
On Tue, 2016-07-12 at 15:14 -0400, Nicolas Dufresne wrote:
> Le mardi 12 juillet 2016 à 15:08 -0400, Nicolas Dufresne a écrit :
> > Le mardi 12 juillet 2016 à 16:16 +0800, Wu-Cheng Li (李務誠) a écrit :
> > > Decoder hardware produces MT21 (compressed). Image processor can
> > > convert
Hi Chris,
On 2016년 07월 13일 10:39, Chris Zhong wrote:
> Hi Chanwoo Choi
>
>
> On 07/13/2016 09:11 AM, Chanwoo Choi wrote:
>> Hi Chris,
>>
>> I'm now developing the extcon property on extcon-test branch.
>> But, it has not been completed.
>>
>> On next version, I'll remove the notification about
Hi,
On Wed, Jul 13, 2016 at 09:45:43AM +0800, Shawn Lin wrote:
> 在 2016/7/13 9:31, Brian Norris 写道:
> >On Wed, Jul 13, 2016 at 09:10:15AM +0800, Shawn Lin wrote:
> >At some level, it's a matter of preference. But when you're talking
> >about the rk3399 PCIe "interrupt controller" domain, it seems
On Tue, 2016-07-12 at 16:16 +0800, Wu-Cheng Li (李務誠) wrote:
> On Mon, Jul 11, 2016 at 10:56 AM, tiffany lin
> wrote:
> > Hi Hans,
> >
> > On Fri, 2016-07-08 at 12:23 +0200, Hans Verkuil wrote:
> >> On 05/30/2016 02:29 PM, Tiffany Lin wrote:
> >> > Add V4L2_PIX_FMT_MT21
Hi Nicolas,
On Tue, 2016-07-12 at 15:14 -0400, Nicolas Dufresne wrote:
> Le mardi 12 juillet 2016 à 15:08 -0400, Nicolas Dufresne a écrit :
> > Le mardi 12 juillet 2016 à 16:16 +0800, Wu-Cheng Li (李務誠) a écrit :
> > > Decoder hardware produces MT21 (compressed). Image processor can
> > > convert
Hi Chris,
On 2016년 07월 13일 10:39, Chris Zhong wrote:
> Hi Chanwoo Choi
>
>
> On 07/13/2016 09:11 AM, Chanwoo Choi wrote:
>> Hi Chris,
>>
>> I'm now developing the extcon property on extcon-test branch.
>> But, it has not been completed.
>>
>> On next version, I'll remove the notification about
Hi,
On Wed, Jul 13, 2016 at 09:45:43AM +0800, Shawn Lin wrote:
> 在 2016/7/13 9:31, Brian Norris 写道:
> >On Wed, Jul 13, 2016 at 09:10:15AM +0800, Shawn Lin wrote:
> >At some level, it's a matter of preference. But when you're talking
> >about the rk3399 PCIe "interrupt controller" domain, it seems
On Tue, 2016-07-12 at 16:16 +0800, Wu-Cheng Li (李務誠) wrote:
> On Mon, Jul 11, 2016 at 10:56 AM, tiffany lin
> wrote:
> > Hi Hans,
> >
> > On Fri, 2016-07-08 at 12:23 +0200, Hans Verkuil wrote:
> >> On 05/30/2016 02:29 PM, Tiffany Lin wrote:
> >> > Add V4L2_PIX_FMT_MT21 documentation
> >> >
> >>
1 - 100 of 1940 matches
Mail list logo