Re: [PATCH 08/12] pinctrl: axp209: account for const type of of_device_id.data

On Tue, Jan 2, 2018 at 2:28 PM, Julia Lawall wrote: > The return value of of_device_get_match_data has type const void *. > The desc field of the pctl structure also has a const type, so there > is no need for the const-discarding cast between them. > > Done using

Re: [PATCH 08/12] pinctrl: axp209: account for const type of of_device_id.data

On Tue, Jan 2, 2018 at 2:28 PM, Julia Lawall wrote: > The return value of of_device_get_match_data has type const void *. > The desc field of the pctl structure also has a const type, so there > is no need for the const-discarding cast between them. > > Done using Coccinelle. > > Signed-off-by:

Re: [PATCH] ethernet: mlx4: Delete an error message for a failed memory allocation in five functions

On 01/01/2018 10:46 PM, SF Markus Elfring wrote: From: Markus Elfring Date: Mon, 1 Jan 2018 21:42:27 +0100 Omit an extra message for a memory allocation failure in these functions. This issue was detected by using the Coccinelle software. Signed-off-by:

Re: [PATCH] ethernet: mlx4: Delete an error message for a failed memory allocation in five functions

On 01/01/2018 10:46 PM, SF Markus Elfring wrote: From: Markus Elfring Date: Mon, 1 Jan 2018 21:42:27 +0100 Omit an extra message for a memory allocation failure in these functions. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- Is this an

Re: [PATCH 02/12] pinctrl: at91-pio4: account for const type of of_device_id.data

On Tue, Jan 2, 2018 at 2:27 PM, Julia Lawall wrote: > This driver creates a const structure that it stores in the data field > of an of_device_id array. > > Adding const to the declaration of the location that receives the > const value from the data field ensures that the

Re: [PATCH 02/12] pinctrl: at91-pio4: account for const type of of_device_id.data

On Tue, Jan 2, 2018 at 2:27 PM, Julia Lawall wrote: > This driver creates a const structure that it stores in the data field > of an of_device_id array. > > Adding const to the declaration of the location that receives the > const value from the data field ensures that the compiler will >

Re: [PATCH 16/67] powerpc: rename dma_direct_ to dma_nommu_

Hi Michael, On Wed, Jan 3, 2018 at 7:24 AM, Michael Ellerman wrote: > Geert Uytterhoeven writes: > >> On Tue, Jan 2, 2018 at 10:45 AM, Michael Ellerman >> wrote: >>> Christoph Hellwig writes: >>> We want to use

Re: [PATCH 16/67] powerpc: rename dma_direct_ to dma_nommu_

Hi Michael, On Wed, Jan 3, 2018 at 7:24 AM, Michael Ellerman wrote: > Geert Uytterhoeven writes: > >> On Tue, Jan 2, 2018 at 10:45 AM, Michael Ellerman >> wrote: >>> Christoph Hellwig writes: >>> We want to use the dma_direct_ namespace for a generic implementation, so rename

Re: [PATCH v3 18/27] pinctrl: replace devm_ioremap_nocache with devm_ioremap

On Wed, Jan 3, 2018 at 7:15 AM, Yisheng Xie wrote: > On 2018/1/2 16:43, Linus Walleij wrote: >> On Sat, Dec 23, 2017 at 12:00 PM, Yisheng Xie wrote: >> >>> Default ioremap is ioremap_nocache, so devm_ioremap has the same >>> function with

Re: [PATCH v3 18/27] pinctrl: replace devm_ioremap_nocache with devm_ioremap

On Wed, Jan 3, 2018 at 7:15 AM, Yisheng Xie wrote: > On 2018/1/2 16:43, Linus Walleij wrote: >> On Sat, Dec 23, 2017 at 12:00 PM, Yisheng Xie wrote: >> >>> Default ioremap is ioremap_nocache, so devm_ioremap has the same >>> function with devm_ioremap_nocache, which can just be killed to >>>

Re: [PATCH v3 06/27] gpio: replace devm_ioremap_nocache with devm_ioremap

On Wed, Jan 3, 2018 at 7:05 AM, Yisheng Xie wrote: > On 2018/1/2 16:41, Linus Walleij wrote: >> On Sat, Dec 23, 2017 at 11:58 AM, Yisheng Xie wrote: >> >>> Default ioremap is ioremap_nocache, so devm_ioremap has the same >>> function with

Re: [PATCH v3 06/27] gpio: replace devm_ioremap_nocache with devm_ioremap

On Wed, Jan 3, 2018 at 7:05 AM, Yisheng Xie wrote: > On 2018/1/2 16:41, Linus Walleij wrote: >> On Sat, Dec 23, 2017 at 11:58 AM, Yisheng Xie wrote: >> >>> Default ioremap is ioremap_nocache, so devm_ioremap has the same >>> function with devm_ioremap_nocache, which can just be killed to >>>

Re: general protection fault in __netlink_ns_capable

