Re: [RFC PATCH bpf-next v2 1/4] tracing/kprobe: bpf: Check error injectable event is on function entry

On Wed, 27 Dec 2017 19:45:42 -0800 Alexei Starovoitov wrote: > On 12/27/17 6:34 PM, Masami Hiramatsu wrote: > > On Wed, 27 Dec 2017 14:46:24 -0800 > > Alexei Starovoitov wrote: > > > >> On 12/26/17 9:56 PM, Masami Hiramatsu wrote: > >>> On Tue, 26 Dec 2017 17:57:32

Re: [RFC PATCH bpf-next v2 1/4] tracing/kprobe: bpf: Check error injectable event is on function entry

On Wed, 27 Dec 2017 19:45:42 -0800 Alexei Starovoitov wrote: > On 12/27/17 6:34 PM, Masami Hiramatsu wrote: > > On Wed, 27 Dec 2017 14:46:24 -0800 > > Alexei Starovoitov wrote: > > > >> On 12/26/17 9:56 PM, Masami Hiramatsu wrote: > >>> On Tue, 26 Dec 2017 17:57:32 -0800 > >>> Alexei

Re: WARNING in strp_data_ready

On Thu, Dec 28, 2017 at 2:19 AM, Tom Herbert wrote: > On Wed, Dec 27, 2017 at 12:20 PM, Ozgur wrote: >> >> >> 27.12.2017, 23:14, "Dmitry Vyukov" : >>> On Wed, Dec 27, 2017 at 9:08 PM, Ozgur wrote: 27.12.2017,

Re: WARNING in strp_data_ready

On Thu, Dec 28, 2017 at 2:19 AM, Tom Herbert wrote: > On Wed, Dec 27, 2017 at 12:20 PM, Ozgur wrote: >> >> >> 27.12.2017, 23:14, "Dmitry Vyukov" : >>> On Wed, Dec 27, 2017 at 9:08 PM, Ozgur wrote: 27.12.2017, 22:21, "Dmitry Vyukov" : > On Wed, Dec 27, 2017 at 8:09 PM, Tom Herbert

Re: [RFC PATCH bpf-next v2 4/4] error-injection: Support fault injection framework

On Wed, 27 Dec 2017 19:49:28 -0800 Alexei Starovoitov wrote: > On 12/27/17 5:38 PM, Masami Hiramatsu wrote: > > On Wed, 27 Dec 2017 14:49:46 -0800 > > Alexei Starovoitov wrote: > > > >> On 12/27/17 12:09 AM, Masami Hiramatsu wrote: > >>> On Tue, 26 Dec 2017 18:12:56

Re: [RFC PATCH bpf-next v2 4/4] error-injection: Support fault injection framework

On Wed, 27 Dec 2017 19:49:28 -0800 Alexei Starovoitov wrote: > On 12/27/17 5:38 PM, Masami Hiramatsu wrote: > > On Wed, 27 Dec 2017 14:49:46 -0800 > > Alexei Starovoitov wrote: > > > >> On 12/27/17 12:09 AM, Masami Hiramatsu wrote: > >>> On Tue, 26 Dec 2017 18:12:56 -0800 > >>> Alexei

[PATCH v2] ocfs2: try a blocking lock before return AOP_TRUNCATED_PAGE

If we can't get inode lock immediately in the function ocfs2_inode_lock_with_page() when reading a page, we should not return directly here, since this will lead to a softlockup problem when the kernel is configured with CONFIG_PREEMPT is not set. The method is to get a blocking lock and

[PATCH v2] ocfs2: try a blocking lock before return AOP_TRUNCATED_PAGE

If we can't get inode lock immediately in the function ocfs2_inode_lock_with_page() when reading a page, we should not return directly here, since this will lead to a softlockup problem when the kernel is configured with CONFIG_PREEMPT is not set. The method is to get a blocking lock and

Re: [PATCH net-next 5/6] arm64: dts: marvell: mcbin: enable the fourth network interface

On Wed, Dec 27, 2017 at 10:24:01PM +, Russell King - ARM Linux wrote: > On Wed, Dec 27, 2017 at 11:14:45PM +0100, Antoine Tenart wrote: > > This patch enables the fourth network interface on the Marvell > > Macchiatobin. It is configured in the 2500Base-X PHY mode. > > > > Signed-off-by:

Re: [PATCH net-next 5/6] arm64: dts: marvell: mcbin: enable the fourth network interface

On Wed, Dec 27, 2017 at 10:24:01PM +, Russell King - ARM Linux wrote: > On Wed, Dec 27, 2017 at 11:14:45PM +0100, Antoine Tenart wrote: > > This patch enables the fourth network interface on the Marvell > > Macchiatobin. It is configured in the 2500Base-X PHY mode. > > > > Signed-off-by:

Re: mmots build error (2)

On Thu, Dec 28, 2017 at 8:32 AM, syzbot wrote: > Hello, > > syzkaller hit the following crash on > 253f36c7c1aee654871b4f0c5e16ee6c396bff9a > git://git.cmpxchg.org/linux-mmots.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is

Re: mmots build error (2)

