search for: yamada

Hi, This To field was not correct indexed by FTS. To: Yamada Taro <yamada at example.com>,=?UTF-8?B?dXNlcjJAZXhhbXBsZS5jb20=?= <user2 at example.com>, =?UTF-8?B?dXNlcjNAZXhhbXBsZS5jb20=?= <user3 at example.com>, user4 desu <user4 at example.com> --> Yamada Taro <yamada at example.com> , user2 at example.com And follow was...

...when passed message_address_parse(). So this debug logs came like following: Debug: @@@@@ befor address parse:uesr1 <user1 at example.com> Debug: @@@@@ after address parse:uesr1 <user1 at example.com> Debug: @@@@@ data:uesr1 <user1 at example.com> Debug: @@@@@ befor address parse:Yamada Taro <yamada at example.com>,user2 at example.com <user2 at example.com>, user3 at example.com <user3 at example.com>, user4 desu <user4 at example.com> Debug: @@@@@ after address parse:"Yamada Taro" <yamada at example.com>, <user2 at example.com> Debug...

Hi Dave, > -----Original Message----- > From: Dave Airlie [mailto:airlied at gmail.com] > Sent: Friday, April 26, 2019 11:19 AM > To: Yamada, Masahiro/山田 真弘 <yamada.masahiro at socionext.com> > Cc: David Airlie <airlied at linux.ie>; Daniel Vetter <daniel at ffwll.ch>; > dri-devel <dri-devel at lists.freedesktop.org>; nouveau > <nouveau at lists.freedesktop.org>; Sam Ravnborg <sam at ravnborg.or...

...rse(). > So this debug logs came like following: > > Debug: @@@@@ befor address parse:uesr1 <user1 at example.com> > Debug: @@@@@ after address parse:uesr1 <user1 at example.com> > Debug: @@@@@ data:uesr1 <user1 at example.com> > Debug: @@@@@ befor address parse:Yamada Taro <yamada at example.com>,user2 at example.com <user2 at example.com>, user3 at example.com <user3 at example.com>, user4 desu <user4 at example.com> > Debug: @@@@@ after address parse:"Yamada Taro" <yamada at example.com>, <user2 at example.com>...

Daniel, drm-misc-next-fixes? Dave. On Fri, 26 Apr 2019 at 12:25, <yamada.masahiro at socionext.com> wrote: > > Hi Dave, > > > -----Original Message----- > > From: Dave Airlie [mailto:airlied at gmail.com] > > Sent: Friday, April 26, 2019 11:19 AM > > To: Yamada, Masahiro/山田 真弘 <yamada.masahiro at socionext.com> > > Cc: Dav...

Hi. On Fri, Mar 29, 2019 at 8:37 PM Masahiro Yamada <yamada.masahiro at socionext.com> wrote: > > Currently, the Kbuild core manipulates header search paths in a crazy > way [1]. > > To fix this mess, I want all Makefiles to add explicit $(srctree)/ to > the search paths in the srctree. Some Makefiles are already written in &...

After long term efforts of fixing non-common clock implementations, clk_disable() is a no-op for a NULL pointer input, and this is now tree-wide consistent. All clock consumers can safely call clk_disable(_unprepare) without NULL pointer check. Signed-off-by: Masahiro Yamada <yamada.masahiro at socionext.com> --- drivers/gpu/drm/etnaviv/etnaviv_gpu.c | 15 +++++---------- drivers/gpu/drm/msm/mdp/mdp4/mdp4_kms.c | 6 ++---- drivers/gpu/drm/msm/mdp/mdp5/mdp5_kms.c | 3 +-- drivers/gpu/drm/msm/msm_gpu.c |...

On Sat, May 20, 2017 at 3:04 PM, Masahiro Yamada <yamada.masahiro at socionext.com> wrote: > 2017-05-21 2:58 GMT+09:00 Masahiro Yamada <yamada.masahiro at socionext.com>: >> After long term efforts of fixing non-common clock implementations, >> clk_disable() is a no-op for a NULL pointer input, and this is now >>...

...The goal of this work is to make the notation consistent, and finally get rid of the gross hacks. Having whitespaces after -I does not matter since commit 48f6e3cf5bc6 ("kbuild: do not drop -I without parameter"). [1]: https://patchwork.kernel.org/patch/9632347/ Signed-off-by: Masahiro Yamada <yamada.masahiro at socionext.com> Reviewed-by: Sam Ravnborg <sam at ravnborg.org> --- I put all gpu/drm changes into a single patch because they are trivial conversion. If you are interested in the big picture of this work, the full patch set is available at the following URL. git:/...

On Fri, 26 Apr 2019 at 11:46, Masahiro Yamada <yamada.masahiro at socionext.com> wrote: > > Hi. > > > On Fri, Mar 29, 2019 at 8:37 PM Masahiro Yamada > <yamada.masahiro at socionext.com> wrote: > > > > Currently, the Kbuild core manipulates header search paths in a crazy > > way [1]. > > &g...