On Tue, Jan 02, 2018 at 04:35:11PM -0800, Andrei Vagin wrote: > On Tue, Jan 02, 2018 at 10:58:01AM -0800, syzbot wrote: > > Hello, > > > > syzkaller hit the following crash on > > 75aa5540627fdb3d8f86229776ea87f995275351 > > git://git.cmpxchg.org/linux-mmots.git/master > > compiler: gcc (GCC)

Re: general protection fault in __netlink_ns_capable

On Tue, Jan 02, 2018 at 04:35:11PM -0800, Andrei Vagin wrote: > On Tue, Jan 02, 2018 at 10:58:01AM -0800, syzbot wrote: > > Hello, > > > > syzkaller hit the following crash on > > 75aa5540627fdb3d8f86229776ea87f995275351 > > git://git.cmpxchg.org/linux-mmots.git/master > > compiler: gcc (GCC)

Re: [PATCH v3] f2fs: add an ioctl to disable GC for specific file

On 2018/1/3 11:21, Jaegeuk Kim wrote: > This patch gives a flag to disable GC on given file, which would be useful, > when > user wants to keep its block map. It also conducts in-place-update for > dontmove > file. > > Signed-off-by: Jaegeuk Kim > --- > > Change log from

Re: [PATCH v3] f2fs: add an ioctl to disable GC for specific file

On 2018/1/3 11:21, Jaegeuk Kim wrote: > This patch gives a flag to disable GC on given file, which would be useful, > when > user wants to keep its block map. It also conducts in-place-update for > dontmove > file. > > Signed-off-by: Jaegeuk Kim > --- > > Change log from v2: > - modify ioctl

Re: [PATCH 04/13] powerpc/powernv: Add platform-specific services for opencapi

On 19/12/17 02:21, Frederic Barrat wrote: Implement a few platform-specific calls which can be used by drivers: - provide the Transaction Layer capabilities of the host, so that the driver can find some common ground and configure the device and host appropriately. - provide the hw

Re: [PATCH 04/13] powerpc/powernv: Add platform-specific services for opencapi

On 19/12/17 02:21, Frederic Barrat wrote: Implement a few platform-specific calls which can be used by drivers: - provide the Transaction Layer capabilities of the host, so that the driver can find some common ground and configure the device and host appropriately. - provide the hw

Re: [PATCH 06/13] ocxl: Driver code for 'generic' opencapi devices

On 19/12/17 02:21, Frederic Barrat wrote: Add an ocxl driver to handle generic opencapi devices. Of course, it's not meant to be the only opencapi driver, any device is free to implement its own. But if a host application only needs basic services like attaching to an opencapi adapter, have

Re: [PATCH 06/13] ocxl: Driver code for 'generic' opencapi devices

On 19/12/17 02:21, Frederic Barrat wrote: Add an ocxl driver to handle generic opencapi devices. Of course, it's not meant to be the only opencapi driver, any device is free to implement its own. But if a host application only needs basic services like attaching to an opencapi adapter, have

[PATCHv4 1/2] capability: introduce sysctl for controlled user-ns capability whitelist

From: Mahesh Bandewar Add a sysctl variable kernel.controlled_userns_caps_whitelist. Capability mask is stored in kernel as kernel_cap_t type (array of u32). This sysctl takes input as comma separated hex u32 words. For simplicity one could see this sysctl to operate on

[PATCHv4 2/2] userns: control capabilities of some user namespaces

From: Mahesh Bandewar With this new notion of "controlled" user-namespaces, the controlled user-namespaces are marked at the time of their creation while the capabilities of processes that belong to them are controlled using the global mask. Init-user-ns is always

[PATCHv4 1/2] capability: introduce sysctl for controlled user-ns capability whitelist

From: Mahesh Bandewar Add a sysctl variable kernel.controlled_userns_caps_whitelist. Capability mask is stored in kernel as kernel_cap_t type (array of u32). This sysctl takes input as comma separated hex u32 words. For simplicity one could see this sysctl to operate on string inputs. However

[PATCHv4 2/2] userns: control capabilities of some user namespaces

From: Mahesh Bandewar With this new notion of "controlled" user-namespaces, the controlled user-namespaces are marked at the time of their creation while the capabilities of processes that belong to them are controlled using the global mask. Init-user-ns is always uncontrolled and a process

[PATCHv4 0/2] capability controlled user-namespaces

From: Mahesh Bandewar TL;DR version - Creating a sandbox environment with namespaces is challenging considering what these sandboxed processes can engage into. e.g. CVE-2017-6074, CVE-2017-7184, CVE-2017-7308 etc. just to name few. Current form of user-namespaces,

[PATCHv4 0/2] capability controlled user-namespaces

From: Mahesh Bandewar TL;DR version - Creating a sandbox environment with namespaces is challenging considering what these sandboxed processes can engage into. e.g. CVE-2017-6074, CVE-2017-7184, CVE-2017-7308 etc. just to name few. Current form of user-namespaces, however, if changed