On Thu, Dec 28, 2017 at 8:32 AM, syzbot wrote: > Hello, > > syzkaller hit the following crash on > 253f36c7c1aee654871b4f0c5e16ee6c396bff9a > git://git.cmpxchg.org/linux-mmots.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console output is attached. > Unfortunately,

Re: WARNING: kernel stack regs has bad 'bp' value (2)

On Wed, Dec 27, 2017 at 7:29 PM, Dmitry Vyukov wrote: > On Thu, Nov 30, 2017 at 10:17 AM, Eric Biggers wrote: >> On Tue, Nov 28, 2017 at 10:36:01AM -0800, syzbot wrote: >>> WARNING: kernel stack regs at 8801c1e5f468 in syzkaller196611:6199 has >>> bad

Re: WARNING: kernel stack regs has bad 'bp' value (2)

On Wed, Dec 27, 2017 at 7:29 PM, Dmitry Vyukov wrote: > On Thu, Nov 30, 2017 at 10:17 AM, Eric Biggers wrote: >> On Tue, Nov 28, 2017 at 10:36:01AM -0800, syzbot wrote: >>> WARNING: kernel stack regs at 8801c1e5f468 in syzkaller196611:6199 has >>> bad 'bp' value 0001 >>> unwind

Re: [PATCH net-next 1/6] phy: add 2.5G SGMII mode to the phy_mode enum

On Wed, Dec 27, 2017 at 11:14:41PM +0100, Antoine Tenart wrote: > This patch adds one more generic PHY mode to the phy_mode enum, to allow > configuring generic PHYs to the 2.5G SGMII mode by using the set_mode > callback. > > Signed-off-by: Antoine Tenart >

Re: [PATCH net-next 1/6] phy: add 2.5G SGMII mode to the phy_mode enum

On Wed, Dec 27, 2017 at 11:14:41PM +0100, Antoine Tenart wrote: > This patch adds one more generic PHY mode to the phy_mode enum, to allow > configuring generic PHYs to the 2.5G SGMII mode by using the set_mode > callback. > > Signed-off-by: Antoine Tenart > --- > include/linux/phy/phy.h | 1 +

Re: [PATCH] Staging: ipx: fixed several no space before tabs coding style issues

On Wed, Dec 27, 2017 at 09:25:44PM +, Jianshen Liu wrote: > Fixed several coding style warnings of "please, no space before tabs". > > Signed-off-by: Jianshen Liu > --- > drivers/staging/ipx/af_ipx.c| 56 > - >

Re: [PATCH] Staging: ipx: fixed several no space before tabs coding style issues

On Wed, Dec 27, 2017 at 09:25:44PM +, Jianshen Liu wrote: > Fixed several coding style warnings of "please, no space before tabs". > > Signed-off-by: Jianshen Liu > --- > drivers/staging/ipx/af_ipx.c| 56 > - > drivers/staging/ipx/ipx_proc.c |

Re: [PATCH 1/2] nvmem: add driver for JZ4780 efuse

Hi Mathieu, PrasannaKumar, On 27.12.2017 13:27, Mathieu Malaterre wrote: From: PrasannaKumar Muralidharan This patch brings support for the JZ4780 efuse. Currently it only expose a read only access to the entire 8K bits efuse memory. Tested-by: Mathieu Malaterre

Re: [PATCH 1/2] nvmem: add driver for JZ4780 efuse

Hi Mathieu, PrasannaKumar, On 27.12.2017 13:27, Mathieu Malaterre wrote: From: PrasannaKumar Muralidharan This patch brings support for the JZ4780 efuse. Currently it only expose a read only access to the entire 8K bits efuse memory. Tested-by: Mathieu Malaterre Signed-off-by: PrasannaKumar

Re: [PATCH] crypto: stm32 - Use standard CONFIG name

On Wed, Dec 20, 2017 at 06:19:32PM +, Corentin Labbe wrote: > All hardware crypto devices have their CONFIG names using the following > convention: > CRYPTO_DEV_name_algo > > This patch apply this conventions on STM32 CONFIG names. > > Signed-off-by: Corentin Labbe

Re: [PATCH] crypto: stm32 - Use standard CONFIG name

On Wed, Dec 20, 2017 at 06:19:32PM +, Corentin Labbe wrote: > All hardware crypto devices have their CONFIG names using the following > convention: > CRYPTO_DEV_name_algo > > This patch apply this conventions on STM32 CONFIG names. > > Signed-off-by: Corentin Labbe Patch applied. Thanks.

Re: [PATCH v2 0/6] crypto: tcrypt: fix and add multi buf speed tests

On Sun, Dec 17, 2017 at 08:28:59AM +, Gilad Ben-Yossef wrote: > The performance of some crypto tfm providers is affected by > the amount of parallelism possible with the processing. > > We already had some support for speed test of multiple concurrent > requests, dubbed multi buffer, in ahash

Re: [PATCH] crypto: x86/twofish-3way - Fix %rbp usage

On Mon, Dec 18, 2017 at 04:40:26PM -0800, Eric Biggers wrote: > From: Eric Biggers > > Using %rbp as a temporary register breaks frame pointer convention and > breaks stack traces when unwinding from an interrupt in the crypto code. > > In twofish-3way, we can't simply

