On Fri, Feb 03, 2017 at 11:07:08PM -0500, Ed Tomlinson wrote:
> Hi,
>
> Any reports of 4.9.7 breaking X?
>
> I run arch and keep it up to date. With todays updates and 4.9.7 built here
> X will not start kde correctly. Reverting to 4.9.6 fixes things. Config is
> the same for both builds. I
On Fri, Feb 03, 2017 at 11:07:08PM -0500, Ed Tomlinson wrote:
> Hi,
>
> Any reports of 4.9.7 breaking X?
>
> I run arch and keep it up to date. With todays updates and 4.9.7 built here
> X will not start kde correctly. Reverting to 4.9.6 fixes things. Config is
> the same for both builds. I
Hi Dmitry,
[auto build test ERROR on regulator/for-next]
[also build test ERROR on v4.10-rc6 next-20170203]
[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/Dmitry-Torokhov/regulator-core-fix
Hi Dmitry,
[auto build test ERROR on regulator/for-next]
[also build test ERROR on v4.10-rc6 next-20170203]
[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/Dmitry-Torokhov/regulator-core-fix
On 01/26, Peter Zijlstra wrote:
>On Thu, Jan 26, 2017 at 05:14:06AM +0800, kernel test robot wrote:
>>
>> FYI, we noticed the following commit:
>>
>> commit: 9881b024b7d7671f6a014091bc96506b89081802 ("sched/clock: Delay
>> switching sched_clock to stable")
>>
On 01/26, Peter Zijlstra wrote:
>On Thu, Jan 26, 2017 at 05:14:06AM +0800, kernel test robot wrote:
>>
>> FYI, we noticed the following commit:
>>
>> commit: 9881b024b7d7671f6a014091bc96506b89081802 ("sched/clock: Delay
>> switching sched_clock to stable")
>>
(adding Julia Lawall)
On Fri, 2017-02-03 at 20:44 -0800, Guenter Roeck wrote:
> On Sat, Jan 28, 2017 at 07:05:09PM +1300, Derek Robson wrote:
> > A style fix across whole driver.
> > changed permissions to octal style, found using checkpatch
> >
> > Signed-off-by: Derek Robson
(adding Julia Lawall)
On Fri, 2017-02-03 at 20:44 -0800, Guenter Roeck wrote:
> On Sat, Jan 28, 2017 at 07:05:09PM +1300, Derek Robson wrote:
> > A style fix across whole driver.
> > changed permissions to octal style, found using checkpatch
> >
> > Signed-off-by: Derek Robson
>
> FWIW, I
Only a couple of comments below. Otherwise, the patch looks fine to me.
On Thu, Jan 26, 2017 at 09:00:31PM +0800, Baoyou Xie wrote:
> +static int zx2967_i2c_flush_fifos(struct zx2967_i2c_info *zx_i2c)
> +{
> + u32 val;
> + u32 offset;
> +
> + if (zx_i2c->msg_rd) {
> +
Only a couple of comments below. Otherwise, the patch looks fine to me.
On Thu, Jan 26, 2017 at 09:00:31PM +0800, Baoyou Xie wrote:
> +static int zx2967_i2c_flush_fifos(struct zx2967_i2c_info *zx_i2c)
> +{
> + u32 val;
> + u32 offset;
> +
> + if (zx_i2c->msg_rd) {
> +
On Fri, Feb 03, 2017 at 11:07:08PM -0500, Ed Tomlinson wrote:
> Hi,
>
> Any reports of 4.9.7 breaking X?
>
> I run arch and keep it up to date. With todays updates and 4.9.7 built here
> X will not start kde correctly. Reverting to 4.9.6 fixes things. Config is
> the same for both builds. I
On Fri, Feb 03, 2017 at 11:07:08PM -0500, Ed Tomlinson wrote:
> Hi,
>
> Any reports of 4.9.7 breaking X?
>
> I run arch and keep it up to date. With todays updates and 4.9.7 built here
> X will not start kde correctly. Reverting to 4.9.6 fixes things. Config is
> the same for both builds. I
FYI, we noticed the following commit:
commit: 0dba1314d4f81115dce711292ec7981d17231064 ("scsi, block: fix duplicate
bdi name registration crashes")
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git
for-4.11/next
in testcase: boot
on test machine: qemu-system-i386
FYI, we noticed the following commit:
commit: 0dba1314d4f81115dce711292ec7981d17231064 ("scsi, block: fix duplicate
bdi name registration crashes")
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git
for-4.11/next
in testcase: boot
on test machine: qemu-system-i386
Hi Lorenzo,
On 2017/2/4 2:36, Lorenzo Pieralisi wrote:
> Hanjun, Sinan,
>
> On Wed, Jan 18, 2017 at 08:54:50PM +0800, Hanjun Guo wrote:
>> From: Hanjun Guo
>>
>> With platform msi support landed in the kernel, and the introduction
>> of IORT for GICv3 ITS (PCI MSI) and
Hi Lorenzo,
On 2017/2/4 2:36, Lorenzo Pieralisi wrote:
> Hanjun, Sinan,
>
> On Wed, Jan 18, 2017 at 08:54:50PM +0800, Hanjun Guo wrote:
>> From: Hanjun Guo
>>
>> With platform msi support landed in the kernel, and the introduction
>> of IORT for GICv3 ITS (PCI MSI) and SMMU, the framework for
On February 04, 2017 7:33 AM Shaohua Li wrote:
> @@ -1404,6 +1401,8 @@ bool madvise_free_huge_pmd(struct mmu_gather *tlb,
> struct vm_area_struct *vma,
> set_pmd_at(mm, addr, pmd, orig_pmd);
> tlb_remove_pmd_tlb_entry(tlb, pmd, addr);
> }
> +
> +
On February 04, 2017 7:33 AM Shaohua Li wrote:
> @@ -1404,6 +1401,8 @@ bool madvise_free_huge_pmd(struct mmu_gather *tlb,
> struct vm_area_struct *vma,
> set_pmd_at(mm, addr, pmd, orig_pmd);
> tlb_remove_pmd_tlb_entry(tlb, pmd, addr);
> }
> +
> +
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
WIP.sched/core
head: f83f0b0647162b099f62e62c203b1cfb90b40239
commit: 297dfd2a653a202557af465e87e0aa5d106a15b1 [118/144] sched/headers:
Remove from
config: mips-cavium_octeon_defconfig (attached as .config)
compiler:
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
WIP.sched/core
head: f83f0b0647162b099f62e62c203b1cfb90b40239
commit: 297dfd2a653a202557af465e87e0aa5d106a15b1 [118/144] sched/headers:
Remove from
config: mips-cavium_octeon_defconfig (attached as .config)
compiler:
> On Fri, Feb 03, 2017 at 04:13:40PM +0200, Andy Shevchenko wrote:
> > On Fri, Feb 3, 2017 at 4:06 PM, Michał Kępień wrote:
> > > Darren, Andy,
> > >
> > > Please drop this patch series for now. I will send a rebased v2 after a
> > > long overdue patch series from Alan Jenkins
> On Fri, Feb 03, 2017 at 04:13:40PM +0200, Andy Shevchenko wrote:
> > On Fri, Feb 3, 2017 at 4:06 PM, Michał Kępień wrote:
> > > Darren, Andy,
> > >
> > > Please drop this patch series for now. I will send a rebased v2 after a
> > > long overdue patch series from Alan Jenkins gets applied in a
Hi Nishanth,
> On 02/03/2017 05:21 PM, Lukasz Majewski wrote:
> > Hi Dave,
> >
> > Thanks for sharing the knowledge :-)
> >
> >> On 02/03/2017 09:24 AM, Lukasz Majewski wrote:
> >>> The "opp_high" property brings support for 1.5 GHz CPU frequency
> >>> for TI's am57xx line of processors.
> >>>
>
Hi Nishanth,
> On 02/03/2017 05:21 PM, Lukasz Majewski wrote:
> > Hi Dave,
> >
> > Thanks for sharing the knowledge :-)
> >
> >> On 02/03/2017 09:24 AM, Lukasz Majewski wrote:
> >>> The "opp_high" property brings support for 1.5 GHz CPU frequency
> >>> for TI's am57xx line of processors.
> >>>
>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
WIP.sched/core
head: f83f0b0647162b099f62e62c203b1cfb90b40239
commit: 3ab291518ff78c8410fd336e02eb59f10d98d4e7 [138/144] sched/headers: Split
out of
config: mips-nlm_xlr_defconfig (attached as .config)
compiler:
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
WIP.sched/core
head: f83f0b0647162b099f62e62c203b1cfb90b40239
commit: 3ab291518ff78c8410fd336e02eb59f10d98d4e7 [138/144] sched/headers: Split
out of
config: mips-nlm_xlr_defconfig (attached as .config)
compiler:
On Friday 03 February 2017 11:02 PM, Sasha Levin wrote:
On Mon, Jan 30, 2017 at 7:30 AM, George Cherian
wrote:
This series adds the support for Cavium Cryptographic Accelerarion Unit (CPT)
CPT is available in Cavium's Octeon-Tx SoC series.
The series was tested
On Friday 03 February 2017 11:02 PM, Sasha Levin wrote:
On Mon, Jan 30, 2017 at 7:30 AM, George Cherian
wrote:
This series adds the support for Cavium Cryptographic Accelerarion Unit (CPT)
CPT is available in Cavium's Octeon-Tx SoC series.
The series was tested with ecryptfs and dm-crypt for
Changed function definition argument to have identifier name.
found using checkpatch
Signed-off-by: Derek Robson
---
Version 1 had missing ; and so broke the build
drivers/staging/speakup/spk_priv.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Changed function definition argument to have identifier name.
found using checkpatch
Signed-off-by: Derek Robson
---
Version 1 had missing ; and so broke the build
drivers/staging/speakup/spk_priv.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Cc Greg
On (01/24/17 14:19), Sergey Senozhatsky wrote:
> Hello Peter, Mikulas
>
> just came across this patch https://lkml.org/lkml/2016/5/17/440
>
> Peter, are you still planning to merge it? or is there something
> that made you change your mind?
ping
-ss
Cc Greg
On (01/24/17 14:19), Sergey Senozhatsky wrote:
> Hello Peter, Mikulas
>
> just came across this patch https://lkml.org/lkml/2016/5/17/440
>
> Peter, are you still planning to merge it? or is there something
> that made you change your mind?
ping
-ss
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
WIP.sched/core
head: f83f0b0647162b099f62e62c203b1cfb90b40239
commit: 3ab291518ff78c8410fd336e02eb59f10d98d4e7 [138/144] sched/headers: Split
out of
config: mips-malta_kvm_defconfig (attached as .config)
compiler:
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
WIP.sched/core
head: f83f0b0647162b099f62e62c203b1cfb90b40239
commit: 3ab291518ff78c8410fd336e02eb59f10d98d4e7 [138/144] sched/headers: Split
out of
config: mips-malta_kvm_defconfig (attached as .config)
compiler:
On Sat, Jan 28, 2017 at 07:05:09PM +1300, Derek Robson wrote:
> A style fix across whole driver.
> changed permissions to octal style, found using checkpatch
>
> Signed-off-by: Derek Robson
FWIW, I think changes like this are best done using coccinelle.
That ensures that the
On Sat, Jan 28, 2017 at 07:05:09PM +1300, Derek Robson wrote:
> A style fix across whole driver.
> changed permissions to octal style, found using checkpatch
>
> Signed-off-by: Derek Robson
FWIW, I think changes like this are best done using coccinelle.
That ensures that the results can be
Fix checkpatch error:
ERROR: space prohibited before that close parenthesis ')'
Signed-off-by: Youngdo Lee
---
drivers/staging/fbtft/fbtft-bus.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/fbtft/fbtft-bus.c
Fix checkpatch error:
ERROR: space prohibited before that close parenthesis ')'
Signed-off-by: Youngdo Lee
---
drivers/staging/fbtft/fbtft-bus.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/fbtft/fbtft-bus.c
b/drivers/staging/fbtft/fbtft-bus.c
index
On Sat, Feb 04, 2017 at 11:47:38AM +0800, Yisheng Xie wrote:
> On 2016/10/18 1:06, Andy Lutomirski wrote:
> > hw_random carefully avoids using a stack buffer except in
> > add_early_randomness(). This causes a crash in virtio_rng if
> > CONFIG_VMAP_STACK=y.
> I try to understand this patch, but I
On Sat, Feb 04, 2017 at 11:47:38AM +0800, Yisheng Xie wrote:
> On 2016/10/18 1:06, Andy Lutomirski wrote:
> > hw_random carefully avoids using a stack buffer except in
> > add_early_randomness(). This causes a crash in virtio_rng if
> > CONFIG_VMAP_STACK=y.
> I try to understand this patch, but I
Hi Sasha,
Thanks for the reveiw.
On Friday 03 February 2017 12:24 AM, Sasha Levin wrote:
On Mon, Jan 30, 2017 at 7:30 AM, George Cherian
wrote:
diff --git a/drivers/crypto/cavium/cpt/cptvf_main.c
b/drivers/crypto/cavium/cpt/cptvf_main.c
new file mode 100644
Hi Sasha,
Thanks for the reveiw.
On Friday 03 February 2017 12:24 AM, Sasha Levin wrote:
On Mon, Jan 30, 2017 at 7:30 AM, George Cherian
wrote:
diff --git a/drivers/crypto/cavium/cpt/cptvf_main.c
b/drivers/crypto/cavium/cpt/cptvf_main.c
new file mode 100644
index 000..4cf466d
---
>
>
> > +static void free_extended_page_bitmap(struct virtio_balloon *vb) {
> > + int i, bmap_count = vb->nr_page_bmap;
> > +
> > + for (i = 1; i < bmap_count; i++) {
> > + kfree(vb->page_bitmap[i]);
> > + vb->page_bitmap[i] = NULL;
> > + vb->nr_page_bmap--;
> >
>
>
> > +static void free_extended_page_bitmap(struct virtio_balloon *vb) {
> > + int i, bmap_count = vb->nr_page_bmap;
> > +
> > + for (i = 1; i < bmap_count; i++) {
> > + kfree(vb->page_bitmap[i]);
> > + vb->page_bitmap[i] = NULL;
> > + vb->nr_page_bmap--;
> >
On Sat, Feb 04, 2017 at 12:56:41PM +1300, Derek Robson wrote:
> Changed function definition argument to have identifier name.
> found using checkpatch
>
> Signed-off-by: Derek Robson
> ---
> drivers/staging/speakup/spk_priv.h | 4 ++--
> 1 file changed, 2 insertions(+), 2
On Sat, Feb 04, 2017 at 12:56:41PM +1300, Derek Robson wrote:
> Changed function definition argument to have identifier name.
> found using checkpatch
>
> Signed-off-by: Derek Robson
> ---
> drivers/staging/speakup/spk_priv.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff
On Sat, 2017-02-04 at 16:31 +1300, Derek Robson wrote:
> On Sat, Feb 04, 2017 at 10:41:20AM +0800, kbuild test robot wrote:
> > Hi Derek,
> >
> > [auto build test ERROR on staging/staging-testing]
> > [also build test ERROR on v4.10-rc6 next-20170203]
> > [if y
On Sat, 2017-02-04 at 16:31 +1300, Derek Robson wrote:
> On Sat, Feb 04, 2017 at 10:41:20AM +0800, kbuild test robot wrote:
> > Hi Derek,
> >
> > [auto build test ERROR on staging/staging-testing]
> > [also build test ERROR on v4.10-rc6 next-20170203]
> > [if y
Here's the sequence of events as I see it:
Repair_HID is a standalone function that removes one reference on the incoming
object. For simple _HID objects, this in fact deletes the object.
For _CID, all elements of the package are examined. If a repair was made on a
_HID within the _CID
Here's the sequence of events as I see it:
Repair_HID is a standalone function that removes one reference on the incoming
object. For simple _HID objects, this in fact deletes the object.
For _CID, all elements of the package are examined. If a repair was made on a
_HID within the _CID
Hi,
Any reports of 4.9.7 breaking X?
I run arch and keep it up to date. With todays updates and 4.9.7 built
here X will not start kde correctly. Reverting to 4.9.6 fixes things.
Config is the same for both builds. I have three btrfs patches and the BFQ
4.9.0-v8r7 patchset applied on top
Hi,
Any reports of 4.9.7 breaking X?
I run arch and keep it up to date. With todays updates and 4.9.7 built
here X will not start kde correctly. Reverting to 4.9.6 fixes things.
Config is the same for both builds. I have three btrfs patches and the BFQ
4.9.0-v8r7 patchset applied on top
On 2017/2/3 22:50, Sinan Kaya wrote:
> On 1/18/2017 7:54 AM, Hanjun Guo wrote:
>> From: Hanjun Guo
>>
>> With platform msi support landed in the kernel, and the introduction
>> of IORT for GICv3 ITS (PCI MSI) and SMMU, the framework for platform msi
>> is ready, this patch
On 2017/2/3 22:50, Sinan Kaya wrote:
> On 1/18/2017 7:54 AM, Hanjun Guo wrote:
>> From: Hanjun Guo
>>
>> With platform msi support landed in the kernel, and the introduction
>> of IORT for GICv3 ITS (PCI MSI) and SMMU, the framework for platform msi
>> is ready, this patch set add few patches to
Hi Andy,
On 2016/10/18 1:06, Andy Lutomirski wrote:
> hw_random carefully avoids using a stack buffer except in
> add_early_randomness(). This causes a crash in virtio_rng if
> CONFIG_VMAP_STACK=y.
I try to understand this patch, but I do not know why it will cause
a crash in virtio_rng with
Hi Andy,
On 2016/10/18 1:06, Andy Lutomirski wrote:
> hw_random carefully avoids using a stack buffer except in
> add_early_randomness(). This causes a crash in virtio_rng if
> CONFIG_VMAP_STACK=y.
I try to understand this patch, but I do not know why it will cause
a crash in virtio_rng with
This patch adds thermal driver for ZTE's zx2967 family.
Signed-off-by: Baoyou Xie
---
drivers/thermal/Kconfig | 8 ++
drivers/thermal/Makefile | 1 +
drivers/thermal/zx2967_thermal.c | 255 +++
3 files changed, 264
This patch adds thermal driver for ZTE's zx2967 family.
Signed-off-by: Baoyou Xie
---
drivers/thermal/Kconfig | 8 ++
drivers/thermal/Makefile | 1 +
drivers/thermal/zx2967_thermal.c | 255 +++
3 files changed, 264 insertions(+)
create
This patch adds dt-binding documentation for zx2967 family thermal sensor.
Signed-off-by: Baoyou Xie
Acked-by: Rob Herring
Reviewed-by: Shawn Guo
---
.../devicetree/bindings/thermal/zx2967-thermal.txt | 116 +
1
Add the zx2967 thermal drivers as maintained by ARM ZTE
architecture maintainers, as they're parts of the core IP.
Signed-off-by: Baoyou Xie
---
MAINTAINERS | 2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 5fb9b62..edfdea3 100644
---
This patch adds dt-binding documentation for zx2967 family thermal sensor.
Signed-off-by: Baoyou Xie
Acked-by: Rob Herring
Reviewed-by: Shawn Guo
---
.../devicetree/bindings/thermal/zx2967-thermal.txt | 116 +
1 file changed, 116 insertions(+)
create mode 100644
Add the zx2967 thermal drivers as maintained by ARM ZTE
architecture maintainers, as they're parts of the core IP.
Signed-off-by: Baoyou Xie
---
MAINTAINERS | 2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 5fb9b62..edfdea3 100644
--- a/MAINTAINERS
+++
The OF graph API leaves too much of the graph walking to clients when
in many cases the driver doesn't care about accessing the port or
endpoint nodes. The drivers typically just want the device connected via
a particular graph connection. of_graph_get_remote_node provides this
functionality.
The OF graph API leaves too much of the graph walking to clients when
in many cases the driver doesn't care about accessing the port or
endpoint nodes. The drivers typically just want the device connected via
a particular graph connection. of_graph_get_remote_node provides this
functionality.
The OMAP driver has its own OF graph helpers that are similar to the
common helpers. This commit replaces most of the calls with the common
helpers. There's still a couple of custom helpers left, but the driver
needs more extensive changes to get rid of them.
In dss_init_ports, we invert the
The OMAP driver has its own OF graph helpers that are similar to the
common helpers. This commit replaces most of the calls with the common
helpers. There's still a couple of custom helpers left, but the driver
needs more extensive changes to get rid of them.
In dss_init_ports, we invert the
Similar to the previous commit, convert drivers open coding OF graph
parsing to use drm_of_find_panel_or_bridge instead.
This changes some error messages to debug messages (in the graph core).
Graph connections are often "no connects" depending on the particular
board, so we want to avoid
Many drivers have a common pattern of searching the OF graph for either an
attached panel or bridge and then finding the DRM struct for the panel
or bridge. Also, most drivers need to handle deferred probing when the
DRM device is not yet instantiated. Create a common function,
Convert drivers to use the new of_graph_get_remote_node() helper
instead of parsing the endpoint node and then getting the remote device
node. Now drivers can just specify the device node and which
port/endpoint and get back the connected remote device node. The details
of the graph binding are
I've been unhappy with the OF graph API for some time and decided to
do something about it. The problem is drivers have to do too much of the
graph parsing and walking themselves. This has led to the same pattern
duplicated over and over. This series adds 2 new helpers and adapts DRM
drivers
Many drivers have a common pattern of searching the OF graph for either an
attached panel or bridge and then finding the DRM struct for the panel
or bridge. Also, most drivers need to handle deferred probing when the
DRM device is not yet instantiated. Create a common function,
Convert drivers to use the new of_graph_get_remote_node() helper
instead of parsing the endpoint node and then getting the remote device
node. Now drivers can just specify the device node and which
port/endpoint and get back the connected remote device node. The details
of the graph binding are
I've been unhappy with the OF graph API for some time and decided to
do something about it. The problem is drivers have to do too much of the
graph parsing and walking themselves. This has led to the same pattern
duplicated over and over. This series adds 2 new helpers and adapts DRM
drivers
Similar to the previous commit, convert drivers open coding OF graph
parsing to use drm_of_find_panel_or_bridge instead.
This changes some error messages to debug messages (in the graph core).
Graph connections are often "no connects" depending on the particular
board, so we want to avoid
right, thanks.
On 2017/2/3 23:33, Matthew Wilcox wrote:
On Fri, Feb 03, 2017 at 04:42:27PM +0800, zhouxianr...@huawei.com wrote:
+static inline void zram_fill_page_partial(char *ptr, unsigned int size,
+ unsigned long value)
+{
+ int i;
+ unsigned long *page;
+
+
right, thanks.
On 2017/2/3 23:33, Matthew Wilcox wrote:
On Fri, Feb 03, 2017 at 04:42:27PM +0800, zhouxianr...@huawei.com wrote:
+static inline void zram_fill_page_partial(char *ptr, unsigned int size,
+ unsigned long value)
+{
+ int i;
+ unsigned long *page;
+
+
On Sat, Feb 04, 2017 at 10:41:20AM +0800, kbuild test robot wrote:
> Hi Derek,
>
> [auto build test ERROR on staging/staging-testing]
> [also build test ERROR on v4.10-rc6 next-20170203]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help
On Sat, Feb 04, 2017 at 10:41:20AM +0800, kbuild test robot wrote:
> Hi Derek,
>
> [auto build test ERROR on staging/staging-testing]
> [also build test ERROR on v4.10-rc6 next-20170203]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help
On February 04, 2017 4:32 AM Mel Gorman wrote:
>
> Hillf Danton pointed out that since commit 1d82de618dd ("mm, vmscan:
> make kswapd reclaim in terms of nodes") that PGDAT_WRITEBACK is no longer
> cleared. It was not noticed as triggering it requires pages under writeback
> to cycle twice
On February 04, 2017 4:32 AM Mel Gorman wrote:
>
> Hillf Danton pointed out that since commit 1d82de618dd ("mm, vmscan:
> make kswapd reclaim in terms of nodes") that PGDAT_WRITEBACK is no longer
> cleared. It was not noticed as triggering it requires pages under writeback
> to cycle twice
On Thu, Feb 02, 2017 at 09:51:25AM +, Al Viro wrote:
> * fuse_copy_fill(). I'm not at all sure that iov_iter_get_pages()
> is a good idea there - fuse_copy_do() could bloody well just use
> copy_{to,from}_iter().
Miklos, could you explain why does lock_request() prohibit page faults
On Thu, Feb 02, 2017 at 09:51:25AM +, Al Viro wrote:
> * fuse_copy_fill(). I'm not at all sure that iov_iter_get_pages()
> is a good idea there - fuse_copy_do() could bloody well just use
> copy_{to,from}_iter().
Miklos, could you explain why does lock_request() prohibit page faults
Hi Derek,
[auto build test ERROR on staging/staging-testing]
[also build test ERROR on v4.10-rc6 next-20170203]
[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/Derek-Robson/Drivers-staging
Hi Derek,
[auto build test ERROR on staging/staging-testing]
[also build test ERROR on v4.10-rc6 next-20170203]
[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/Derek-Robson/Drivers-staging
On 02/03/2017 10:20 AM, Vivien Didelot wrote:
> Simplify the code handling the slave netdevice notifier call by
> providing a dsa_slave_changeupper helper for NETDEV_CHANGEUPPER, and so
> on (only this event is supported at the moment.)
>
> Return NOTIFY_DONE when we did not care about an
On 02/03/2017 10:20 AM, Vivien Didelot wrote:
> Simplify the code handling the slave netdevice notifier call by
> providing a dsa_slave_changeupper helper for NETDEV_CHANGEUPPER, and so
> on (only this event is supported at the moment.)
>
> Return NOTIFY_DONE when we did not care about an
Hi Derek,
[auto build test ERROR on staging/staging-testing]
[also build test ERROR on v4.10-rc6 next-20170203]
[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/Derek-Robson/Drivers-staging
Hi Derek,
[auto build test ERROR on staging/staging-testing]
[also build test ERROR on v4.10-rc6 next-20170203]
[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/Derek-Robson/Drivers-staging
Hi
On Thu, Feb 2, 2017 at 3:38 PM, Douglas Anderson wrote:
> The Sharp lq123p1jx31 has a requirement that the VDD is on for at
> least 300 ms before being turned off. At the moment nothing anywhere
> in the kernel is ensuring this.
>
> The simplest way to ensure this is
Hi
On Thu, Feb 2, 2017 at 3:38 PM, Douglas Anderson wrote:
> The Sharp lq123p1jx31 has a requirement that the VDD is on for at
> least 300 ms before being turned off. At the moment nothing anywhere
> in the kernel is ensuring this.
>
> The simplest way to ensure this is to add a "disable"
This adds a file in i915's debugfs directory that allows userspace to
manually control HPD storm detection. This is mainly for hotplugging
tests, where we might want to test HPD storm functionality or disable
storm detection to speed up hotplugging tests without breaking anything.
Signed-off-by:
This adds a file in i915's debugfs directory that allows userspace to
manually control HPD storm detection. This is mainly for hotplugging
tests, where we might want to test HPD storm functionality or disable
storm detection to speed up hotplugging tests without breaking anything.
Signed-off-by:
Hi Vlastimil,
[auto build test WARNING on mmotm/master]
[also build test WARNING on v4.10-rc6]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Vlastimil,
[auto build test WARNING on mmotm/master]
[also build test WARNING on v4.10-rc6]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On 02/03/2017 01:39 PM, Jon Mason wrote:
> From: Joey Zhong
>
> Implements suspend/resume, external phy 54810 is assumed
> to remain powered up during deep-sleep for wake-on-lane.
s/wake-on-lane/Wake-on-LAN, are you positive phy_stop() is not
suspending the PHY and issuing
On 02/03/2017 01:39 PM, Jon Mason wrote:
> From: Joey Zhong
>
> Implements suspend/resume, external phy 54810 is assumed
> to remain powered up during deep-sleep for wake-on-lane.
s/wake-on-lane/Wake-on-LAN, are you positive phy_stop() is not
suspending the PHY and issuing BMCR_PWRDOWN write?
Hi Laurent,
On 04/02/17 01:22, Laurent Vivier wrote:
Le 03/02/2017 à 16:17, Waldemar Brodkorb a écrit :
[snip]
Btw: Laurent, are you m68k with mmu support are going to be included
upstream? I always carry an old binary for any m68k with mmu testing.
I'm working to have the FPU included for
Hi Laurent,
On 04/02/17 01:22, Laurent Vivier wrote:
Le 03/02/2017 à 16:17, Waldemar Brodkorb a écrit :
[snip]
Btw: Laurent, are you m68k with mmu support are going to be included
upstream? I always carry an old binary for any m68k with mmu testing.
I'm working to have the FPU included for
On Sat, Feb 4, 2017 at 2:52 AM, Andy Lutomirski wrote:
> On Fri, Feb 3, 2017 at 8:42 AM, Hoeun Ryu wrote:
>> On Sat, Feb 4, 2017 at 12:39 AM, Michal Hocko wrote:
>>> On Sat 04-02-17 00:30:05, Hoeun Ryu wrote:
Using virtually
On Sat, Feb 4, 2017 at 2:52 AM, Andy Lutomirski wrote:
> On Fri, Feb 3, 2017 at 8:42 AM, Hoeun Ryu wrote:
>> On Sat, Feb 4, 2017 at 12:39 AM, Michal Hocko wrote:
>>> On Sat 04-02-17 00:30:05, Hoeun Ryu wrote:
Using virtually mapped stack, kernel stacks are allocated via vmalloc.
In
1 - 100 of 1432 matches
Mail list logo