Re: [PATCH V8 0/3] OPP: Allow OPP table to be used for power-domains

On 18-12-17, 15:51, Viresh Kumar wrote: > Hi, > > Now that the performance state of PM domains are supported by the kernel > (merged in linux-next), I am trying once again to define the bindings > which we dropped until the code is merged first. > > Summary: > > Power-domains can also have

Re: [PATCH V8 0/3] OPP: Allow OPP table to be used for power-domains

On 18-12-17, 15:51, Viresh Kumar wrote: > Hi, > > Now that the performance state of PM domains are supported by the kernel > (merged in linux-next), I am trying once again to define the bindings > which we dropped until the code is merged first. > > Summary: > > Power-domains can also have

Re: [Intel-gfx] [PATCH v2] drm/i915: Try EDID bitbanging on HDMI after failed read

On Tue, 02 Jan 2018, Chris Wilson wrote: > Quoting Rodrigo Vivi (2018-01-02 19:12:18) >> On Sun, Dec 31, 2017 at 10:34:54PM +, Stefan Brüns wrote: >> > + edid = drm_get_edid(connector, i2c); >> > + >> > + if (!edid && !intel_gmbus_is_forced_bit(i2c)) { >> > +

Re: [Intel-gfx] [PATCH v2] drm/i915: Try EDID bitbanging on HDMI after failed read

On Tue, 02 Jan 2018, Chris Wilson wrote: > Quoting Rodrigo Vivi (2018-01-02 19:12:18) >> On Sun, Dec 31, 2017 at 10:34:54PM +, Stefan Brüns wrote: >> > + edid = drm_get_edid(connector, i2c); >> > + >> > + if (!edid && !intel_gmbus_is_forced_bit(i2c)) { >> > +

Re: 4.15-rc6 PTI regression: L1 TLB mismatch MCE on Athlon64

> > These MCE-s do not happen on 4.14 and 4.15.0-rc4-00041-gace52288edf0. > > They do happen on each boot into 4.15-rc6. Will try to bisect. > > Please do. And try -rc5 too. 4.15-rc5 is OK. Will try CONFIG_X86_PTDUMP on the next kernel. > And then Linus' pti merges: > >

Re: 4.15-rc6 PTI regression: L1 TLB mismatch MCE on Athlon64

> > These MCE-s do not happen on 4.14 and 4.15.0-rc4-00041-gace52288edf0. > > They do happen on each boot into 4.15-rc6. Will try to bisect. > > Please do. And try -rc5 too. 4.15-rc5 is OK. Will try CONFIG_X86_PTDUMP on the next kernel. > And then Linus' pti merges: > >

Re: [PATCH] exec: Weaken dumpability for secureexec

On Tue, Jan 02, 2018 at 03:21:33PM -0800, Kees Cook wrote: > This is a logical revert of: > > commit e37fdb785a5f ("exec: Use secureexec for setting dumpability") > > This weakens dumpability back to checking only for uid/gid changes in > current (which is useless), but userspace depends on

Re: [PATCH] exec: Weaken dumpability for secureexec

On Tue, Jan 02, 2018 at 03:21:33PM -0800, Kees Cook wrote: > This is a logical revert of: > > commit e37fdb785a5f ("exec: Use secureexec for setting dumpability") > > This weakens dumpability back to checking only for uid/gid changes in > current (which is useless), but userspace depends on

Re: About the try to remove cross-release feature entirely by Ingo

On Wed, Jan 03, 2018 at 11:10:37AM +0900, Byungchul Park wrote: > > The point I was trying to drive home is that "all we have to do is > > just classify everything well or just invalidate the right lock > > Just to be sure, we don't have to invalidate lock objects at all but > a problematic

Re: About the try to remove cross-release feature entirely by Ingo

On Wed, Jan 03, 2018 at 11:10:37AM +0900, Byungchul Park wrote: > > The point I was trying to drive home is that "all we have to do is > > just classify everything well or just invalidate the right lock > > Just to be sure, we don't have to invalidate lock objects at all but > a problematic

Re: [PATCH] exec: Weaken dumpability for secureexec

On Tue, Jan 02, 2018 at 03:21:33PM -0800, Kees Cook wrote: > This is a logical revert of: > > commit e37fdb785a5f ("exec: Use secureexec for setting dumpability") > > This weakens dumpability back to checking only for uid/gid changes in > current (which is useless), but userspace depends on

Re: [PATCH] exec: Weaken dumpability for secureexec

On Tue, Jan 02, 2018 at 03:21:33PM -0800, Kees Cook wrote: > This is a logical revert of: > > commit e37fdb785a5f ("exec: Use secureexec for setting dumpability") > > This weakens dumpability back to checking only for uid/gid changes in > current (which is useless), but userspace depends on

Re: [PATCH] bonding: Delete an error message for a failed memory allocation in bond_update_slave_arr()

On Mon, Jan 1, 2018 at 8:07 AM, SF Markus Elfring wrote: > From: Markus Elfring > Date: Mon, 1 Jan 2018 17:00:04 +0100 > > Omit an extra message for a memory allocation failure in this function. > > This issue was detected by using

Re: [PATCH] bonding: Delete an error message for a failed memory allocation in bond_update_slave_arr()

On Mon, Jan 1, 2018 at 8:07 AM, SF Markus Elfring wrote: > From: Markus Elfring > Date: Mon, 1 Jan 2018 17:00:04 +0100 > > Omit an extra message for a memory allocation failure in this function. > > This issue was detected by using the Coccinelle software. > What is the issue with this message?

Re: [PATCH] nokia N9: Add support for magnetometer and touchscreen

Hi, On 01/02/2018 06:27 PM, Sebastian Reichel wrote: > Hi, > > On Tue, Jan 02, 2018 at 02:17:22PM +0100, Pavel Machek wrote: >> This adds dts support for magnetometer and touchscreen on Nokia N9. > > I think it makes sense to have this splitted. > >> Signed-off-by: Pavel Machek

Re: [PATCH] nokia N9: Add support for magnetometer and touchscreen

Hi, On 01/02/2018 06:27 PM, Sebastian Reichel wrote: > Hi, > > On Tue, Jan 02, 2018 at 02:17:22PM +0100, Pavel Machek wrote: >> This adds dts support for magnetometer and touchscreen on Nokia N9. > > I think it makes sense to have this splitted. > >> Signed-off-by: Pavel Machek >> >> diff

Re: [PATCH] mm/fadvise: discard partial pages iff endbyte is also eof

> 在 2017年12月23日，12:16，十刀 写道： > > From: "shidao.ytt" > > in commit 441c228f817f7 ("mm: fadvise: document the > fadvise(FADV_DONTNEED) behaviour for partial pages") Mel Gorman > explained why partial pages should be preserved instead of

Re: [PATCH] mm/fadvise: discard partial pages iff endbyte is also eof

> 在 2017年12月23日，12:16，十刀 写道： > > From: "shidao.ytt" > > in commit 441c228f817f7 ("mm: fadvise: document the > fadvise(FADV_DONTNEED) behaviour for partial pages") Mel Gorman > explained why partial pages should be preserved instead of discarded > when using fadvise(FADV_DONTNEED), however

Re: [PATCH 2/3] dt-bindings: mtd: atmel-quadspi: add an optional property 'dmacap,memcpy'

On Tue, Jan 02, 2018 at 07:18:58PM +, Trent Piepho wrote: > On Tue, 2018-01-02 at 11:22 +0100, Ludovic Desroches wrote: > > On Wed, Dec 27, 2017 at 10:40:00PM +0100, Cyrille Pitchen wrote: > > > > > Or maybe no change at all is required at the at_xdmac.c driver side: we > > > just don't care

Re: [PATCH 2/3] dt-bindings: mtd: atmel-quadspi: add an optional property 'dmacap,memcpy'

On Tue, Jan 02, 2018 at 07:18:58PM +, Trent Piepho wrote: > On Tue, 2018-01-02 at 11:22 +0100, Ludovic Desroches wrote: > > On Wed, Dec 27, 2017 at 10:40:00PM +0100, Cyrille Pitchen wrote: > > > > > Or maybe no change at all is required at the at_xdmac.c driver side: we > > > just don't care

Re: [PATCH 0/2] perf-probe: Improve warning message for buildid mismatch

On 12/18/2017 12:58 PM, Masami Hiramatsu wrote: > Hello, > > This series ensure the build-ids for target binary and debuginfo > are matched. If there is a mismatch, it warns user to check the > package versions. For the series, Reviewed-by: Ravi Bangoria

Re: [PATCH 0/2] perf-probe: Improve warning message for buildid mismatch

On 12/18/2017 12:58 PM, Masami Hiramatsu wrote: > Hello, > > This series ensure the build-ids for target binary and debuginfo > are matched. If there is a mismatch, it warns user to check the > package versions. For the series, Reviewed-by: Ravi Bangoria

Re: [f2fs-dev] [PATCH v3] f2fs: add reserved blocks for root user

On 2018/1/3 3:24, Jaegeuk Kim wrote: >> How about adding uid & gid verification also like ext4? > > Again, that's another feature which requires a mount option. I think it'd be > better to add that, once we have a use-case. That's OK. ;) Thanks,

Re: [f2fs-dev] [PATCH v5] f2fs: add reserved blocks for root user

On 2018/1/3 10:21, Jaegeuk Kim wrote: > This patch allows root to reserve some blocks via mount option. > > "-o reserve_root=N" means N x 4KB-sized blocks for root only. > > Signed-off-by: Jaegeuk Kim > --- > > Change log from v4: > - fix f_bfree in statfs Could you fix

Re: [f2fs-dev] [PATCH v3] f2fs: add reserved blocks for root user

On 2018/1/3 3:24, Jaegeuk Kim wrote: >> How about adding uid & gid verification also like ext4? > > Again, that's another feature which requires a mount option. I think it'd be > better to add that, once we have a use-case. That's OK. ;) Thanks,

Re: [f2fs-dev] [PATCH v5] f2fs: add reserved blocks for root user

On 2018/1/3 10:21, Jaegeuk Kim wrote: > This patch allows root to reserve some blocks via mount option. > > "-o reserve_root=N" means N x 4KB-sized blocks for root only. > > Signed-off-by: Jaegeuk Kim > --- > > Change log from v4: > - fix f_bfree in statfs Could you fix f_bfree calculation

[PATCH v2 1/4] dmaengine: xilinx_dma: populate dma caps properly

When client driver uses dma_get_slave_caps() api, it checks for certain fields of dma_device struct currently driver is not settings the directions and addr_widths fields resulting dma_get_slave_caps() returning failure. This patch fixes this issue by populating proper values to the struct

[PATCH v2 1/4] dmaengine: xilinx_dma: populate dma caps properly

When client driver uses dma_get_slave_caps() api, it checks for certain fields of dma_device struct currently driver is not settings the directions and addr_widths fields resulting dma_get_slave_caps() returning failure. This patch fixes this issue by populating proper values to the struct

[PATCH v2 3/4] dmaengine: xilinx_dma: Fix warning variable prev set but not used

This patch fixes the below sparse warning in the driver drivers/dma/xilinx/xilinx_dma.c: In function ‘xilinx_vdma_dma_prep_interleaved’: drivers/dma/xilinx/xilinx_dma.c:1614:43: warning: variable ‘prev’ set but not used [-Wunused-but-set-variable] struct xilinx_vdma_tx_segment *segment, *prev =

[PATCH v2 0/4] dmaengine: xilinx_dma: Bug fixes

This patch series does the below --> Fixes sparse warnings in the driver. --> properly configures the SG mode bit in the driver for cdma. --> populates dma caps properly. This patch series got created on top of linux tag 4.15-rc4 i.e slave-dma.git next branch Kedareswara rao Appana (4):

[PATCH v2 3/4] dmaengine: xilinx_dma: Fix warning variable prev set but not used

This patch fixes the below sparse warning in the driver drivers/dma/xilinx/xilinx_dma.c: In function ‘xilinx_vdma_dma_prep_interleaved’: drivers/dma/xilinx/xilinx_dma.c:1614:43: warning: variable ‘prev’ set but not used [-Wunused-but-set-variable] struct xilinx_vdma_tx_segment *segment, *prev =

[PATCH v2 0/4] dmaengine: xilinx_dma: Bug fixes

This patch series does the below --> Fixes sparse warnings in the driver. --> properly configures the SG mode bit in the driver for cdma. --> populates dma caps properly. This patch series got created on top of linux tag 4.15-rc4 i.e slave-dma.git next branch Kedareswara rao Appana (4):

[PATCH v2 2/4] dmaengine: xilinx_dma: properly configure the SG mode bit in the driver for cdma

If the hardware is configured for Scatter Gather(SG) mode, and hardware is idle, in the control register SG mode bit must be set to a 0 then back to 1 by the software, to force the CDMA SG engine to use a new value written to the CURDESC_PNTR register, failure to do so could result errors from the

[PATCH v2 2/4] dmaengine: xilinx_dma: properly configure the SG mode bit in the driver for cdma

If the hardware is configured for Scatter Gather(SG) mode, and hardware is idle, in the control register SG mode bit must be set to a 0 then back to 1 by the software, to force the CDMA SG engine to use a new value written to the CURDESC_PNTR register, failure to do so could result errors from the

Re: [PATCH v3 00/27] kill devm_ioremap_nocache

+ cris/ia64/mn10300/openrisc maintainers On 2017/12/25 9:09, Yisheng Xie wrote: > hi Christophe and Greg, > > On 2017/12/24 16:55, christophe leroy wrote: >> >> >> Le 23/12/2017 à 16:57, Guenter Roeck a écrit : >>> On 12/23/2017 05:48 AM, Greg KH wrote: On Sat, Dec 23, 2017 at 06:55:25PM

Re: [PATCH v3 00/27] kill devm_ioremap_nocache

+ cris/ia64/mn10300/openrisc maintainers On 2017/12/25 9:09, Yisheng Xie wrote: > hi Christophe and Greg, > > On 2017/12/24 16:55, christophe leroy wrote: >> >> >> Le 23/12/2017 à 16:57, Guenter Roeck a écrit : >>> On 12/23/2017 05:48 AM, Greg KH wrote: On Sat, Dec 23, 2017 at 06:55:25PM

[PATCH v2 4/4] dmaengine: xilinx_dma: Free BD consistent memory

Free BD consistent memory while freeing the channel i.e in free_chan_resources. Signed-off-by: Radhey Shyam Pandey Signed-off-by: Kedareswara rao Appana --- Changes for v2: --> None. drivers/dma/xilinx/xilinx_dma.c | 5 + 1 file changed, 5

[PATCH v2 4/4] dmaengine: xilinx_dma: Free BD consistent memory

Free BD consistent memory while freeing the channel i.e in free_chan_resources. Signed-off-by: Radhey Shyam Pandey Signed-off-by: Kedareswara rao Appana --- Changes for v2: --> None. drivers/dma/xilinx/xilinx_dma.c | 5 + 1 file changed, 5 insertions(+) diff --git

Re: [PATCH v2] regulator: sc2731: Fix defines for SC2731_WR_UNLOCK and SC2731_PWR_WR_PROT_VALUE

Hi Axel, On 一, 1月 01, 2018 at 08:38:50下午 +0800, Axel Lin wrote: > The defines for SC2731_WR_UNLOCK and SC2731_PWR_WR_PROT_VALUE makes > regmap_write() call looks strange because it takes reg parameter fist > then val. > Base on Erick's suggestion to define SC2731_PWR_WR_PROT and >

Re: [PATCH v2] regulator: sc2731: Fix defines for SC2731_WR_UNLOCK and SC2731_PWR_WR_PROT_VALUE

Hi Axel, On 一, 1月 01, 2018 at 08:38:50下午 +0800, Axel Lin wrote: > The defines for SC2731_WR_UNLOCK and SC2731_PWR_WR_PROT_VALUE makes > regmap_write() call looks strange because it takes reg parameter fist > then val. > Base on Erick's suggestion to define SC2731_PWR_WR_PROT and >

Re: WARNING in adjust_ptr_min_max_vals

On Tue, Jan 02, 2018 at 08:58:01PM -0800, syzbot wrote: > Hello, > > syzkaller hit the following crash on > 0e08c463db387a2adcb0243b15ab868a73f87807 > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console

Re: WARNING in adjust_ptr_min_max_vals

On Tue, Jan 02, 2018 at 08:58:01PM -0800, syzbot wrote: > Hello, > > syzkaller hit the following crash on > 0e08c463db387a2adcb0243b15ab868a73f87807 > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console

Re: [PATCH v5 2/2] PCI: mediatek: Set up class type and vendor ID for MT7622

On Tue, 2018-01-02 at 10:56 +, Lorenzo Pieralisi wrote: > On Thu, Dec 28, 2017 at 09:39:12AM +0800, Honghui Zhang wrote: > > On Wed, 2017-12-27 at 12:45 -0600, Bjorn Helgaas wrote: > > > On Wed, Dec 27, 2017 at 08:59:54AM +0800, honghui.zh...@mediatek.com > > > wrote: > > > > From: Honghui

Re: [PATCH v5 2/2] PCI: mediatek: Set up class type and vendor ID for MT7622

On Tue, 2018-01-02 at 10:56 +, Lorenzo Pieralisi wrote: > On Thu, Dec 28, 2017 at 09:39:12AM +0800, Honghui Zhang wrote: > > On Wed, 2017-12-27 at 12:45 -0600, Bjorn Helgaas wrote: > > > On Wed, Dec 27, 2017 at 08:59:54AM +0800, honghui.zh...@mediatek.com > > > wrote: > > > > From: Honghui

[PATCH] irqchip/gic-v3-its: Add workaround for ThunderX2 erratum #174

When an interrupt is moved across node collections on ThunderX2 multi Socket platform, an interrupt stops routed to new collection and results in loss of interrupts. Adding workaround to issue INV after MOVI for cross-node collection move to flush out the cached entry. Signed-off-by: Ganapatrao

[PATCH] irqchip/gic-v3-its: Add workaround for ThunderX2 erratum #174

When an interrupt is moved across node collections on ThunderX2 multi Socket platform, an interrupt stops routed to new collection and results in loss of interrupts. Adding workaround to issue INV after MOVI for cross-node collection move to flush out the cached entry. Signed-off-by: Ganapatrao

Re: [PATCH] KVM: nVMX: remove unnecessary vmwrite from L2->L1 vmexit

On 2018/01/02 17:47, Liran Alon wrote: On 02/01/18 00:58, Paolo Bonzini wrote: The POSTED_INTR_NV field is constant (though it differs between the vmcs01 and vmcs02), there is no need to reload it on vmexit to L1. Signed-off-by: Paolo Bonzini ---   arch/x86/kvm/vmx.c

Re: [PATCH] KVM: nVMX: remove unnecessary vmwrite from L2->L1 vmexit

On 2018/01/02 17:47, Liran Alon wrote: On 02/01/18 00:58, Paolo Bonzini wrote: The POSTED_INTR_NV field is constant (though it differs between the vmcs01 and vmcs02), there is no need to reload it on vmexit to L1. Signed-off-by: Paolo Bonzini ---   arch/x86/kvm/vmx.c | 3 ---   1 file

Business Opportunity

Hello, How are you and your family? Thanks for accepting my connection. I am connecting you due to a Business Opportunity. Should you like to know more about it. Do get back to me so i give you further details. I hope to hear from you soon Regards, MR. YIN LIANCHEN CHIEF INVESTMENT OFFICER

Business Opportunity

Hello, How are you and your family? Thanks for accepting my connection. I am connecting you due to a Business Opportunity. Should you like to know more about it. Do get back to me so i give you further details. I hope to hear from you soon Regards, MR. YIN LIANCHEN CHIEF INVESTMENT OFFICER

Re: [PATCH 16/67] powerpc: rename dma_direct_ to dma_nommu_

Geert Uytterhoeven writes: > On Tue, Jan 2, 2018 at 10:45 AM, Michael Ellerman wrote: >> Christoph Hellwig writes: >> >>> We want to use the dma_direct_ namespace for a generic implementation, >>> so rename powerpc to the second best

Re: [PATCH 16/67] powerpc: rename dma_direct_ to dma_nommu_

Geert Uytterhoeven writes: > On Tue, Jan 2, 2018 at 10:45 AM, Michael Ellerman wrote: >> Christoph Hellwig writes: >> >>> We want to use the dma_direct_ namespace for a generic implementation, >>> so rename powerpc to the second best choice: dma_nommu_. >> >> I'm not a fan of "nommu". Some of

Re: general protection fault in copy_verifier_state

On Tue, Jan 02, 2018 at 02:58:01PM -0800, syzbot wrote: > Hello, > > syzkaller hit the following crash on > 6bb8824732f69de0f233ae6b1a8158e149627b38 > git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console

Re: general protection fault in copy_verifier_state

On Tue, Jan 02, 2018 at 02:58:01PM -0800, syzbot wrote: > Hello, > > syzkaller hit the following crash on > 6bb8824732f69de0f233ae6b1a8158e149627b38 > git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console

Re: [PATCH v3 18/27] pinctrl: replace devm_ioremap_nocache with devm_ioremap

On 2018/1/2 16:43, Linus Walleij wrote: > On Sat, Dec 23, 2017 at 12:00 PM, Yisheng Xie wrote: > >> Default ioremap is ioremap_nocache, so devm_ioremap has the same >> function with devm_ioremap_nocache, which can just be killed to >> save the size of devres.o >> >>

Re: [PATCH v3 18/27] pinctrl: replace devm_ioremap_nocache with devm_ioremap

On 2018/1/2 16:43, Linus Walleij wrote: > On Sat, Dec 23, 2017 at 12:00 PM, Yisheng Xie wrote: > >> Default ioremap is ioremap_nocache, so devm_ioremap has the same >> function with devm_ioremap_nocache, which can just be killed to >> save the size of devres.o >> >> This patch is to use use

Re: [PATCH v2 0/4] Address error and recovery for AER and DPC

On 2018-01-03 00:32, Bjorn Helgaas wrote: On Fri, Dec 29, 2017 at 12:54:15PM +0530, Oza Pawandeep wrote: This patch set brings in support for DPC and AER to co-exist and not to race for recovery. The current implementation of AER and error message broadcasting to the EP driver is tightly

Re: [PATCH v2 0/4] Address error and recovery for AER and DPC

On 2018-01-03 00:32, Bjorn Helgaas wrote: On Fri, Dec 29, 2017 at 12:54:15PM +0530, Oza Pawandeep wrote: This patch set brings in support for DPC and AER to co-exist and not to race for recovery. The current implementation of AER and error message broadcasting to the EP driver is tightly

RE: [LINUX PATCH 3/4] dmaengine: xilinx_dma: Fix compilation warning

Hi Vinod, >On Wed, Jan 03, 2018 at 05:13:29AM +, Appana Durga Kedareswara Rao >wrote: >> Hi Vinod, >> >> Thanks for the review... >> >> > >> >On Thu, Dec 21, 2017 at 03:41:37PM +0530, Kedareswara rao Appana wrote: >> > >> >Fix title here too >> >> Sure will fix in v2... >> >> > >> >BTW

RE: [LINUX PATCH 3/4] dmaengine: xilinx_dma: Fix compilation warning

Hi Vinod, >On Wed, Jan 03, 2018 at 05:13:29AM +, Appana Durga Kedareswara Rao >wrote: >> Hi Vinod, >> >> Thanks for the review... >> >> > >> >On Thu, Dec 21, 2017 at 03:41:37PM +0530, Kedareswara rao Appana wrote: >> > >> >Fix title here too >> >> Sure will fix in v2... >> >> > >> >BTW

[PATCH] iommu/of: Only do IOMMU lookup for available ones

The for_each_matching_node_and_match() would return every matching nodes including unavailable ones. It's pointless to init unavailable IOMMUs, so add a sanity check to avoid that. Signed-off-by: Jeffy Chen --- drivers/iommu/of_iommu.c | 3 +++ 1 file changed, 3

[PATCH] iommu/of: Only do IOMMU lookup for available ones

The for_each_matching_node_and_match() would return every matching nodes including unavailable ones. It's pointless to init unavailable IOMMUs, so add a sanity check to avoid that. Signed-off-by: Jeffy Chen --- drivers/iommu/of_iommu.c | 3 +++ 1 file changed, 3 insertions(+) diff --git

Re: [PATCH v3 06/27] gpio: replace devm_ioremap_nocache with devm_ioremap

On 2018/1/2 16:41, Linus Walleij wrote: > On Sat, Dec 23, 2017 at 11:58 AM, Yisheng Xie wrote: > >> Default ioremap is ioremap_nocache, so devm_ioremap has the same >> function with devm_ioremap_nocache, which can just be killed to >> save the size of devres.o >> >>

Re: [PATCH v3 06/27] gpio: replace devm_ioremap_nocache with devm_ioremap

On 2018/1/2 16:41, Linus Walleij wrote: > On Sat, Dec 23, 2017 at 11:58 AM, Yisheng Xie wrote: > >> Default ioremap is ioremap_nocache, so devm_ioremap has the same >> function with devm_ioremap_nocache, which can just be killed to >> save the size of devres.o >> >> This patch is to use use

linux-next: Tree for Jan 3

Hi all, Changes since 20180102: The clk tree lost its build failure. The kvm-arm tree gained a conflict against Linus' tree. Non-merge commits (relative to Linus' tree): 6587 6916 files changed, 273638 insertions(+), 194470 deletions

linux-next: Tree for Jan 3

Hi all, Changes since 20180102: The clk tree lost its build failure. The kvm-arm tree gained a conflict against Linus' tree. Non-merge commits (relative to Linus' tree): 6587 6916 files changed, 273638 insertions(+), 194470 deletions