Re: [PATCH v2 0/6] crypto: tcrypt: fix and add multi buf speed tests

On Sun, Dec 17, 2017 at 08:28:59AM +, Gilad Ben-Yossef wrote: > The performance of some crypto tfm providers is affected by > the amount of parallelism possible with the processing. > > We already had some support for speed test of multiple concurrent > requests, dubbed multi buffer, in ahash

Re: [PATCH] crypto: x86/twofish-3way - Fix %rbp usage

On Mon, Dec 18, 2017 at 04:40:26PM -0800, Eric Biggers wrote: > From: Eric Biggers > > Using %rbp as a temporary register breaks frame pointer convention and > breaks stack traces when unwinding from an interrupt in the crypto code. > > In twofish-3way, we can't simply replace %rbp with another

[PATCH net-next v9 1/2] dt-bindings: net: add DT bindings for Socionext UniPhier AVE

DT bindings for the AVE ethernet controller found on Socionext's UniPhier platforms. Signed-off-by: Kunihiko Hayashi Signed-off-by: Jassi Brar Acked-by: Rob Herring Reviewed-by: Florian Fainelli

[PATCH net-next v9 1/2] dt-bindings: net: add DT bindings for Socionext UniPhier AVE

DT bindings for the AVE ethernet controller found on Socionext's UniPhier platforms. Signed-off-by: Kunihiko Hayashi Signed-off-by: Jassi Brar Acked-by: Rob Herring Reviewed-by: Florian Fainelli --- .../bindings/net/socionext,uniphier-ave4.txt | 48 ++ 1 file

[PATCH net-next v9 2/2] net: ethernet: socionext: add AVE ethernet driver

The UniPhier platform from Socionext provides the AVE ethernet controller that includes MAC and MDIO bus supporting RGMII/RMII modes. The controller is named AVE. Signed-off-by: Kunihiko Hayashi Signed-off-by: Jassi Brar Reviewed-by:

[PATCH net-next v9 2/2] net: ethernet: socionext: add AVE ethernet driver

The UniPhier platform from Socionext provides the AVE ethernet controller that includes MAC and MDIO bus supporting RGMII/RMII modes. The controller is named AVE. Signed-off-by: Kunihiko Hayashi Signed-off-by: Jassi Brar Reviewed-by: Andrew Lunn --- drivers/net/ethernet/Kconfig |

[PATCH net-next v9 0/2] add UniPhier AVE ethernet support

This series adds support for Socionext AVE ethernet controller implemented on UniPhier SoCs. This driver supports RGMII/RMII modes. v8: https://www.spinics.net/lists/netdev/msg474374.html The PHY patch included in v1 has already separated in: http://www.spinics.net/lists/netdev/msg454595.html

[PATCH net-next v9 0/2] add UniPhier AVE ethernet support

This series adds support for Socionext AVE ethernet controller implemented on UniPhier SoCs. This driver supports RGMII/RMII modes. v8: https://www.spinics.net/lists/netdev/msg474374.html The PHY patch included in v1 has already separated in: http://www.spinics.net/lists/netdev/msg454595.html

Re: [PATCH] padata: add SPDX identifier

Cheah Kok Cheong wrote: > Add SPDX license identifier according to the type of license text found > in the file. > > Cc: Philippe Ombredanne > Signed-off-by: Cheah Kok Cheong > --- > kernel/padata.c | 1 + > 1 file changed, 1

Re: [PATCH] padata: add SPDX identifier

Cheah Kok Cheong wrote: > Add SPDX license identifier according to the type of license text found > in the file. > > Cc: Philippe Ombredanne > Signed-off-by: Cheah Kok Cheong > --- > kernel/padata.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/kernel/padata.c b/kernel/padata.c >

Re: [RFC][PATCHv6 00/12] printk: introduce printing kernel thread

Hello, On (12/21/17 23:19), Steven Rostedt wrote: [..] > > I wrote this before but this isn't a theoretical problem. We see > > these stalls a lot. Preemption isn't enabled to begin with. Memory > > pressure is high and OOM triggers and printk starts printing out OOM > > warnings; then, a

Re: [RFC][PATCHv6 00/12] printk: introduce printing kernel thread

Hello, On (12/21/17 23:19), Steven Rostedt wrote: [..] > > I wrote this before but this isn't a theoretical problem. We see > > these stalls a lot. Preemption isn't enabled to begin with. Memory > > pressure is high and OOM triggers and printk starts printing out OOM > > warnings; then, a

RE: [PATCH v2] ftrace/module: Move ftrace_release_mod to ddebug_cleanup label

  Hello Steve, As per the discussion I sent patch v2. Please find. Thanks, Namit Gupta - Original Message - Sender : NAMIT GUPTA  ./Senior Chief Engineer/SRI-Delhi-Platform S/W 1 Team/Samsung Electronics Date : 2017-12-12 17:29 (GMT+5:30) Title :

RE: [PATCH v2] ftrace/module: Move ftrace_release_mod to ddebug_cleanup label

  Hello Steve, As per the discussion I sent patch v2. Please find. Thanks, Namit Gupta - Original Message - Sender : NAMIT GUPTA  ./Senior Chief Engineer/SRI-Delhi-Platform S/W 1 Team/Samsung Electronics Date : 2017-12-12 17:29 (GMT+5:30) Title : [PATCH v2] ftrace/module:

[PATCH net-next v6 5/6] net: dccp: Add DCCP sendmsg trace event

Add DCCP sendmsg trace event (dccp/dccp_probe) for replacing dccpprobe. User can trace this event via ftrace or perftools. Signed-off-by: Masami Hiramatsu --- Changes in v5 - Fix to add local directory to include for trace.h. Thanks Steven! --- net/dccp/Makefile |

[PATCH net-next v6 4/6] net: sctp: Remove debug SCTP probe module

Remove SCTP probe module since jprobe has been deprecated. That function is now replaced by sctp/sctp_probe and sctp/sctp_probe_path trace-events. You can use it via ftrace or perftools. Signed-off-by: Masami Hiramatsu --- net/sctp/Kconfig | 12 --- net/sctp/Makefile |

[PATCH net-next v6 1/6] net: tcp: Add trace events for TCP congestion window tracing

This adds an event to trace TCP stat variables with slightly intrusive trace-event. This uses ftrace/perf event log buffer to trace those state, no needs to prepare own ring-buffer, nor custom user apps. User can use ftrace to trace this event as below; # cd /sys/kernel/debug/tracing # echo

[PATCH net-next v6 5/6] net: dccp: Add DCCP sendmsg trace event

Add DCCP sendmsg trace event (dccp/dccp_probe) for replacing dccpprobe. User can trace this event via ftrace or perftools. Signed-off-by: Masami Hiramatsu --- Changes in v5 - Fix to add local directory to include for trace.h. Thanks Steven! --- net/dccp/Makefile |3 ++

[PATCH net-next v6 4/6] net: sctp: Remove debug SCTP probe module

Remove SCTP probe module since jprobe has been deprecated. That function is now replaced by sctp/sctp_probe and sctp/sctp_probe_path trace-events. You can use it via ftrace or perftools. Signed-off-by: Masami Hiramatsu --- net/sctp/Kconfig | 12 --- net/sctp/Makefile |3 -

[PATCH net-next v6 1/6] net: tcp: Add trace events for TCP congestion window tracing

This adds an event to trace TCP stat variables with slightly intrusive trace-event. This uses ftrace/perf event log buffer to trace those state, no needs to prepare own ring-buffer, nor custom user apps. User can use ftrace to trace this event as below; # cd /sys/kernel/debug/tracing # echo

Re: [Ocfs2-devel] [PATCH] ocfs2: try a blocking lock before return AOP_TRUNCATED_PAGE

On 2017/12/28 10:48, Gang He wrote: > Hi Alex, > > >> Hi Gang, >> >> On 2017/12/27 18:37, Gang He wrote: >>> Hi Jun, >>> >>> >> Hi Gang, Do you mean that too many retrys in loop cast losts of CPU-time and block page-fault interrupt? We should not add any delay in

[PATCH net-next v6 2/6] net: tcp: Remove TCP probe module

Remove TCP probe module since jprobe has been deprecated. That function is now replaced by tcp/tcp_probe trace-event. You can use it via ftrace or perftools. Signed-off-by: Masami Hiramatsu --- net/Kconfig | 17 --- net/ipv4/Makefile|1

[PATCH net-next v6 2/6] net: tcp: Remove TCP probe module

Remove TCP probe module since jprobe has been deprecated. That function is now replaced by tcp/tcp_probe trace-event. You can use it via ftrace or perftools. Signed-off-by: Masami Hiramatsu --- net/Kconfig | 17 --- net/ipv4/Makefile|1 net/ipv4/tcp_probe.c | 301

Re: [Ocfs2-devel] [PATCH] ocfs2: try a blocking lock before return AOP_TRUNCATED_PAGE

On 2017/12/28 10:48, Gang He wrote: > Hi Alex, > > >> Hi Gang, >> >> On 2017/12/27 18:37, Gang He wrote: >>> Hi Jun, >>> >>> >> Hi Gang, Do you mean that too many retrys in loop cast losts of CPU-time and block page-fault interrupt? We should not add any delay in

[PATCH net-next v6 6/6] net: dccp: Remove dccpprobe module

Remove DCCP probe module since jprobe has been deprecated. That function is now replaced by dccp/dccp_probe trace-event. You can use it via ftrace or perftools. Signed-off-by: Masami Hiramatsu --- Changes in v5: - Fix a conflict with previous change in Makefile. ---

[PATCH net-next v6 3/6] net: sctp: Add SCTP ACK tracking trace event

