Re: [PATCH 3/7] RISC-V: Rework kernel's virtual address space mapping

On Wed, 27 Mar 2019 14:36:39 PDT (-0700), log...@deltatee.com wrote: The motivation for this is to support P2P transactions. P2P requires having struct pages for IO memory which means the linear mapping must be able to cover all of the IO regions. Unfortunately with Sv39 we are not able to cover

Re: [PATCH v3 3/4] driver core: add dev_print_hex_dump() logging function.

On Wed, Mar 27, 2019 at 05:28:17PM -0700, Life is hard, and then you die wrote: > > On Wed, Mar 27, 2019 at 11:37:57AM +0900, Greg Kroah-Hartman wrote: > > On Tue, Mar 26, 2019 at 06:48:06PM -0700, Ronald Tschalär wrote: > > > This is the dev_xxx() analog to print_hex_dump(), using dev_printk() >

Re: [PATCH 3.18 132/134] rcu: Do RCU GP kthread self-wakeup from softirq and interrupt

On Thu, Mar 28, 2019 at 01:36:12AM +, Zhang, Jun wrote: > Hello, Paul > > Yes, I only use original V3.18.136 to test. Because system run very slowly, I > give up. > > Device: NUC (made in 2017) > OS:ubuntu 16.04 > Kernel: V3.18.136 (come from >

Re: WARNING in arch_install_hw_breakpoint

On Wed, Mar 27, 2019 at 06:48:41PM +0100, Borislav Petkov wrote: > On Wed, Mar 27, 2019 at 04:17:25PM +0100, Borislav Petkov wrote: > Ok, after adding some debug output, it looks like this (newlines mine): > > [ 200.921625][ T8029]repro-80290d..4 200923254us : >

Re: [PATCH v5 0/9] Mediatek MT8183 clock support

On Tue, 2019-03-05 at 13:05 +0800, Weiyi Lu wrote: Hi Stephen, Just gentle ping. Many thanks. > Resend clock patches from v4 based on v5.0-rc1. > > The whole series now is composed of > a fix for PLL tuner (PATCH 1), > clock common changes for both MT8183 & MT6765 (PATCH 2-3), > clock support

[PATCH v2] arch_topology: Make cpu_capacity sysfs node as ready-only

If user updates any cpu's cpu_capacity, then the new value is going to be applied to all its online sibling cpus. But this need not to be correct always, as sibling cpus (in ARM, same micro architecture cpus) would have different cpu_capacity with different performance characteristics. So,

Re: [PATCH v13 10/11] gpio: 74x164: Utilize the for_each_set_clump8 macro

On Wed, Mar 27, 2019 at 02:33:14PM +0200, Andy Shevchenko wrote: > On Wed, Mar 27, 2019 at 02:02:39PM +0900, William Breathitt Gray wrote: > > Replace verbose implementation in set_multiple callback with > > for_each_set_clump8 macro to simplify code and improve clarity. > > > +

Re: [PATCH v3 3/3] Drivers: hv: vmbus: Fix race condition with new ring_buffer_info mutex

On Thu, Mar 21, 2019 at 04:04:20PM +, Michael Kelley wrote: > From: Kimberly Brown Sent: Wednesday, March 20, 2019 > 8:48 PM > > > > > Adding more locks will solve the problem but it seems like overkill. > > > > > Why not either use a reference count or an RCU style access for the > > > > >

Re: [PATCH v13 01/11] bitops: Introduce the for_each_set_clump8 macro

On Wed, Mar 27, 2019 at 07:42:54AM +0100, Lukas Wunner wrote: > On Wed, Mar 27, 2019 at 01:58:45PM +0900, William Breathitt Gray wrote: > > This macro iterates for each 8-bit group of bits (clump) with set bits, > > within a bitmap memory region. For each iteration, "start" is set to the > > bit

linux-next: Tree for Mar 28

Hi all, Changes since 20190327: The sound-asoc tree lost its build failure. The drm-intel tree lost its build failure. The pidfd tree gained build failures so I used the version from next-20190327. Non-merge commits (relative to Linus' tree): 3408 2961 files changed, 96322 insertions

RE: [PATCH v19,RESEND 24/27] x86/vdso: Add __vdso_sgx_enter_enclave() to wrap SGX enclave transitions

Hi Andy, > From: linux-sgx-ow...@vger.kernel.org [mailto:linux-sgx- > ow...@vger.kernel.org] On Behalf Of Andy Lutomirski > > I suppose the real question is: are there a significant number of > users who will want to run enclaves created using an old SDK on Linux? > And will there actually be

[PATCH 0/2] mtd: physmap: Using gpio-addrs

I have a system with ADDR24 of the flash chip connected to a gpio pin. This series fixes a bug in physmap-core.c and adds an example for using gpio-addrs to the dt-binding based on the system I'm using. Chris Packham (2): mtd: maps: physmap: Store gpio_values correctly dt-binding: mtd:

[PATCH 1/2] mtd: maps: physmap: Store gpio_values correctly

When the gpio-addr-flash.c driver was merged with physmap-core.c the code to store the current gpio_values was lost. This meant that once a gpio was asserted it was never de-asserted. Fix this by storing the current offset in gpio_values like the old driver used to. Fixes: commit ba32ce95cbd9

[PATCH 2/2] dt-binding: mtd: physmap: Add example using addr-gpios property

Add an example showing how to use the addr-gpios property to deal with a system with limited IO space. Cc: devicet...@vger.kernel.org Signed-off-by: Chris Packham --- .../devicetree/bindings/mtd/mtd-physmap.txt | 16 1 file changed, 16 insertions(+) diff --git

Re: [PATCH 4/6] x86, mm: make split_mem_range() more easy to read

On Sun, Mar 24, 2019 at 03:29:04PM +0100, Thomas Gleixner wrote: >Wei, > >On Tue, 12 Feb 2019, Wei Yang wrote: >> >> This patch changes the implementation from the first perception to the >> second to reduce one different handling on end_pfn. After doing so, the >> code is easier to read. > >It's

[PATCH v2] tty:serial_core: Spelling mistake

fix spelling mistake "overriden" -> "overridden" This fix resolves warning reported by checkpatch tool. Signed-off-by: Hariprasad Kelam --- Changes in V2: -Make commit message more clear --- drivers/tty/serial/serial_core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

Re: linux-next: build warning after merge of the phy-next tree

Hi Stephen, Thanks for the notice. I sent patch to fix this warning. https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1964942.html Regards, Srinath. On Thu, Mar 28, 2019 at 5:59 AM Stephen Rothwell wrote: > > Hi Kishon, > > After merging the phy-next tree, today's linux-next build

[GIT PULL] ARM: SoC fixes for v5.1

The following changes since commit 8c2ffd9174779014c3fe1f96d9dc3641d9175f00: Linux 5.1-rc2 (2019-03-24 14:02:26 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git tags/armsoc-fixes for you to fetch changes up to

Re: [PATCH] Convert struct pid count to refcount_t

On Thu, Mar 28, 2019 at 3:34 AM Joel Fernandes wrote: > On Thu, Mar 28, 2019 at 01:59:45AM +0100, Jann Horn wrote: > > On Thu, Mar 28, 2019 at 1:06 AM Kees Cook wrote: > > > On Wed, Mar 27, 2019 at 7:53 AM Joel Fernandes (Google) > > > wrote: > > > > > > > > struct pid's count is an atomic_t

Re: linux-next: build failure after merge of the pidfd tree

Hi Christian, On Thu, 28 Mar 2019 03:28:25 +0100 Christian Brauner wrote: > > Sorry about that. Should be fixed now. Thanks. -- Cheers, Stephen Rothwell pgp1SaIC5hwdu.pgp Description: OpenPGP digital signature

[PATCH kselftest-next] selftests: cgroup: fix cleanup path in test_memcg_subtree_control()

Dan reported, that cleanup path in test_memcg_subtree_control() triggers a static checker warning: ./tools/testing/selftests/cgroup/test_memcontrol.c:76 \ test_memcg_subtree_control() error: uninitialized symbol 'child2'. Fix this by initializing child2 and parent2 variables and split the

RE: Issues with i.MX SPI DMA transfers

> From: Igor Plyatov [mailto:plya...@gmail.com] > > Dear developers, > > please, help to resolve two issues with SPI DMA transfers at i.MX6Q platform. > > First issue is >  [ 4465.008003] spi_master spi0: I/O Error in DMA RX > > Second issue is duplication for one of received bytes. > Copy

[PATCH v3 1/2] dt-bindings: arm: coresight: Support static funnel

Document DT binding for static (non-configurable) funnel and give an example for it. Cc: Mathieu Poirier Cc: Suzuki K Poulose Cc: Wanglai Shi Signed-off-by: Leo Yan --- .../devicetree/bindings/arm/coresight.txt | 45 +-- 1 file changed, 42 insertions(+), 3 deletions(-)

[PATCH v3 2/2] coresight: funnel: Support static funnel

Since CoreSight hardware topology can use a 'hidden' funnel in the trace data path, this kind funnel doesn't have register for accessing and is used by default from hardware design perspective. Below is an example for related hardware topology: +--+ +--+ | cpu0 |->| ETM |-\

[PATCH v3 0/2] CoreSight: Support static funnel

Since before there have no platforms use static funnel in mainline kernel (though maybe some in-house SoC has used it but didn't upstream for mainline kernel yet so we don't be aware for it), when enable CoreSight DT binding for hikey960, we found the SoC uses the static funnel in the link path

Re: [PATCH] Convert struct pid count to refcount_t

On Thu, Mar 28, 2019 at 01:59:45AM +0100, Jann Horn wrote: > On Thu, Mar 28, 2019 at 1:06 AM Kees Cook wrote: > > On Wed, Mar 27, 2019 at 7:53 AM Joel Fernandes (Google) > > wrote: > > > > > > struct pid's count is an atomic_t field used as a refcount. Use > > > refcount_t for it which is

RE: [PATCH v2 2/2] arm64: dts: imx8qxp: Add EDMA0/EDMA1 nodes

> From: Daniel Baluta > Sent: Thursday, March 28, 2019 3:03 AM > > i.MX8QXP contains a total of 4 EDMA controllers of which two are primarily > for audio components and the other two are for non-audio periperhals. > > This patch adds the EDMA0/EDMA1 nodes used by audio peripherals. > > EDMA0

Re: linux-next: build failure after merge of the pidfd tree

ion it appears in > >Caused by commit > > 9170fba40db0 ("pid: add pidfd_open()") > >I have used the version of the pifd tree from next-20190327 for today. > >Please do *not* use linux-next as a development tree (I have seen >several >different version of this cod

[PATCH v3 09/12] soc: mediatek: cmdq: add polling function

add polling function in cmdq helper functions Signed-off-by: Bibby Hsieh --- drivers/soc/mediatek/mtk-cmdq-helper.c | 30 ++ include/linux/mailbox/mtk-cmdq-mailbox.h | 1 + include/linux/soc/mediatek/mtk-cmdq.h| 15 +++ 3 files changed, 46

[PATCH v3 07/12] soc: mediatek: cmdq: clear the event in cmdq initial flow

GCE hardware stored event information in own internal sysram, if the initial value in those sysram is not zero value it will cause a situation that gce can wait the event immediately after client ask gce to wait event but not really trigger the corresponding hardware. In order to make sure that

[PATCH v3 05/12] soc: mediatek: cmdq: move the CMDQ_IRQ_MASK into cmdq driver data

The interrupt mask and thread number has positive correlation, so we move the CMDQ_IRQ_MASK into cmdq driver data and calculate it by thread number. Signed-off-by: Bibby Hsieh --- drivers/mailbox/mtk-cmdq-mailbox.c | 12 +++- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git

[PATCH v3 04/12] dt-binding: gce: add binding for gce subsys property

cmdq driver provide a function that get the relationship of sub system number from device node for client. add specification for #subsys-cells, mediatek,gce-subsys. Signed-off-by: Bibby Hsieh --- Documentation/devicetree/bindings/mailbox/mtk-gce.txt | 15 --- 1 file changed, 12

[PATCH v3 03/12] dt-binding: gce: add binding for gce event property

Client hardware would send event to GCE hardware, so #event-cells, mediatek,gce-event-names, mediatek,gce-events. present the event. Signed-off-by: Bibby Hsieh --- Documentation/devicetree/bindings/mailbox/mtk-gce.txt | 17 ++--- 1 file changed, 14 insertions(+), 3 deletions(-)

[PATCH v3 00/12] support gce on mt8183 platform

Changes since v2: - according to CK's review comment, change the property name and refine the parameter - change the patch's title - remove unused property from dt-binding and dts Changes since v1: - add prefix "cmdq" in the commit subject - add dt-binding document for get event and

[PATCH v3 01/12] dt-binding: gce: remove thread-num property

"thread-num" is an unused property so we remove it from example. Signed-off-by: Bibby Hsieh --- Documentation/devicetree/bindings/mailbox/mtk-gce.txt | 1 - 1 file changed, 1 deletion(-) diff --git a/Documentation/devicetree/bindings/mailbox/mtk-gce.txt

[PATCH v3 02/12] dt-binding: gce: add gce header file for mt8183

Add documentation for the mt8183 gce. Add gce header file defined the gce hardware event, subsys number and constant for mt8183. Signed-off-by: Bibby Hsieh Reviewed-by: Rob Herring --- .../devicetree/bindings/mailbox/mtk-gce.txt| 6 +- include/dt-bindings/gce/mt8183-gce.h

[PATCH v3 12/12] arm64: dts: add gce node for mt8183

add gce device node for mt8183 Signed-off-by: Bibby Hsieh --- arch/arm64/boot/dts/mediatek/mt8183.dtsi | 12 1 file changed, 12 insertions(+) diff --git a/arch/arm64/boot/dts/mediatek/mt8183.dtsi b/arch/arm64/boot/dts/mediatek/mt8183.dtsi index 165b859..0301bd9 100644 ---

[PATCH v3 11/12] soc: mediatek: cmdq: add cmdq_dev_get_event function

When client ask gce to clear or wait for event, client need to pass event number to the API. We suggest client store the event information in device node, so we provide an API for client parse the event property. Signed-off-by: Bibby Hsieh --- drivers/soc/mediatek/mtk-cmdq-helper.c | 32

[PATCH v3 06/12] soc: mediatek: cmdq: support mt8183 gce function

add mt8183 compatible name for supporting gce function Signed-off-by: Bibby Hsieh --- drivers/mailbox/mtk-cmdq-mailbox.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/mailbox/mtk-cmdq-mailbox.c b/drivers/mailbox/mtk-cmdq-mailbox.c index 87617dc..6db1e2d 100644 ---

[PATCH v3 08/12] soc: mediatek: cmdq: add packet encoder function

Implement a function can encode the GCE instructions Signed-off-by: Bibby Hsieh --- drivers/soc/mediatek/mtk-cmdq-helper.c | 125 ++- include/linux/mailbox/mtk-cmdq-mailbox.h | 2 + include/linux/soc/mediatek/mtk-cmdq.h| 14 ++-- 3 files changed, 99

[PATCH v3 10/12] soc: mediatek: cmdq: add cmdq_dev_get_subsys function

GCE cannot know the register base address, this function can help cmdq client to get the relationship of subsys and register base address. Signed-off-by: Bibby Hsieh --- drivers/soc/mediatek/mtk-cmdq-helper.c | 25 + include/linux/soc/mediatek/mtk-cmdq.h | 18

Re: [PATCH v2] staging: rtl8723bs: core: fix line over 80 characters warning

On Wed, 2019-03-27 at 23:49 +0530, Anirudh Rayabharam wrote: > Checkpatch.pl complains that these lines are over 80 characters. Use the > "psecuritypriv" pointer for consistency, remove unnecessary parantheses > and fix the alignment. > > This patch just cleans up a condition, it doesn't affect

RE: [PATCHv4 16/28] PCI: mobiveil: refactor Mobiveil PCIe Host Bridge IP driver

Hi Lorenzo, Thanks a lot for your comments! > -Original Message- > From: Lorenzo Pieralisi > Sent: 2019年3月28日 1:39 > To: Z.q. Hou > Cc: linux-...@vger.kernel.org; linux-arm-ker...@lists.infradead.org; > devicet...@vger.kernel.org; linux-kernel@vger.kernel.org; > bhelg...@google.com;

Re: linux-next: build warning after merge of the rtc tree

On Thu, 28 Mar 2019 at 01:59, Alexandre Belloni wrote: > > On 28/03/2019 01:36:21+, Joel Stanley wrote: > > On Thu, 28 Mar 2019 at 01:23, Stephen Rothwell > > wrote: > > > > > > Hi all, > > > > > > After merging the rtc tree, today's linux-next build (x86_64 allmodconfig) > > > produced

Re: [RFC PATCH 0/10] Another Approach to Use PMEM as NUMA Node

On 3/27/19 1:09 PM, Michal Hocko wrote: On Wed 27-03-19 11:59:28, Yang Shi wrote: On 3/27/19 10:34 AM, Dan Williams wrote: On Wed, Mar 27, 2019 at 2:01 AM Michal Hocko wrote: On Tue 26-03-19 19:58:56, Yang Shi wrote: [...] It is still NUMA, users still can see all the NUMA nodes. No,

Re: [PATCH v2] staging: rtl8723bs: core: fix line over 80 characters warning

Thanks! Reviewed-by: Dan Carpenter regards, dan carpenter

linux-next: build failure after merge of the pidfd tree

undeclared identifier is reported only once for each function it appears in Caused by commit 9170fba40db0 ("pid: add pidfd_open()") I have used the version of the pifd tree from next-20190327 for today. Please do *not* use linux-next as a development tree (I have seen several differe

Re: [PATCH net-next v5 04/22] ethtool: move to its own directory

On 3/25/2019 10:08 AM, Michal Kubecek wrote: > The ethtool netlink interface is going to be split into multiple files so > that it will be more convenient to put all of them in a separate directory > net/ethtool. Start by moving current ethtool.c with ioctl interface into > this directory and

Re: linux-next: build warning after merge of the rtc tree

On 28/03/2019 01:36:21+, Joel Stanley wrote: > On Thu, 28 Mar 2019 at 01:23, Stephen Rothwell wrote: > > > > Hi all, > > > > After merging the rtc tree, today's linux-next build (x86_64 allmodconfig) > > produced this warning: > > > > drivers/rtc/rtc-aspeed.c: In function

[PATCH -mmots] initramfs: fix a compilation error

The commit 754006569c54 ("initramfs: cleanup populate_rootfs") introduced a compilation error with CONFIG_BLK_DEV_RAM != y due to clean_rootfs() is only declared with CONFIG_BLK_DEV_RAM=y. init/initramfs.c: In function 'populate_rootfs': init/initramfs.c:659:3: error: implicit declaration of

Re: linux-next: build warning after merge of the rtc tree

On Thu, 28 Mar 2019 at 01:23, Stephen Rothwell wrote: > > Hi all, > > After merging the rtc tree, today's linux-next build (x86_64 allmodconfig) > produced this warning: > > drivers/rtc/rtc-aspeed.c: In function 'aspeed_rtc_read_time': > drivers/rtc/rtc-aspeed.c:26:16: warning: unused variable

RE: [PATCH 3.18 132/134] rcu: Do RCU GP kthread self-wakeup from softirq and interrupt

Hello, Paul Yes, I only use original V3.18.136 to test. Because system run very slowly, I give up. Device: NUC (made in 2017) OS:ubuntu 16.04 Kernel: V3.18.136 (come from https://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18.136/) System can boot, but run very slowly, and couldn't

Re: INFO: task hung in evdev_release

syzbot has bisected this bug to: commit e32d99af6830c9a8f37b4f2637ef0cdc60fa79fb Author: Jerome Brunet Date: Tue Jul 17 15:42:50 2018 + ASoC: meson: add axg fifos DT binding documentation bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13fba69b20 start commit:

linux-next: build warning after merge of the rtc tree

Hi all, After merging the rtc tree, today's linux-next build (x86_64 allmodconfig) produced this warning: drivers/rtc/rtc-aspeed.c: In function 'aspeed_rtc_read_time': drivers/rtc/rtc-aspeed.c:26:16: warning: unused variable 'flags' [-Wunused-variable] unsigned long flags;

Re: [PATCH] misc/fastrpc: add checked value for dma_set_mask

On Thu, Mar 28, 2019 at 2:29 AM Greg KH wrote: > > On Mon, Mar 18, 2019 at 10:05:19PM -0400, Bo YU wrote: > > There be should check return value from dma_set_mask to throw some infos > > if fail to set dma mask. > > > > Detected by CoverityScan, CID# 1443983: Error handling issues > >

Re: [PATCH] Convert struct pid count to refcount_t

On Thu, Mar 28, 2019 at 1:06 AM Kees Cook wrote: > On Wed, Mar 27, 2019 at 7:53 AM Joel Fernandes (Google) > wrote: > > > > struct pid's count is an atomic_t field used as a refcount. Use > > refcount_t for it which is basically atomic_t but does additional > > checking to prevent use-after-free

Re: [PATCH] trace/page_ref: print out the page migratetype name

On Wed, Mar 27, 2019 at 09:24:22AM -0400, Steven Rostedt wrote: > On Wed, 27 Mar 2019 13:09:37 +0800 > Huang Shijie wrote: > > > Print out the page migratetype name which is more readable. > > Except that it breaks perf and trace-cmd, as they wont know what a > migratetype_names array contains.

Re: pick_next_task() picking the wrong task [v4.9.163]

On Sat, 2019-03-23 at 11:15 +0100, Peter Zijlstra wrote: > On Fri, Mar 22, 2019 at 05:57:59PM -0400, Radu Rendec wrote: > > Hi Everyone, > > > > I believe I'm seeing a weird behavior of pick_next_task() where it > > chooses a lower priority task over a higher priority one. The scheduling > >

Re: [RFC PATCH 01/68] kbuild: skip sub-make for in-tree build with GNU Make 4.x

David, On Thu, Mar 28, 2019 at 8:41 AM David Howells wrote: > > From: Masahiro Yamada > > Commit 2b50f7ab6368 ("kbuild: add workaround for Debian make-kpkg") > annoyed people who want to wrap the top Makefile with GNUmakefile > or something in order to customize it for their use. > > On second

Re: [PATCH AUTOSEL 5.0 152/262] x86/kprobes: Prohibit probing on IRQ handlers directly

Hi Sasha, Could you drop this? This prevents probing too much functions, and we will drop it from upstream. Anyway, commit a50480cb6d61 ("kprobes/x86: Blacklist non-attachable interrupt functions") fixes same issue. So please pick it instead of this. Thank you, On Wed, 27 Mar 2019 14:00:07

Re: [PATCH] drivers/acpi: Clear status of an event before enabling it

On Wed, Mar 27, 2019 at 5:24 AM Rafael J. Wysocki wrote: > > On Thu, Mar 21, 2019 at 3:16 AM Furquan Shaikh wrote: > > > > On Wed, Mar 20, 2019 at 5:11 PM Rafael J. Wysocki wrote: > > > > > > On Wed, Mar 20, 2019 at 11:34 PM Furquan Shaikh > > > wrote: > > > > > > > > Commit 18996f2db918

Investment Proposal.

Greetings, We are consultancy firm situated in Bahrain currently looking to finance new or existing projects in any industry. Currently we are sourcing for investment opportunities for our review and consideration and we provide financial and strategic advisory services to growing companies

Re: [PATCH 2/4] pid: add pidfd_open()

pidfd_open is open pidfd for pid relative to pidns, so a better analogy is that it is like openat for a relative pathname wrt dirfd. O_DIRECTORY is analogous to what type of object, so a TIDFD flag in the future which interprets pid (pathname) as thread id only and pins that specific struct pid.

Re: [PATCH] tracing: fix potential null pointer dereference on rctr_end

I just found this in the depths of my inbox (which is now managed by a local Patchwork system, so no more lost patches!) On Thu, 27 Sep 2018 23:47:00 +0100 Colin King wrote: > From: Colin Ian King > > Currently rctr_end may assigned null if strchr() fails leading to > a null pointer

Re: [PATCH v3 2/4] lib/hexdump.c: factor out generic hexdump formatting for reuse.

On Wed, Mar 27, 2019 at 09:46:48AM +0200, Andy Shevchenko wrote: > On Wed, Mar 27, 2019 at 3:49 AM Ronald Tschalär wrote: > > > > This introduces print_hex_dump_to_cb() which contains all the hexdump > > formatting minus the actual printk() call, allowing an arbitrary print > > function to be

linux-next: build warning after merge of the phy-next tree

Hi Kishon, After merging the phy-next tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: In file included from include/linux/phy/phy.h:19, from drivers/phy/broadcom/phy-bcm-sr-usb.c:10: drivers/phy/broadcom/phy-bcm-sr-usb.c: In function

Re: [PATCH v3 3/4] driver core: add dev_print_hex_dump() logging function.

On Wed, Mar 27, 2019 at 11:37:57AM +0900, Greg Kroah-Hartman wrote: > On Tue, Mar 26, 2019 at 06:48:06PM -0700, Ronald Tschalär wrote: > > This is the dev_xxx() analog to print_hex_dump(), using dev_printk() > > instead of straight printk() to match other dev_xxx() logging functions. > > --- > >

RE: [PATCH v4] HID: core: move Usage Page concatenation to Main item

Hi Nicolas, V4 looks good to me. Thanks, Terry >-Original Message- >Subject: [PATCH v4] HID: core: move Usage Page concatenation to Main item >

Re: [PATCH] ARM: dts: at91: Fix typo in ISC_D0 on PC9

On Mon, 11 Mar 2019 08:57:42 +0100, David Engraf wrote: > The function argument for the ISC_D0 on PC9 was incorrect. According to > the documentation it should be 'C' aka 3. > > Signed-off-by: David Engraf > --- > arch/arm/boot/dts/sama5d2-pinfunc.h | 2 +- > 1 file changed, 1 insertion(+), 1

Re: [PATCH 1/3] dt-bindings: ahci-fsl-qoriq: add ls1028a chip name to the list

On Mon, 11 Mar 2019 15:20:12 +0800, Peng Ma wrote: > Add ls1028a compatible to bindings documentation. > > Signed-off-by: Peng Ma > --- > depends on: > - http://patchwork.ozlabs.org/patch/1045217/ > > .../devicetree/bindings/ata/ahci-fsl-qoriq.txt |3 ++- > 1 files changed, 2

Re: [PATCH 4/6] x86, mm: make split_mem_range() more easy to read

On Thu, Mar 28, 2019 at 01:16:08AM +0100, Thomas Gleixner wrote: >Wei, > >On Wed, 27 Mar 2019, Wei Yang wrote: >> On Sun, Mar 24, 2019 at 03:29:04PM +0100, Thomas Gleixner wrote: >> >Note, it's a combo of changes (including your patch 1/6) and needs to be >> >split up. It would be nice if you have

Re: [RFC PATCH 57/68] vfs: Convert pstore to use the new mount API

On Wed, Mar 27, 2019 at 4:47 PM David Howells wrote: > > Convert the pstore filesystem to the new internal mount API as the old > one will be obsoleted and removed. This allows greater flexibility in > communication of mount parameters between userspace, the VFS and the > filesystem. > > See

Re: [PATCH v3 4/4] Input: add Apple SPI keyboard and trackpad driver.

On Wed, Mar 27, 2019 at 11:35:30AM +0200, Andy Shevchenko wrote: > On Tue, Mar 26, 2019 at 06:48:07PM -0700, Ronald Tschalär wrote: > > The keyboard and trackpad on recent MacBook's (since 8,1) and > > MacBookPro's (13,* and 14,*) are attached to an SPI controller instead > > of USB, as

Re: [PATCH 05/25] dt-bindings: leds: Add function and color properties

On Tue, Mar 12, 2019 at 05:43:11PM +0100, Jacek Anaszewski wrote: > On 3/11/19 6:24 PM, Jacek Anaszewski wrote: > > Dan, > > > > On 3/11/19 1:26 PM, Dan Murphy wrote: > > > On 3/10/19 1:28 PM, Jacek Anaszewski wrote: > > > > Introduce dedicated properties for conveying information about > > > >

Re: [PATCH v2 00/25] Add generic support for composing LED class device name

On Sun, Mar 10, 2019 at 07:28:11PM +0100, Jacek Anaszewski wrote: > Changes from v1: > > - improved led_parse_properties() to parse label property at first > and return immediately after parsing succeeds > - added tool get_led_device_info.sh for retrieving LED class device's > parent device

Re: [PATCH 4/6] x86, mm: make split_mem_range() more easy to read

Wei, On Wed, 27 Mar 2019, Wei Yang wrote: > On Sun, Mar 24, 2019 at 03:29:04PM +0100, Thomas Gleixner wrote: > >Note, it's a combo of changes (including your patch 1/6) and needs to be > >split up. It would be nice if you have time to split it up into separate > >patches, add proper changelogs

Re: [PATCH 04/25] dt-bindings: leds: Add LED_COLOR_NAME definitions

On Sun, Mar 10, 2019 at 07:28:15PM +0100, Jacek Anaszewski wrote: > Add common LED color name definitions for use in Device Tree. Do we actually have variations in color strings? Maybe someone uses "RED" or something. If not, I think this adds less value compared to function names. Just my 2

Re: [PATCH] Convert struct pid count to refcount_t

On Wed, Mar 27, 2019 at 7:53 AM Joel Fernandes (Google) wrote: > > struct pid's count is an atomic_t field used as a refcount. Use > refcount_t for it which is basically atomic_t but does additional > checking to prevent use-after-free bugs. No change in behavior if > CONFIG_REFCOUNT_FULL=n. > >

Re: [PATCH 03/25] dt-bindings: leds: Add LED_FUNCTION definitions

On Sun, Mar 10, 2019 at 07:28:14PM +0100, Jacek Anaszewski wrote: > Add common LED function definitions for use in Device Tree. > The function names were extracted from existing dts files > after eliminating oddities. I'd like this to be suggestions of what to use rather than what's already out

Re: [PATCH] power: reset: syscon-reboot: add a mask property

On Fri, Mar 08, 2019 at 08:49:30AM +0100, Martin Schiller wrote: > Make the syscon-reboot driver accept value and mask instead of > just value. > > Prior to this patch, the property name for the value was 'mask'. If > only the mask property is defined on a node, maintain compatibility > by using

[RFC PATCH 66/68] vfs: Convert ubifs to use the new mount API

Convert the ubifs filesystem to the new internal mount API as the old one will be obsoleted and removed. This allows greater flexibility in communication of mount parameters between userspace, the VFS and the filesystem. See Documentation/filesystems/mount_api.txt for more information.

[RFC PATCH 67/68] vfs: Convert orangefs to use the new mount API

Convert the orangefs filesystem to the new internal mount API as the old one will be obsoleted and removed. This allows greater flexibility in communication of mount parameters between userspace, the VFS and the filesystem. See Documentation/filesystems/mount_api.txt for more information. cc:

[RFC PATCH 64/68] vfs: Convert devpts to use the new mount API

Convert the devpts filesystem to the new internal mount API as the old one will be obsoleted and removed. This allows greater flexibility in communication of mount parameters between userspace, the VFS and the filesystem. See Documentation/filesystems/mount_api.txt for more information.

[RFC PATCH 62/68] vfs: Convert coda to use the new mount API

Convert the coda filesystem to the new internal mount API as the old one will be obsoleted and removed. This allows greater flexibility in communication of mount parameters between userspace, the VFS and the filesystem. See Documentation/filesystems/mount_api.txt for more information. Note this

[RFC PATCH 63/68] vfs: Convert autofs to use the new mount API

Convert the autofs filesystem to the new internal mount API as the old one will be obsoleted and removed. This allows greater flexibility in communication of mount parameters between userspace, the VFS and the filesystem. See Documentation/filesystems/mount_api.txt for more information.

[RFC PATCH 59/68] vfs: Convert hypfs to use the new mount API

Convert the hypfs filesystem to the new internal mount API as the old one will be obsoleted and removed. This allows greater flexibility in communication of mount parameters between userspace, the VFS and the filesystem. See Documentation/filesystems/mount_api.txt for more information.

[RFC PATCH 61/68] vfs: Kill mount_single()

Kill mount_single() as nothing now uses it. It has been replaced by vfs_get_super() keyed with vfs_get_single_super or vfs_get_single_reconf_super. Signed-off-by: David Howells --- Documentation/filesystems/vfs.txt |4 +-- fs/super.c| 55

[RFC PATCH 57/68] vfs: Convert pstore to use the new mount API

Convert the pstore filesystem to the new internal mount API as the old one will be obsoleted and removed. This allows greater flexibility in communication of mount parameters between userspace, the VFS and the filesystem. See Documentation/filesystems/mount_api.txt for more information.

[RFC PATCH 58/68] hypfs: Fix error number left in struct pointer member

In hypfs_fill_super(), if hypfs_create_update_file() fails, sbi->update_file is left holding an error number. This is passed to hypfs_kill_super() which doesn't check for this. Fix this by not setting sbi->update_value until after we've checked for error. Fixes: 24bbb1faf3f0 ("[PATCH]

[RFC PATCH 55/68] vfs: Convert debugfs to use the new mount API

Convert the debugfs filesystem to the new internal mount API as the old one will be obsoleted and removed. This allows greater flexibility in communication of mount parameters between userspace, the VFS and the filesystem. See Documentation/filesystems/mount_api.txt for more information.

[RFC PATCH 54/68] vfs: Add a single-or-reconfig keying to vfs_get_super()

Add an additional keying mode to vfs_get_super() to indicate that only a single superblock should exist in the system, and that, if it does, further mounts should invoke reconfiguration upon it. This allows mount_single() to be replaced. Signed-off-by: David Howells --- fs/super.c

[RFC PATCH 56/68] vfs: Convert tracefs to use the new mount API

Convert the tracefs filesystem to the new internal mount API as the old one will be obsoleted and removed. This allows greater flexibility in communication of mount parameters between userspace, the VFS and the filesystem. See Documentation/filesystems/mount_api.txt for more information.

Re: [PATCH 2/3] dt-bindings: clk: g12a-clkc: add PCIE PLL clock ID

On Thu, 7 Mar 2019 15:14:54 +0100, Neil Armstrong wrote: > Add a clock ID for the reference clock feeding the USB3+PCIe Combo PHY. > > Signed-off-by: Neil Armstrong > --- > include/dt-bindings/clock/g12a-clkc.h | 1 + > 1 file changed, 1 insertion(+) > Reviewed-by: Rob Herring

[RFC PATCH 52/68] vfs: Convert ceph to use the new mount API

Convert the ceph filesystem to the new internal mount API as the old one will be obsoleted and removed. This allows greater flexibility in communication of mount parameters between userspace, the VFS and the filesystem. See Documentation/filesystems/mount_api.txt for more information.

[RFC PATCH 41/68] vfs: Convert ramfs, shmem, tmpfs, devtmpfs, rootfs to use the new mount API

Convert the ramfs, shmem, tmpfs, devtmpfs and rootfs filesystems to the new internal mount API as the old one will be obsoleted and removed. This allows greater flexibility in communication of mount parameters between userspace, the VFS and the filesystem. See

[RFC PATCH 38/68] vfs: Convert securityfs to use the new mount API

Convert the securityfs filesystem to the new internal mount API as the old one will be obsoleted and removed. This allows greater flexibility in communication of mount parameters between userspace, the VFS and the filesystem. See Documentation/filesystems/mount_api.txt for more information.

[RFC PATCH 39/68] vfs: Convert selinuxfs to use the new mount API

Convert the selinuxfs filesystem to the new internal mount API as the old one will be obsoleted and removed. This allows greater flexibility in communication of mount parameters between userspace, the VFS and the filesystem. See Documentation/filesystems/mount_api.txt for more information.

[RFC PATCH 44/68] vfs: Convert fuse to use the new mount API

Convert the fuse filesystem to the new internal mount API as the old one will be obsoleted and removed. This allows greater flexibility in communication of mount parameters between userspace, the VFS and the filesystem. See Documentation/filesystems/mount_api.txt for more information. ---

[RFC PATCH 43/68] vfs: Make fs_parse() handle fs_param_is_fd-type params better

Make fs_parse() handle fs_param_is_fd-type parameters that are passed a string by converting it to an integer (in addition to handling direct fd specification). Also range check the integer. Signed-off-by: David Howells --- fs/fs_parser.c | 15 +-- 1 file changed, 13

[RFC PATCH 45/68] vfs: Move the subtype parameter into fuse

Move as much as possible of the mount subtype apparatus into the fuse driver. The bits that are left involve determining whether it's permitted to split the filesystem type string passed in to mount(2). Consequently, this means that we cannot get rid of the FS_HAS_SUBTYPE flag unless we define

  1   2   3   4   5   6   7   8   9   10   >