Re: [ANNOUNCE] Git v2.16.0-rc0

Bryan Turner wrote: > On Tue, Jan 2, 2018 at 9:07 PM, Jonathan Nieder wrote: >> So my first question is why the basename detection is not working for >> you. What value of GIT_SSH, GIT_SSH_COMMAND, or core.sshCommand are >> you using? > > So I'd been digging further into

Re: [ANNOUNCE] Git v2.16.0-rc0

Bryan Turner wrote: > On Tue, Jan 2, 2018 at 9:07 PM, Jonathan Nieder wrote: >> So my first question is why the basename detection is not working for >> you. What value of GIT_SSH, GIT_SSH_COMMAND, or core.sshCommand are >> you using? > > So I'd been digging further into this for the last hour

Re: About the try to remove cross-release feature entirely by Ingo

On 1/3/2018 11:58 AM, Dave Chinner wrote: On Wed, Jan 03, 2018 at 11:28:44AM +0900, Byungchul Park wrote: On 1/1/2018 7:18 PM, Matthew Wilcox wrote: On Sat, Dec 30, 2017 at 06:00:57PM -0500, Theodore Ts'o wrote: Also, what to do with TCP connections which are created in userspace (with some

Re: About the try to remove cross-release feature entirely by Ingo

On 1/3/2018 11:58 AM, Dave Chinner wrote: On Wed, Jan 03, 2018 at 11:28:44AM +0900, Byungchul Park wrote: On 1/1/2018 7:18 PM, Matthew Wilcox wrote: On Sat, Dec 30, 2017 at 06:00:57PM -0500, Theodore Ts'o wrote: Also, what to do with TCP connections which are created in userspace (with some