Add SCTP ACK tracking trace event to trace the changes of SCTP association state in response to incoming packets. It is used for debugging SCTP congestion control algorithms, and will replace sctp_probe module. Note that this event a bit tricky. Since this consists of 2 events (sctp_probe and

[PATCH net-next v6 6/6] net: dccp: Remove dccpprobe module

Remove DCCP probe module since jprobe has been deprecated. That function is now replaced by dccp/dccp_probe trace-event. You can use it via ftrace or perftools. Signed-off-by: Masami Hiramatsu --- Changes in v5: - Fix a conflict with previous change in Makefile. --- net/dccp/Kconfig | 17

[PATCH net-next v6 3/6] net: sctp: Add SCTP ACK tracking trace event

Add SCTP ACK tracking trace event to trace the changes of SCTP association state in response to incoming packets. It is used for debugging SCTP congestion control algorithms, and will replace sctp_probe module. Note that this event a bit tricky. Since this consists of 2 events (sctp_probe and

[PATCH net-next v6 0/6] net: tcp: sctp: dccp: Replace jprobe usage with trace events

Hi, This series is v6 of the replacement of jprobe usage with trace events. This version fixes trace/events/tcp.h to avoid sparse warning, as same as Mat Martineau's patch. Previous version is here; https://www.spinics.net/lists/netdev/msg474057.html Changes from v5: [1/6]: Avoid

[PATCH net-next v6 0/6] net: tcp: sctp: dccp: Replace jprobe usage with trace events

Hi, This series is v6 of the replacement of jprobe usage with trace events. This version fixes trace/events/tcp.h to avoid sparse warning, as same as Mat Martineau's patch. Previous version is here; https://www.spinics.net/lists/netdev/msg474057.html Changes from v5: [1/6]: Avoid

Re: [PATCH 2/2] staging: iio: add spaces around '-' operator

On Wed, 27 Dec 2017, Ji-Hun Kim wrote: > Clean up checkpatch warning: > CHECK: spaces preferred around that '-' (ctx:VxV) > > Signed-off-by: Ji-Hun Kim > --- > drivers/staging/iio/adc/ad7192.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git

Re: [PATCH 2/2] staging: iio: add spaces around '-' operator

On Wed, 27 Dec 2017, Ji-Hun Kim wrote: > Clean up checkpatch warning: > CHECK: spaces preferred around that '-' (ctx:VxV) > > Signed-off-by: Ji-Hun Kim > --- > drivers/staging/iio/adc/ad7192.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git

Re: [PATCH 4.14 00/74] 4.14.10-stable review

On 27 December 2017 at 22:15, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.10 release. > There are 74 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied,

Re: [PATCH 4.14 00/74] 4.14.10-stable review

On 27 December 2017 at 22:15, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.10 release. > There are 74 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > >

Re: [PATCH] pinctrl: spear: Delete an error message for a failed memory allocation in spear_pinctrl_probe()

On 27-12-17, 22:48, SF Markus Elfring wrote: > From: Markus Elfring > Date: Wed, 27 Dec 2017 22:44:04 +0100 > > Omit an extra message for a memory allocation failure in this function. > > This issue was detected by using the Coccinelle software. > >

Re: [PATCH] pinctrl: spear: Delete an error message for a failed memory allocation in spear_pinctrl_probe()

On 27-12-17, 22:48, SF Markus Elfring wrote: > From: Markus Elfring > Date: Wed, 27 Dec 2017 22:44:04 +0100 > > Omit an extra message for a memory allocation failure in this function. > > This issue was detected by using the Coccinelle software. > > Signed-off-by: Markus Elfring > --- >

Re: [PATCH] pinctrl/spear/plgpio: Delete two error messages for a failed memory allocation in plgpio_probe()

On 27-12-17, 22:39, SF Markus Elfring wrote: > From: Markus Elfring > Date: Wed, 27 Dec 2017 22:34:28 +0100 > > Omit extra messages for a memory allocation failure in this function. > > This issue was detected by using the Coccinelle software. > > Signed-off-by:

Re: [PATCH] pinctrl/spear/plgpio: Delete two error messages for a failed memory allocation in plgpio_probe()

On 27-12-17, 22:39, SF Markus Elfring wrote: > From: Markus Elfring > Date: Wed, 27 Dec 2017 22:34:28 +0100 > > Omit extra messages for a memory allocation failure in this function. > > This issue was detected by using the Coccinelle software. > > Signed-off-by: Markus Elfring > --- >

DIRECTOR IN CHARGE: DR.PATRICE TEME

UN Visitor Centre Department of Public Information United Nations Headquarters Room DHL-1B-154 New York, NY 10017 E-mail:un...@teewars.org United Nations Compensation Unit, In Affiliation with World Bank Our Ref: UN/WBO/042UK/2017. Congratulations Beneficiary, How are you today? Hope all is

DIRECTOR IN CHARGE: DR.PATRICE TEME

UN Visitor Centre Department of Public Information United Nations Headquarters Room DHL-1B-154 New York, NY 10017 E-mail:un...@teewars.org United Nations Compensation Unit, In Affiliation with World Bank Our Ref: UN/WBO/042UK/2017. Congratulations Beneficiary, How are you today? Hope all is

Re: [PATCH] objtool: Fix clang enum conversion warning

On Wed, Dec 27, 2017 at 10:42:45PM -0500, Nick Desaulniers wrote: > On Wed, Dec 27, 2017 at 12:38 PM, Josh Poimboeuf wrote: > > On Wed, Dec 27, 2017 at 01:34:34PM +0100, Lukas Bulwahn wrote: > >> Assuming that the authorship of this one-line change does not matter, as it > >>

Re: [PATCH] objtool: Fix clang enum conversion warning

On Wed, Dec 27, 2017 at 10:42:45PM -0500, Nick Desaulniers wrote: > On Wed, Dec 27, 2017 at 12:38 PM, Josh Poimboeuf wrote: > > On Wed, Dec 27, 2017 at 01:34:34PM +0100, Lukas Bulwahn wrote: > >> Assuming that the authorship of this one-line change does not matter, as it > >> is largely suggested

Re: [f2fs-dev] [PATCH 1/2] f2fs: pass down write hints to block layer for bufferd write

Hi Jaegeuk, On 12/28/2017 12:26 PM, Jaegeuk Kim wrote: > On 12/23, Chao Yu wrote: >> On 2017/12/15 10:06, Jaegeuk Kim wrote: >>> On 12/14, Hyunchul Lee wrote: Hi Jaegeuk, I need your comment about the fs_iohint mount option. a) w/o fs_iohint, propagate user hints to low

Re: [f2fs-dev] [PATCH 1/2] f2fs: pass down write hints to block layer for bufferd write

Hi Jaegeuk, On 12/28/2017 12:26 PM, Jaegeuk Kim wrote: > On 12/23, Chao Yu wrote: >> On 2017/12/15 10:06, Jaegeuk Kim wrote: >>> On 12/14, Hyunchul Lee wrote: Hi Jaegeuk, I need your comment about the fs_iohint mount option. a) w/o fs_iohint, propagate user hints to low