...The goal of this work is to make the notation consistent, and finally get rid of the gross hacks. Having whitespaces after -I does not matter since commit 48f6e3cf5bc6 ("kbuild: do not drop -I without parameter"). [1]: https://patchwork.kernel.org/patch/9632347/ Signed-off-by: Masahiro Yamada <yamada.masahiro at socionext.com> --- I put all gpu/drm changes into a single patch because they are trivial conversion. Please let me know if I need to split this into per-driver patches. drivers/gpu/drm/amd/amdgpu/Makefile | 2 +- drivers/gpu/drm/amd/lib/Makefile | 2 +- drivers/gp...

2017-05-21 2:58 GMT+09:00 Masahiro Yamada <yamada.masahiro at socionext.com>: > After long term efforts of fixing non-common clock implementations, > clk_disable() is a no-op for a NULL pointer input, and this is now > tree-wide consistent. > > All clock consumers can safely call clk_disable(_unprepare) without > NU...

...annotate_reachable(), annotate_unreachable() Changes in v3: - Split into per-commit revert (per Nadav Amit) - Add some cleanups with preprocessor approach Changes in v2: - Revive clean-ups made by 5bdcd510c2ac (per Peter Zijlstra) - Fix commit quoting style (per Peter Zijlstra) Masahiro Yamada (12): Revert "x86/jump-labels: Macrofy inline assembly code to work around GCC inlining bugs" Revert "x86/cpufeature: Macrofy inline assembly code to work around GCC inlining bugs" Revert "x86/extable: Macrofy inline assembly code to work around GCC inlini...

...annotate_reachable(), annotate_unreachable() Changes in v3: - Split into per-commit revert (per Nadav Amit) - Add some cleanups with preprocessor approach Changes in v2: - Revive clean-ups made by 5bdcd510c2ac (per Peter Zijlstra) - Fix commit quoting style (per Peter Zijlstra) Masahiro Yamada (12): Revert "x86/jump-labels: Macrofy inline assembly code to work around GCC inlining bugs" Revert "x86/cpufeature: Macrofy inline assembly code to work around GCC inlining bugs" Revert "x86/extable: Macrofy inline assembly code to work around GCC inlini...

...inter position (x, y) upon keypress? In original wxWidgets, wxKeyEvent supports GetX() and GetY() methods, but wxRuby''s KeyEvent object does not have one. I also checked with event.methods and event.instance_variables. Do I need to keep track of pointer position by evt_motion? -- Taisuke Yamada <tyamadajp@spam.rakugaki.org>, http://rakugaki.org/ 2268 E9A2 D4F9 014E F11D 1DF7 DCA3 83BC 78E5 CD3A Message to my public address may not be handled in a timely manner. For a direct contact, please use my private address on my namecard.

On Wed, Dec 19, 2018 at 5:26 AM Nadav Amit <namit at vmware.com> wrote: > > > On Dec 17, 2018, at 8:03 AM, Masahiro Yamada <yamada.masahiro at socionext.com> wrote: > > > > This series reverts the in-kernel workarounds for inlining issues. > > > > The commit description of 77b0bf55bc67 mentioned > > "We also hope that GCC will eventually get fixed,..." > > > > N...

https://bugzilla.samba.org/show_bug.cgi?id=12173 Bug ID: 12173 Summary: memory leak around poptGetOptArg() Product: rsync Version: 3.0.6 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org Reporter:

...'t pass compilation > due to: tools/testing/radix-tree/idr.c:17: undefined reference to > WARN_ON_ONCE. This patch adds the bug.h header to idr.h to solve the > issue. Thanks; I sent this same patch out yesterday. Unfortunately, you didn't cc the author of this breakage, Masahiro Yamada. I want to highlight that these kinds of header cleanups are risky, and very low reward. I really don't want to see patches going all over the tree randomly touching header files. If we've got a real problem to solve, then sure. But I want to see a strong justification for any more heade...

...'t pass compilation > due to: tools/testing/radix-tree/idr.c:17: undefined reference to > WARN_ON_ONCE. This patch adds the bug.h header to idr.h to solve the > issue. Thanks; I sent this same patch out yesterday. Unfortunately, you didn't cc the author of this breakage, Masahiro Yamada. I want to highlight that these kinds of header cleanups are risky, and very low reward. I really don't want to see patches going all over the tree randomly touching header files. If we've got a real problem to solve, then sure. But I want to see a strong justification for any more heade...

On Sun, Dec 16, 2018 at 12:29 PM Nadav Amit <namit at vmware.com> wrote: > > > On Dec 15, 2018, at 6:50 PM, Masahiro Yamada <yamada.masahiro at socionext.com> wrote: > > > > Revert the following 9 commits: > > > > [1] 5bdcd510c2ac ("x86/jump-labels: Macrofy inline assembly code to > > work around GCC inlining bugs") > > > > This was partially reverted becau...