Re: [PATCH 10/13] ocxl: Add Makefile and Kconfig

On 19/12/17 02:21, Frederic Barrat wrote: OCXL_BASE triggers the platform support needed by the driver. Signed-off-by: Frederic Barrat --- drivers/misc/Kconfig | 1 + drivers/misc/Makefile | 1 + drivers/misc/ocxl/Kconfig | 25

Re: [PATCH 10/13] ocxl: Add Makefile and Kconfig

On 19/12/17 02:21, Frederic Barrat wrote: OCXL_BASE triggers the platform support needed by the driver. Signed-off-by: Frederic Barrat --- drivers/misc/Kconfig | 1 + drivers/misc/Makefile | 1 + drivers/misc/ocxl/Kconfig | 25 +

Re: [PATCH 02/11] clk: sunxi-ng: a83t: Add M divider to TCON1 clock

On Sun, Dec 31, 2017 at 5:01 AM, Jernej Skrabec wrote: > TCON1 also has M divider, contrary to TCON0. > > Fixes: 05359be1176b ("clk: sunxi-ng: Add driver for A83T CCU") > > Signed-off-by: Jernej Skrabec Added "And the mux is only 2 bits wide,

Re: [PATCH 02/11] clk: sunxi-ng: a83t: Add M divider to TCON1 clock

On Sun, Dec 31, 2017 at 5:01 AM, Jernej Skrabec wrote: > TCON1 also has M divider, contrary to TCON0. > > Fixes: 05359be1176b ("clk: sunxi-ng: Add driver for A83T CCU") > > Signed-off-by: Jernej Skrabec Added "And the mux is only 2 bits wide, instead of 3." to the commit message and applied.

  1   2   3   4   5   6   7   8   9   10   >