Re: [PATCH v2] gpio: winbond: add driver

On Wed, Dec 27, 2017 at 07:42:21PM +0100, Maciej S. Szmigiero wrote: >On 27.12.2017 01:24, William Breathitt Gray wrote: >> On Mon, Dec 25, 2017 at 03:48:16PM +0100, Maciej S. Szmigiero wrote: >(..) >>> All the existing ISA bus drivers seem to depend on CONFIG_ISA_BUS_API >>> instead of selecting

Re: [PATCH v2] gpio: winbond: add driver

On Wed, Dec 27, 2017 at 07:42:21PM +0100, Maciej S. Szmigiero wrote: >On 27.12.2017 01:24, William Breathitt Gray wrote: >> On Mon, Dec 25, 2017 at 03:48:16PM +0100, Maciej S. Szmigiero wrote: >(..) >>> All the existing ISA bus drivers seem to depend on CONFIG_ISA_BUS_API >>> instead of selecting

Re: [PATCH V8 3/3] OPP: Allow "opp-hz" and "opp-microvolt" to contain magic values

On 27-12-17, 15:54, Rob Herring wrote: > On Wed, Dec 27, 2017 at 2:56 AM, Viresh Kumar wrote: > > On 26-12-17, 14:29, Rob Herring wrote: > >> On Mon, Dec 18, 2017 at 03:51:30PM +0530, Viresh Kumar wrote: > > > >> > +On some platforms the exact frequency or voltage may be

Re: [PATCH V8 3/3] OPP: Allow "opp-hz" and "opp-microvolt" to contain magic values

On 27-12-17, 15:54, Rob Herring wrote: > On Wed, Dec 27, 2017 at 2:56 AM, Viresh Kumar wrote: > > On 26-12-17, 14:29, Rob Herring wrote: > >> On Mon, Dec 18, 2017 at 03:51:30PM +0530, Viresh Kumar wrote: > > > >> > +On some platforms the exact frequency or voltage may be hidden from the > >> >

Re: [PATCH] Documentation: gpu/i915: rename intel_guc_loader.c

On Wed, Dec 27, 2017 at 08:19:49PM -0800, Randy Dunlap wrote: > https://marc.info/?l=dri-devel=151237442131113=2 > > Already applied to drm/ tree. Gotcha; cheers. -- Joey Pabalinas signature.asc Description: PGP signature

Re: [PATCH] Documentation: gpu/i915: rename intel_guc_loader.c

On Wed, Dec 27, 2017 at 08:19:49PM -0800, Randy Dunlap wrote: > https://marc.info/?l=dri-devel=151237442131113=2 > > Already applied to drm/ tree. Gotcha; cheers. -- Joey Pabalinas signature.asc Description: PGP signature

Re: [PATCH v2] gpio: winbond: add driver

On Wed, Dec 27, 2017 at 12:16:53PM +0100, Linus Walleij wrote: >On Wed, Dec 27, 2017 at 1:24 AM, William Breathitt Gray > wrote: > >> The issue seems to relate to the select GPIOLIB line for the STX104 >> Kconfig option (which has a ISA_BUS_API dependency). Switching

Re: [PATCH v2] gpio: winbond: add driver

On Wed, Dec 27, 2017 at 12:16:53PM +0100, Linus Walleij wrote: >On Wed, Dec 27, 2017 at 1:24 AM, William Breathitt Gray > wrote: > >> The issue seems to relate to the select GPIOLIB line for the STX104 >> Kconfig option (which has a ISA_BUS_API dependency). Switching GPIOLIB >> to be a dependency,

Re: [RFC PATCH bpf-next v2 1/4] tracing/kprobe: bpf: Check error injectable event is on function entry

On 12/27/17 8:16 PM, Steven Rostedt wrote: On Wed, 27 Dec 2017 19:45:42 -0800 Alexei Starovoitov wrote: I don't think that's the case. My reading of current trace_kprobe_ftrace() -> arch_check_ftrace_location() is that it will not be true for old mcount case. In the old mcount

