Hi Linus,
Could you please pull this request?
Thanks,
The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:
Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git
Hi Linus,
Could you please pull this request?
Thanks,
The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:
Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git
On 07/19/2017 07:45 PM, yanjiang@windriver.com wrote:
From: Yanjiang Jin
Without this patch we couldn't change the timeout value of imx2_wdt.
Signed-off-by: Yanjiang Jin
---
drivers/watchdog/imx2_wdt.c | 3 +++
1 file changed, 3
On 07/19/2017 07:45 PM, yanjiang@windriver.com wrote:
From: Yanjiang Jin
Without this patch we couldn't change the timeout value of imx2_wdt.
Signed-off-by: Yanjiang Jin
---
drivers/watchdog/imx2_wdt.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/watchdog/imx2_wdt.c
On Wed, 2017-07-19 at 18:05 -0700, Joe Perches wrote:
> On Wed, 2017-07-19 at 17:08 -0700, Linus Torvalds wrote:
> > (b) we could split this thing up some sane way.
> >
> > Anybody got any ideas?
[]
> Just for ease of manipulation and not breaking the script much,
> I'd suggest just having a
On Wed, 2017-07-19 at 18:05 -0700, Joe Perches wrote:
> On Wed, 2017-07-19 at 17:08 -0700, Linus Torvalds wrote:
> > (b) we could split this thing up some sane way.
> >
> > Anybody got any ideas?
[]
> Just for ease of manipulation and not breaking the script much,
> I'd suggest just having a
Hi, Matthias
just a gentle ping on this
Sean
On Wed, 2017-06-21 at 15:49 +0800, sean.w...@mediatek.com wrote:
> From: Sean Wang
>
> Fixed binding violation and also updated related binding documentation to
> reflect the reset signals the MediaTek Ethernet
Hi, Matthias
just a gentle ping on this
Sean
On Wed, 2017-06-21 at 15:49 +0800, sean.w...@mediatek.com wrote:
> From: Sean Wang
>
> Fixed binding violation and also updated related binding documentation to
> reflect the reset signals the MediaTek Ethernet requires.
>
> Sean Wang
Hi, Matthias
just a gentle ping on this
Sean
On Sat, 2017-06-17 at 01:06 +0800, sean.w...@mediatek.com wrote:
> From: Sean Wang
>
> Changes since v4:
> - redefine the two dummy clocks with the correct frequency
> which is 25MHz and 280MHz respectively.
>
>
Hi, Matthias
just a gentle ping on this
Sean
On Sat, 2017-06-17 at 01:06 +0800, sean.w...@mediatek.com wrote:
> From: Sean Wang
>
> Changes since v4:
> - redefine the two dummy clocks with the correct frequency
> which is 25MHz and 280MHz respectively.
>
> Changes since v3:
> -
://github.com/0day-ci/linux/commits/Robin-Murphy/Optimise-64-bit-IOVA-allocations/20170719-060847
> base: https://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git next
> config: arm-multi_v7_defconfig (attached as .config)
> compiler: arm-linux-gnueabi-gcc (Debian 6.1.1-9) 6.1.1
://github.com/0day-ci/linux/commits/Robin-Murphy/Optimise-64-bit-IOVA-allocations/20170719-060847
> base: https://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git next
> config: arm-multi_v7_defconfig (attached as .config)
> compiler: arm-linux-gnueabi-gcc (Debian 6.1.1-9) 6.1.1
On 19 Jul 2017, at 16:59, Andrew Morton wrote:
On Wed, 19 Jul 2017 14:39:43 -0400 "Zi Yan"
wrote:
On 19 Jul 2017, at 4:04, kbuild test robot wrote:
Hi Zi,
[auto build test WARNING on mmotm/master]
[also build test WARNING on v4.13-rc1 next-20170718]
[if your patch
On 19 Jul 2017, at 16:59, Andrew Morton wrote:
On Wed, 19 Jul 2017 14:39:43 -0400 "Zi Yan"
wrote:
On 19 Jul 2017, at 4:04, kbuild test robot wrote:
Hi Zi,
[auto build test WARNING on mmotm/master]
[also build test WARNING on v4.13-rc1 next-20170718]
[if your patch is applied to the wrong
From: Yanjiang Jin
Without this patch we couldn't change the timeout value of imx2_wdt.
Signed-off-by: Yanjiang Jin
---
drivers/watchdog/imx2_wdt.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/watchdog/imx2_wdt.c
From: Yanjiang Jin
Without this patch we couldn't change the timeout value of imx2_wdt.
Signed-off-by: Yanjiang Jin
---
drivers/watchdog/imx2_wdt.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/watchdog/imx2_wdt.c b/drivers/watchdog/imx2_wdt.c
index 4874b0f..6cfeee6 100644
From: Fabio Estevam
eeprom_93xx46_platform_data struct has a 'struct gpio_desc'
type member, so it is better to include ,
which provides 'struct gpio_desc' type.
Signed-off-by: Fabio Estevam
---
Changes since v1:
- None
From: Fabio Estevam
eeprom_93xx46_platform_data struct has a 'struct gpio_desc'
type member, so it is better to include ,
which provides 'struct gpio_desc' type.
Signed-off-by: Fabio Estevam
---
Changes since v1:
- None
include/linux/eeprom_93xx46.h | 3 +--
1 file changed, 1 insertion(+), 2
Signed-off-by: Mark Yao
---
Changes in v5:
- clean document commit title
- move changes description out of docummit commit msg
Changes in v2:
- rename rk322x to rk3228
- correct some vop registers define
Signed-off-by: Mark Yao
---
Changes in v5:
- clean document commit title
- move changes description out of docummit commit msg
Changes in v2:
- rename rk322x to rk3228
- correct some vop registers define
Documentation/devicetree/bindings/display/rockchip/rockchip-vop.txt | 4
1 file
Vop Full framework now has following vops:
IP versionchipname
3.1 rk3288
3.2 rk3368
3.4 rk3366
3.5 rk3399 big
3.6 rk3399 lit
3.7 rk3228
3.8 rk3328
The above IP version is from H/W define, some of vop support
Grouping the vop registers facilitates make register
definition clearer, and also is useful for different vop
reuse the same group register.
Signed-off-by: Mark Yao
---
drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 99 +-
From: Fabio Estevam
Commit 3ca9b1ac28398c ("misc: eeprom_93xx46: Add support for a GPIO
'select' line.") introduced the optional usage of 'select-gpios'
by using the gpiod API in a convoluted way.
Rewrite the gpiod handling to make the code simpler.
Signed-off-by: Fabio
Grouping the vop registers facilitates make register
definition clearer, and also is useful for different vop
reuse the same group register.
Signed-off-by: Mark Yao
---
drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 99 +-
drivers/gpu/drm/rockchip/rockchip_drm_vop.h |
From: Fabio Estevam
Commit 3ca9b1ac28398c ("misc: eeprom_93xx46: Add support for a GPIO
'select' line.") introduced the optional usage of 'select-gpios'
by using the gpiod API in a convoluted way.
Rewrite the gpiod handling to make the code simpler.
Signed-off-by: Fabio Estevam
---
Changes
Vop Full framework now has following vops:
IP versionchipname
3.1 rk3288
3.2 rk3368
3.4 rk3366
3.5 rk3399 big
3.6 rk3399 lit
3.7 rk3228
3.8 rk3328
The above IP version is from H/W define, some of vop support
Since the drm atomic framework, only a small part of the vop
register needs sync write, Currently seems only following registers
need sync write:
cfg_done, standby and interrupt related register.
All ctrl registers are using the sync write method that is
inefficient, hardcode the write_relaxed
In the hardware design process, the design of line flags
register is associated with the interrupt register,
placing the line flags in the interrupt definition is
more reasonable, and it would make multi-vop define easilier.
Changes in v3:
- Explain more in details, introduce why we need this
It's a hardware bug, all window's overlay channel reset
value is same, hardware overlay would be die.
so we must initial difference id for each overlay channel.
The Channel register is supported on all vop will full design.
Following is the details for this register
VOP_WIN0_CTRL2
bit[7:4]
Since the drm atomic framework, only a small part of the vop
register needs sync write, Currently seems only following registers
need sync write:
cfg_done, standby and interrupt related register.
All ctrl registers are using the sync write method that is
inefficient, hardcode the write_relaxed
In the hardware design process, the design of line flags
register is associated with the interrupt register,
placing the line flags in the interrupt definition is
more reasonable, and it would make multi-vop define easilier.
Changes in v3:
- Explain more in details, introduce why we need this
It's a hardware bug, all window's overlay channel reset
value is same, hardware overlay would be die.
so we must initial difference id for each overlay channel.
The Channel register is supported on all vop will full design.
Following is the details for this register
VOP_WIN0_CTRL2
bit[7:4]
These patches try to make all current rockchip full framework vop works
on drm, fill missing vop on full framework.
Vop Full framework now has following vops:
IP versionchipname
3.1 rk3288
3.2 rk3368
3.4 rk3366
3.5 rk3399 big
These patches try to make all current rockchip full framework vop works
on drm, fill missing vop on full framework.
Vop Full framework now has following vops:
IP versionchipname
3.1 rk3288
3.2 rk3368
3.4 rk3366
3.5 rk3399 big
At present we are using init_table to initialize some
registers, but the Register init table use un-document define,
it is unreadable, and sometimes we only want to update tiny
bits, init table method is not friendly, it's diffcult to
reuse for difference chips.
To make it clean, initialize
At present we are using init_table to initialize some
registers, but the Register init table use un-document define,
it is unreadable, and sometimes we only want to update tiny
bits, init table method is not friendly, it's diffcult to
reuse for difference chips.
To make it clean, initialize
Hi Viresh,
On Tue, Jul 18, 2017 at 11:19 PM, Viresh Kumar wrote:
> On 18-07-17, 21:39, Joel Fernandes wrote:
>> Not really, to me B will still work because in the case the flag is
>> set, we are correctly double boosting in the next cycle.
>>
>> Taking an example, with B
Hi Viresh,
On Tue, Jul 18, 2017 at 11:19 PM, Viresh Kumar wrote:
> On 18-07-17, 21:39, Joel Fernandes wrote:
>> Not really, to me B will still work because in the case the flag is
>> set, we are correctly double boosting in the next cycle.
>>
>> Taking an example, with B = flag is set and D =
From: Fabio Estevam
eeprom_93xx46_platform_data struct has a 'struct gpio_desc'
type member, so it is better to include ,
which provides 'struct gpio_desc' type.
Signed-off-by: Fabio Estevam
---
include/linux/eeprom_93xx46.h | 3 +--
1 file
From: Fabio Estevam
eeprom_93xx46_platform_data struct has a 'struct gpio_desc'
type member, so it is better to include ,
which provides 'struct gpio_desc' type.
Signed-off-by: Fabio Estevam
---
include/linux/eeprom_93xx46.h | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
On 07/19/2017 06:44 PM, Zhaoyang Huang wrote:
> /proc/vmallocinfo will not show the area allocated by vm_map_ram, which
> will make confusion when debug. Add vm_struct for them and show them in
> proc.
>
> Signed-off-by: Zhaoyang Huang
> ---
another patch titled
On 07/19/2017 06:44 PM, Zhaoyang Huang wrote:
> /proc/vmallocinfo will not show the area allocated by vm_map_ram, which
> will make confusion when debug. Add vm_struct for them and show them in
> proc.
>
> Signed-off-by: Zhaoyang Huang
> ---
another patch titled "vmalloc: show lazy-purged vma
From: Fabio Estevam
Commit 3ca9b1ac28398c ("misc: eeprom_93xx46: Add support for a GPIO
'select' line.") introduced the optional usage of 'select-gpios'
by using the gpiod API in a convoluted way.
Rewrite the gpiod handling to make the code simpler.
Signed-off-by: Fabio
From: Fabio Estevam
Commit 3ca9b1ac28398c ("misc: eeprom_93xx46: Add support for a GPIO
'select' line.") introduced the optional usage of 'select-gpios'
by using the gpiod API in a convoluted way.
Rewrite the gpiod handling to make the code simpler.
Signed-off-by: Fabio Estevam
---
Hi Jim,
2017-07-19 2:47 GMT+08:00 Jim Mattson :
> Why do we expect the VM_EXIT_INTR_INFO and EXIT_QUALIFICATION fields
> of the VMCS to have the correct values for the injected exception?
Good point, I think we should synthesize VM_EXIT_INTR_INFO and
EXIT_QUALIFICATION
Hi Jim,
2017-07-19 2:47 GMT+08:00 Jim Mattson :
> Why do we expect the VM_EXIT_INTR_INFO and EXIT_QUALIFICATION fields
> of the VMCS to have the correct values for the injected exception?
Good point, I think we should synthesize VM_EXIT_INTR_INFO and
EXIT_QUALIFICATION manually, I will post a
在 2017-07-20 10:03,icen...@aosc.io 写道:
在 2017-07-20 06:59,Ondřej Jirman 写道:
Hi,
Icenowy Zheng píše v Út 04. 04. 2017 v 17:50 +0800:
From: Icenowy Zheng
Now we have driver for the PRCM CCU, switch to use it instead of
old-style clock nodes for apb0-related clocks in
在 2017-07-20 10:03,icen...@aosc.io 写道:
在 2017-07-20 06:59,Ondřej Jirman 写道:
Hi,
Icenowy Zheng píše v Út 04. 04. 2017 v 17:50 +0800:
From: Icenowy Zheng
Now we have driver for the PRCM CCU, switch to use it instead of
old-style clock nodes for apb0-related clocks in sunxi-h3-h5.dtsi .
The
On Wed, 2017-07-19 at 14:50 +0200, Greg KH wrote:
> From: Greg Kroah-Hartman
>
> It's better to use the DRIVER_ATTR_RW() and DRIVER_ATTR_RO() macros to
> explicitly show that this is a read/write or read/only sysfs file. So
> convert the remaining SCSI drivers that
On Wed, 2017-07-19 at 14:50 +0200, Greg KH wrote:
> From: Greg Kroah-Hartman
>
> It's better to use the DRIVER_ATTR_RW() and DRIVER_ATTR_RO() macros to
> explicitly show that this is a read/write or read/only sysfs file. So
> convert the remaining SCSI drivers that use the old style to use the
On 2017年07月18日 01:24, Rob Herring wrote:
On Wed, Jul 12, 2017 at 10:04:02AM +0800, Mark Yao wrote:
Changes in v2:
- rename rk322x to rk3228(Heiko Stübner)
This goes below '---' and you need a commit msg here. Also, it is not
clear in the subject this is for Rockchip.
Got it, will fix it at
On 2017年07月18日 01:24, Rob Herring wrote:
On Wed, Jul 12, 2017 at 10:04:02AM +0800, Mark Yao wrote:
Changes in v2:
- rename rk322x to rk3228(Heiko Stübner)
This goes below '---' and you need a commit msg here. Also, it is not
clear in the subject this is for Rockchip.
Got it, will fix it at
The additional arguments in the internal __rproc_boot() function
were dropped in commit 2bfc311a57f5 ("remoteproc: Drop wait in
__rproc_boot()"). The exported rproc_boot() is now just a wrapper
around this internal function, so merge them together.
Signed-off-by: Suman Anna
---
The additional arguments in the internal __rproc_boot() function
were dropped in commit 2bfc311a57f5 ("remoteproc: Drop wait in
__rproc_boot()"). The exported rproc_boot() is now just a wrapper
around this internal function, so merge them together.
Signed-off-by: Suman Anna
---
在 2017-07-20 06:59,Ondřej Jirman 写道:
Hi,
Icenowy Zheng píše v Út 04. 04. 2017 v 17:50 +0800:
From: Icenowy Zheng
Now we have driver for the PRCM CCU, switch to use it instead of
old-style clock nodes for apb0-related clocks in sunxi-h3-h5.dtsi .
The mux 3 of R_CCU is still
Commit 8a228ecfe086b ("rpmsg: Indirection table for rpmsg_endpoint
operations") has made the rpmsg_send_offchannel_raw() a static
function and local to the virtio_rpmsg_bus module, but has not
dropped the corresponding EXPORT_SYMBOL. Fix this.
Signed-off-by: Suman Anna
---
在 2017-07-20 06:59,Ondřej Jirman 写道:
Hi,
Icenowy Zheng píše v Út 04. 04. 2017 v 17:50 +0800:
From: Icenowy Zheng
Now we have driver for the PRCM CCU, switch to use it instead of
old-style clock nodes for apb0-related clocks in sunxi-h3-h5.dtsi .
The mux 3 of R_CCU is still the internal
Commit 8a228ecfe086b ("rpmsg: Indirection table for rpmsg_endpoint
operations") has made the rpmsg_send_offchannel_raw() a static
function and local to the virtio_rpmsg_bus module, but has not
dropped the corresponding EXPORT_SYMBOL. Fix this.
Signed-off-by: Suman Anna
---
On 2017/7/19 15:55, Thomas Gleixner wrote:
> On Wed, 19 Jul 2017, Li, Aubrey wrote:
>> On 2017/7/18 15:19, Thomas Gleixner wrote:
>>> You can very well avoid it by taking the irq timings or whatever other
>>> information into account for the NOHZ decision.
>>>
>> If I read the source correctly,
On 2017/7/19 15:55, Thomas Gleixner wrote:
> On Wed, 19 Jul 2017, Li, Aubrey wrote:
>> On 2017/7/18 15:19, Thomas Gleixner wrote:
>>> You can very well avoid it by taking the irq timings or whatever other
>>> information into account for the NOHZ decision.
>>>
>> If I read the source correctly,
On Mon, 10 Jul 2017, Michal Hocko wrote:
> From: Michal Hocko
>
> Tetsuo Handa has reported [1][2][3]that direct reclaimers might get stuck
> in too_many_isolated loop basically for ever because the last few pages
> on the LRU lists are isolated by the kswapd which is stuck on
On Mon, 10 Jul 2017, Michal Hocko wrote:
> From: Michal Hocko
>
> Tetsuo Handa has reported [1][2][3]that direct reclaimers might get stuck
> in too_many_isolated loop basically for ever because the last few pages
> on the LRU lists are isolated by the kswapd which is stuck on fs locks
> when
From: Rafael J. Wysocki
Commit eed4d47efe95 (ACPI / sleep: Ignore spurious SCI wakeups from
suspend-to-idle) introduced acpi_freeze_sync() whose purpose is to
flush all of the processing of possible wakeup events signaled via
the ACPI SCI. However, it doesn't flush
From: Rafael J. Wysocki
Commit eed4d47efe95 (ACPI / sleep: Ignore spurious SCI wakeups from
suspend-to-idle) introduced acpi_freeze_sync() whose purpose is to
flush all of the processing of possible wakeup events signaled via
the ACPI SCI. However, it doesn't flush the query workqueue used
by
From: Rafael J. Wysocki
Regardless of whether or not debug messages from the core system
suspend/hibernation code are enabled, it is useful to know when
system-wide transitions start and finish (or fail), so print "info"
messages at these points.
Signed-off-by:
From: Rafael J. Wysocki
Regardless of whether or not debug messages from the core system
suspend/hibernation code are enabled, it is useful to know when
system-wide transitions start and finish (or fail), so print "info"
messages at these points.
Signed-off-by: Rafael J. Wysocki
---
-> v2:
FYI, we noticed the following commit:
commit: 6974f0c4555e285ab217cee58b6e874f776ff409 ("include/linux/string.h: add
the option of fortified string.h functions")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
in testcase: boot
on test machine: qemu-system-i386
FYI, we noticed the following commit:
commit: 6974f0c4555e285ab217cee58b6e874f776ff409 ("include/linux/string.h: add
the option of fortified string.h functions")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
in testcase: boot
on test machine: qemu-system-i386
Fix an error detected by checkpatch.pl on line 75 and move the opening
brace after the function signature to a new line.
Signed-off-by: Munir Contractor
---
drivers/staging/rtl8188eu/include/rtw_ioctl.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff
Fix an error detected by checkpatch.pl on line 75 and move the opening
brace after the function signature to a new line.
Signed-off-by: Munir Contractor
---
drivers/staging/rtl8188eu/include/rtw_ioctl.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
On 2017/7/19 22:48, Paul E. McKenney wrote:
> On Wed, Jul 19, 2017 at 01:44:06PM +0800, Li, Aubrey wrote:
>> On 2017/7/18 23:20, Paul E. McKenney wrote:
>>
2) for rcu idle enter/exit, I measured the details which Paul provided, and
the result matches with what I have measured before,
On 2017/7/19 22:48, Paul E. McKenney wrote:
> On Wed, Jul 19, 2017 at 01:44:06PM +0800, Li, Aubrey wrote:
>> On 2017/7/18 23:20, Paul E. McKenney wrote:
>>
2) for rcu idle enter/exit, I measured the details which Paul provided, and
the result matches with what I have measured before,
On Wed, Jul 19, 2017 at 5:19 PM, Paul Moore wrote:
> On Wed, Jul 19, 2017 at 8:03 PM, Paul Moore wrote:
>> On Tue, Jul 18, 2017 at 6:25 PM, Kees Cook wrote:
>>> The SELinux bprm_secureexec hook can be merged with the
On Wed, Jul 19, 2017 at 5:19 PM, Paul Moore wrote:
> On Wed, Jul 19, 2017 at 8:03 PM, Paul Moore wrote:
>> On Tue, Jul 18, 2017 at 6:25 PM, Kees Cook wrote:
>>> The SELinux bprm_secureexec hook can be merged with the bprm_set_creds
>>> hook since it's dealing with the same information, and all
From: Frank Rowand
Update the cpp include flags for compiling device tree dts files
to match the changes made to the kernel build process in
commit d5d332d3f7e8 ("devicetree: Move include prefixes from arch
to separate directory").
Cc: # 4.12
From: Frank Rowand
Update the cpp include flags for compiling device tree dts files
to match the changes made to the kernel build process in
commit d5d332d3f7e8 ("devicetree: Move include prefixes from arch
to separate directory").
Cc: # 4.12
Signed-off-by: Frank Rowand
---
On Wed, Jul 19, 2017 at 02:56:02PM -0700, Paul E. McKenney wrote:
> On Thu, Jul 20, 2017 at 06:33:26AM +0900, Akira Yokosawa wrote:
> > On 2017/07/20 2:43, Paul E. McKenney wrote:
> > > On Mon, Jul 17, 2017 at 05:24:42PM +0900, Akira Yokosawa wrote:
> > >> >From
On Wed, Jul 19, 2017 at 02:56:02PM -0700, Paul E. McKenney wrote:
> On Thu, Jul 20, 2017 at 06:33:26AM +0900, Akira Yokosawa wrote:
> > On 2017/07/20 2:43, Paul E. McKenney wrote:
> > > On Mon, Jul 17, 2017 at 05:24:42PM +0900, Akira Yokosawa wrote:
> > >> >From
On Wed, 2017-07-19 at 11:11 -0700, Guenter Roeck wrote:
> On Thu, Jul 20, 2017 at 12:35:09AM +0930, Joel Stanley wrote:
> > > > On Tue, Jul 18, 2017 at 1:06 PM, Andrew Jeffery wrote:
> > > The driver features fan control and basic dual-tachometer support.
> >
> > Say something
On Wed, 2017-07-19 at 11:11 -0700, Guenter Roeck wrote:
> On Thu, Jul 20, 2017 at 12:35:09AM +0930, Joel Stanley wrote:
> > > > On Tue, Jul 18, 2017 at 1:06 PM, Andrew Jeffery wrote:
> > > The driver features fan control and basic dual-tachometer support.
> >
> > Say something about the
Hi all,
Today's linux-next merge of the drm-misc tree got a conflict in:
drivers/gpu/drm/i915/i915_drv.c
between commit:
99c539bef538 ("drm/i915: unregister interfaces first in unload")
from the drm-intel tree and commit:
baf54385af78 ("drm/i915: Drop drm_vblank_cleanup")
from the
Hi all,
Today's linux-next merge of the drm-misc tree got a conflict in:
drivers/gpu/drm/i915/i915_drv.c
between commit:
99c539bef538 ("drm/i915: unregister interfaces first in unload")
from the drm-intel tree and commit:
baf54385af78 ("drm/i915: Drop drm_vblank_cleanup")
from the
update the comment bellow as ...'s/by one driver's allocating/because
one driver has allocated/'..., sorry
for the confusion
On Thu, Jul 20, 2017 at 9:15 AM, Zhaoyang Huang wrote:
> On Thu, Jul 20, 2017 at 4:50 AM, Andrew Morton
> wrote:
>>
update the comment bellow as ...'s/by one driver's allocating/because
one driver has allocated/'..., sorry
for the confusion
On Thu, Jul 20, 2017 at 9:15 AM, Zhaoyang Huang wrote:
> On Thu, Jul 20, 2017 at 4:50 AM, Andrew Morton
> wrote:
>> On Wed, 19 Jul 2017 18:44:03 +0800 Zhaoyang Huang
On Wed, 19 Jul 2017, Michal Hocko wrote:
> On Thu 29-06-17 10:46:21, Michal Hocko wrote:
> > Forgot to CC Hugh.
> >
> > Hugh, Andrew, do you see this could cause any problem wrt.
> > ksm/khugepaged exit path?
>
> ping. I would really appreciate some help here. I would like to resend
> the patch
On Wed, 19 Jul 2017, Michal Hocko wrote:
> On Thu 29-06-17 10:46:21, Michal Hocko wrote:
> > Forgot to CC Hugh.
> >
> > Hugh, Andrew, do you see this could cause any problem wrt.
> > ksm/khugepaged exit path?
>
> ping. I would really appreciate some help here. I would like to resend
> the patch
Best Regards!
Anson Huang
> -Original Message-
> From: Lucas Stach [mailto:l.st...@pengutronix.de]
> Sent: 2017-07-19 6:28 PM
> To: Leonard Crestez
> Cc: Viresh Kumar ; Rafael J. Wysocki
> ; Shawn Guo
Best Regards!
Anson Huang
> -Original Message-
> From: Lucas Stach [mailto:l.st...@pengutronix.de]
> Sent: 2017-07-19 6:28 PM
> To: Leonard Crestez
> Cc: Viresh Kumar ; Rafael J. Wysocki
> ; Shawn Guo ; Fabio Estevam
> ; linux...@vger.kernel.org; Octavian Purdila
> ; Anson Huang ;
On Thu, Jul 20, 2017 at 4:50 AM, Andrew Morton
wrote:
> On Wed, 19 Jul 2017 18:44:03 +0800 Zhaoyang Huang
> wrote:
>
>> /proc/vmallocinfo will not show the area allocated by vm_map_ram, which
>> will make confusion when debug. Add vm_struct
On Thu, Jul 20, 2017 at 4:50 AM, Andrew Morton
wrote:
> On Wed, 19 Jul 2017 18:44:03 +0800 Zhaoyang Huang
> wrote:
>
>> /proc/vmallocinfo will not show the area allocated by vm_map_ram, which
>> will make confusion when debug. Add vm_struct for them and show them in
>> proc.
>>
>
> Please
On Wed, 2017-07-19 at 17:08 -0700, Linus Torvalds wrote:
> I can easily just look at the reject and fix it, but I don't really
> want to. Why? Because I hate the MAINTAINERS file.
>
> It's the most painful file for merging too, because everybody touches
> it - kind of like the old "one single
On Wed, 2017-07-19 at 17:08 -0700, Linus Torvalds wrote:
> I can easily just look at the reject and fix it, but I don't really
> want to. Why? Because I hate the MAINTAINERS file.
>
> It's the most painful file for merging too, because everybody touches
> it - kind of like the old "one single
On Mon, 2017-06-26 at 15:32 +0300, Paul Kocialkowski wrote:
> After detecting an IRQ storm, hotplug detection will switch from
> irq-based detection to poll-based detection. After a short delay or
> when resetting storm detection from debugfs, detection will switch
> back to being irq-based.
>
>
On Mon, 2017-06-26 at 15:32 +0300, Paul Kocialkowski wrote:
> After detecting an IRQ storm, hotplug detection will switch from
> irq-based detection to poll-based detection. After a short delay or
> when resetting storm detection from debugfs, detection will switch
> back to being irq-based.
>
>
On 07/19/2017 05:53 PM, Linus Torvalds wrote:
> On Wed, Jul 19, 2017 at 5:35 PM, Linus Torvalds
> wrote:
>>
>> Your mailer is crap, and destroys utf-8 characters. In particular:
>>
>> -M: Michał Mirosław
>
> Using
On 07/19/2017 05:53 PM, Linus Torvalds wrote:
> On Wed, Jul 19, 2017 at 5:35 PM, Linus Torvalds
> wrote:
>>
>> Your mailer is crap, and destroys utf-8 characters. In particular:
>>
>> -M: Michał Mirosław
>
> Using pseudo-MIME-encoding, that was actually (before my cut-and-paste
>
FYI, we noticed the following commit:
commit: bff589be59c50924a9715951160578e570cba5c6 ("platform/x86: dell-wmi:
Convert to the WMI bus infrastructure")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
in testcase: boot
on test machine: qemu-system-x86_64 -enable-kvm -m
FYI, we noticed the following commit:
commit: bff589be59c50924a9715951160578e570cba5c6 ("platform/x86: dell-wmi:
Convert to the WMI bus infrastructure")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
in testcase: boot
on test machine: qemu-system-x86_64 -enable-kvm -m
FYI, we noticed the following commit:
commit: df33767d9fe0ca93c606cc9042df05e5045c8158 ("uuid: hoist helpers
uuid_equal() and uuid_copy() from xfs")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
in testcase: boot
on test machine: qemu-system-x86_64 -enable-kvm -m 420M
FYI, we noticed the following commit:
commit: df33767d9fe0ca93c606cc9042df05e5045c8158 ("uuid: hoist helpers
uuid_equal() and uuid_copy() from xfs")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
in testcase: boot
on test machine: qemu-system-x86_64 -enable-kvm -m 420M
201 - 300 of 3020 matches
Mail list logo