Re: [RFC PATCH bpf-next v2 1/4] tracing/kprobe: bpf: Check error injectable event is on function entry

On 12/27/17 8:16 PM, Steven Rostedt wrote: On Wed, 27 Dec 2017 19:45:42 -0800 Alexei Starovoitov wrote: I don't think that's the case. My reading of current trace_kprobe_ftrace() -> arch_check_ftrace_location() is that it will not be true for old mcount case. In the old mcount case, you

Re: [RFC V7 2/2] OPP: Allow "opp-hz" and "opp-microvolt" to contain magic values

On 27-12-17, 15:36, Rob Herring wrote: > On Tue, Dec 26, 2017 at 10:45 PM, Viresh Kumar > wrote: > > On 26-12-17, 14:23, Rob Herring wrote: > >> > cpu_opp_table: cpu_opp_table { > >> > compatible = "operating-points-v2"; > >> >

Re: [RFC V7 2/2] OPP: Allow "opp-hz" and "opp-microvolt" to contain magic values

On 27-12-17, 15:36, Rob Herring wrote: > On Tue, Dec 26, 2017 at 10:45 PM, Viresh Kumar > wrote: > > On 26-12-17, 14:23, Rob Herring wrote: > >> > cpu_opp_table: cpu_opp_table { > >> > compatible = "operating-points-v2"; > >> > opp-shared; > >> > > >> >

Re: [PATCH 04/12] ext2: drop unneeded newline

On Wed, Dec 27, 2017 at 03:51:37PM +0100, Julia Lawall wrote: > ext2_msg prints a newline at the end of the message string, so the message > string does not need to include a newline explicitly. Done using > Coccinelle. > > Signed-off-by: Julia Lawall Reviewed-by:

Re: [PATCH 04/12] ext2: drop unneeded newline

On Wed, Dec 27, 2017 at 03:51:37PM +0100, Julia Lawall wrote: > ext2_msg prints a newline at the end of the message string, so the message > string does not need to include a newline explicitly. Done using > Coccinelle. > > Signed-off-by: Julia Lawall Reviewed-by: Theodore Ts'o

Re: [RFC PATCH v11 4/5] PCI / PM: Add support for the PCIe WAKE# signal for OF

* Rafael J. Wysocki [171228 00:51]: > On Wed, Dec 27, 2017 at 4:08 PM, Tony Lindgren wrote: > > * Rafael J. Wysocki [171227 01:00]: > >> On Tuesday, December 26, 2017 2:06:47 AM CET JeffyChen wrote: > >> > Hi Rafael, > >> > > >> > Thanks

Re: [RFC PATCH v11 4/5] PCI / PM: Add support for the PCIe WAKE# signal for OF

* Rafael J. Wysocki [171228 00:51]: > On Wed, Dec 27, 2017 at 4:08 PM, Tony Lindgren wrote: > > * Rafael J. Wysocki [171227 01:00]: > >> On Tuesday, December 26, 2017 2:06:47 AM CET JeffyChen wrote: > >> > Hi Rafael, > >> > > >> > Thanks for your reply :) > >> > > >> > On 12/26/2017 08:11 AM,

Re: [PATCH] Documentation: gpu/i915: rename intel_guc_loader.c

On 12/27/2017 07:28 PM, Joey Pabalinas wrote: > Commit e8668bbcb0f91c7baa ("drm/i915/guc: Rename intel_guc_loader.c to > intel_guc_fw.c") renamed drivers/gpu/drm/i915/intel_guc_loader.c > but didn't update Documentation/gpu/i915.rst. Change intel_guc_loader.c > to intel_guc_fw.c in

Re: [PATCH v3 bpf-next 2/2] tools/bpftool: fix bpftool build with bintutils >= 2.9

On Wed, 27 Dec 2017 19:16:29 +, Roman Gushchin wrote: > Bpftool build is broken with binutils version 2.29 and later. > The cause is commit 003ca0fd2286 ("Refactor disassembler selection") > in the binutils repo, which changed the disassembler() function > signature. > > Fix this by adding a

Re: [PATCH] Documentation: gpu/i915: rename intel_guc_loader.c

On 12/27/2017 07:28 PM, Joey Pabalinas wrote: > Commit e8668bbcb0f91c7baa ("drm/i915/guc: Rename intel_guc_loader.c to > intel_guc_fw.c") renamed drivers/gpu/drm/i915/intel_guc_loader.c > but didn't update Documentation/gpu/i915.rst. Change intel_guc_loader.c > to intel_guc_fw.c in

Re: [PATCH v3 bpf-next 2/2] tools/bpftool: fix bpftool build with bintutils >= 2.9

On Wed, 27 Dec 2017 19:16:29 +, Roman Gushchin wrote: > Bpftool build is broken with binutils version 2.29 and later. > The cause is commit 003ca0fd2286 ("Refactor disassembler selection") > in the binutils repo, which changed the disassembler() function > signature. > > Fix this by adding a

Re: [RFC PATCH bpf-next v2 1/4] tracing/kprobe: bpf: Check error injectable event is on function entry

On Wed, 27 Dec 2017 19:45:42 -0800 Alexei Starovoitov wrote: > I don't think that's the case. My reading of current > trace_kprobe_ftrace() -> arch_check_ftrace_location() > is that it will not be true for old mcount case. In the old mcount case, you can't use ftrace to return

Re: [RFC PATCH bpf-next v2 1/4] tracing/kprobe: bpf: Check error injectable event is on function entry

On Wed, 27 Dec 2017 19:45:42 -0800 Alexei Starovoitov wrote: > I don't think that's the case. My reading of current > trace_kprobe_ftrace() -> arch_check_ftrace_location() > is that it will not be true for old mcount case. In the old mcount case, you can't use ftrace to return without calling

Re: [Ocfs2-devel] [PATCH] ocfs2: try a blocking lock before return AOP_TRUNCATED_PAGE

Hi, On 12/27/2017 05:29 PM, Gang He wrote: If we can't get inode lock immediately in the function ocfs2_inode_lock_with_page() when reading a page, we should not return directly here, since this will lead to a softlockup problem. The method is to get a blocking lock and immediately unlock

Re: [Ocfs2-devel] [PATCH] ocfs2: try a blocking lock before return AOP_TRUNCATED_PAGE

Hi, On 12/27/2017 05:29 PM, Gang He wrote: If we can't get inode lock immediately in the function ocfs2_inode_lock_with_page() when reading a page, we should not return directly here, since this will lead to a softlockup problem. The method is to get a blocking lock and immediately unlock

Re: [RFC PATCH bpf-next v2 4/4] error-injection: Support fault injection framework

On 12/27/17 5:38 PM, Masami Hiramatsu wrote: On Wed, 27 Dec 2017 14:49:46 -0800 Alexei Starovoitov wrote: On 12/27/17 12:09 AM, Masami Hiramatsu wrote: On Tue, 26 Dec 2017 18:12:56 -0800 Alexei Starovoitov wrote: On Tue, Dec 26, 2017 at

Re: [RFC PATCH bpf-next v2 4/4] error-injection: Support fault injection framework

On 12/27/17 5:38 PM, Masami Hiramatsu wrote: On Wed, 27 Dec 2017 14:49:46 -0800 Alexei Starovoitov wrote: On 12/27/17 12:09 AM, Masami Hiramatsu wrote: On Tue, 26 Dec 2017 18:12:56 -0800 Alexei Starovoitov wrote: On Tue, Dec 26, 2017 at 04:48:25PM +0900, Masami Hiramatsu wrote: Support

Re: [RFC PATCH bpf-next v2 1/4] tracing/kprobe: bpf: Check error injectable event is on function entry

On 12/27/17 6:34 PM, Masami Hiramatsu wrote: On Wed, 27 Dec 2017 14:46:24 -0800 Alexei Starovoitov wrote: On 12/26/17 9:56 PM, Masami Hiramatsu wrote: On Tue, 26 Dec 2017 17:57:32 -0800 Alexei Starovoitov wrote: On Tue, Dec 26, 2017 at 04:46:59PM

Re: [RFC PATCH bpf-next v2 1/4] tracing/kprobe: bpf: Check error injectable event is on function entry

On 12/27/17 6:34 PM, Masami Hiramatsu wrote: On Wed, 27 Dec 2017 14:46:24 -0800 Alexei Starovoitov wrote: On 12/26/17 9:56 PM, Masami Hiramatsu wrote: On Tue, 26 Dec 2017 17:57:32 -0800 Alexei Starovoitov wrote: On Tue, Dec 26, 2017 at 04:46:59PM +0900, Masami Hiramatsu wrote: Check

Re: [PATCH] objtool: Fix clang enum conversion warning

On Wed, Dec 27, 2017 at 12:38 PM, Josh Poimboeuf wrote: > On Wed, Dec 27, 2017 at 01:34:34PM +0100, Lukas Bulwahn wrote: >> Assuming that the authorship of this one-line change does not matter, as it >> is largely suggested by the clang compiler anyway, and we want to move

Re: [PATCH] objtool: Fix clang enum conversion warning

On Wed, Dec 27, 2017 at 12:38 PM, Josh Poimboeuf wrote: > On Wed, Dec 27, 2017 at 01:34:34PM +0100, Lukas Bulwahn wrote: >> Assuming that the authorship of this one-line change does not matter, as it >> is largely suggested by the clang compiler anyway, and we want to move the >> change forward,

[PATCH -next] xen/pvcalls: use GFP_ATOMIC under spin lock

A spin lock is taken here so we should use GFP_ATOMIC. Fixes: 9774c6cca266 ("xen/pvcalls: implement accept command") Signed-off-by: Wei Yongjun --- drivers/xen/pvcalls-front.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/xen/pvcalls-front.c

[PATCH -next] xen/pvcalls: use GFP_ATOMIC under spin lock

A spin lock is taken here so we should use GFP_ATOMIC. Fixes: 9774c6cca266 ("xen/pvcalls: implement accept command") Signed-off-by: Wei Yongjun --- drivers/xen/pvcalls-front.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/xen/pvcalls-front.c

  1   2   3   4   5   6   7   8   9   10   >