[PATCH v2 6/6] arm64: dts: ns2: Add USB3 Support

From: Yendapally Reddy Dhananjaya Reddy Add USB3 support to the Northstar2 Device tree files Signed-off-by: Yendapally Reddy Dhananjaya Reddy Signed-off-by: Jon Mason ---

[PATCH v2 2/6] dt-bindings: usb: Add documentation for NS2 CDRU USB3

Add documentation for CDRU USB3 registers available in NS2 SoC Signed-off-by: Jon Mason --- .../devicetree/bindings/usb/brcm,cdru-usb3-ctrl.txt| 14 ++ 1 file changed, 14 insertions(+) create mode 100644

RE: HELP DESK

Webmail Update 20GB 23GB Dear user Your mailbox has exceeded the storage limit of 20GB set by the administrator, you are currently running at 20.9 GB, you can not send or receive new messages until your verify you mailbox. to Re-validate your account CLICK

Re: [PATCH] security: fix description of values returned by cap_inode_need_killpriv

On Wed, Jul 26, 2017 at 02:31:08PM -0400, Stefan Berger wrote: > cap_inode_need_killpriv returns 1 if security.capability exists, > 0 otherwise. Fix the description of the return value to reflect this. > > Signed-off-by: Stefan Berger > --- > security/commoncap.c | 3

Re: [PATCH tip/core/rcu 02/15] rcu: Use timer as backstop for NOCB deferred wakeups

On Wed, 26 Jul 2017 14:47:41 -0700 "Paul E. McKenney" wrote: > > It is much lighter weight than a timer setup. > > How much lighter weight? In other words, what fraction of the > timers have to avoid being cancelled for irq_work to break even? No idea. I guess

Re: [PATCH v2 10/13] xen/pvcalls: implement poll command

On 07/25/2017 05:22 PM, Stefano Stabellini wrote: > For active sockets, check the indexes and use the inflight_conn_req > waitqueue to wait. > > For passive sockets, send PVCALLS_POLL to the backend. Use the > inflight_accept_req waitqueue if an accept is outstanding. Otherwise use > the

Re: [PATCH v2 04/13] xen/pvcalls: implement connect command

On Wed, 26 Jul 2017, Boris Ostrovsky wrote: > On 7/25/2017 5:22 PM, Stefano Stabellini wrote: > > Send PVCALLS_CONNECT to the backend. Allocate a new ring and evtchn for > > the active socket. > > > > Introduce a data structure to keep track of sockets. Introduce a > > waitqueue to allow the

linux-next: missing Signed-off-by in commit in the drm tree

Hi all, Commit 7d2818f54e38 ("drm/vc4: Allow vblank_disable_immediate on non-fw-kms. (v2)") is missing a Signed-off-by line for its commiter. -- Cheers, Stephen Rothwell

linux-next: Signed-off-by missing from a commit in the tip tree

Hi all, Commit 585d93c5ffcc ("perf annotate stdio: Fix --show-total-period") has no Signed-off-by for its author. -- Cheers, Stephen Rothwell

[PATCH][next] clk: ti: check for null return in strrchr to avoid null dereferencing

From: Colin Ian King strrchr can potentially return a null so the following strlen on the null pointer can cause a null dereference. Add a check to see if the string postfix is not null before calling strlen. Detected by CoverityScan, CID#1452039 ("Dereference null

Re: [PATCH] netpoll: Fix device name check in netpoll_setup()

From: Matthias Kaehlcke Date: Tue, 25 Jul 2017 11:36:25 -0700 > Apparently netpoll_setup() assumes that netpoll.dev_name is a pointer > when checking if the device name is set: > > if (np->dev_name) { > ... > > However the field is a character array, therefore the

[PATCH v2 1/5] PCI: mediatek: Add a structure to abstract the controller generations

From: Ryder Lee Introduce a structure "mtk_pcie_soc" to abstract the differences between controller generations, and the .startup() hook is used to encapsulate some SoC-dependent related setting. In doing so, the common code which will be reused by future chips. In

[PATCH v2 4/5] PCI: mediatek: Add new generation controller support

From: Ryder Lee Add support for new Gen2 controller which has two root ports and shares the probing flow with legacy controller. Currently this IP block can be found on MT7622/MT2712. Signed-off-by: Ryder Lee Signed-off-by: Honghui Zhang

[PATCH v2 3/5] dt-bindings: PCI: rename and cleanup MediaTek binding text

From: Ryder Lee In order to accommodate other SoC generations, this patch updates filename to make it more generic, regroups specific properties by SoCs, and removes redundant descriptions. Signed-off-by: Ryder Lee ---

[PATCH v2 5/5] dt-bindings: PCI: add support for new generation controller

From: Ryder Lee Add support for MediaTek new generation controller and update related properities. Signed-off-by: Ryder Lee Signed-off-by: Honghui Zhang --- .../devicetree/bindings/pci/mediatek-pcie.txt | 168

[PATCH v2 2/5] PCI: mediatek: switch to use platform_get_resource_byname()

From: Ryder Lee This is a transitional patch. We currently use platfarm_get_resource() for retrieving the IOMEM resources, but there might be some chips don't have subsys/shared registers part, which depends on platform design, and these will be introduced in further

Re: [PATCH 2/2] printk: Add boottime and real timestamps

Hi Prarit, [auto build test ERROR on linus/master] [also build test ERROR on v4.13-rc2] [cannot apply to next-20170726] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Prarit-Bhargava/printk

Re: [PATCH] turbostat: Running on virtual machine is not supported

Henrique, I like your suggestion, thanks! BTW. let's discuss (and patch) turbostat on linux-pm, rather than on lkml. thanks, -Len On Tue, Jul 25, 2017 at 11:59 AM, Henrique de Moraes Holschuh wrote: > On Tue, 25 Jul 2017, Prarit Bhargava wrote: >> A common way of determining

[PATCH v2 5/5] dt-bindings: PCI: add support for new generation controller

From: Ryder Lee Add support for MediaTek new generation controller and update related properities. Signed-off-by: Ryder Lee Signed-off-by: Honghui Zhang --- .../devicetree/bindings/pci/mediatek-pcie.txt | 168

Re: [PATCH 1/1] mm/hugetlb: Make huge_pte_offset() consistent and document behaviour

On 07/26/2017 06:34 AM, Punit Agrawal wrote: > Michal Hocko writes: > >> On Wed 26-07-17 14:33:57, Michal Hocko wrote: >>> On Wed 26-07-17 13:11:46, Punit Agrawal wrote: >> [...] I've been running tests from mce-test suite and libhugetlbfs for similar changes we did

[PATCH] staging: greybus: Remove unnecessary platform_set_drvdata

Unnecessary platform_set_drvdata() has been removed since the driver core clears the driver data to NULL after device release or on probe failure. There is no need to manually clear the device driver data to NULL. The Coccinelle semantic patch used to make this change is as follows: // @@ struct

Re: [PATCH v2 1/5] PCI: mediatek: Add a structure to abstract the controller generations

On Thu, 2017-07-27 at 10:58 +0800, honghui.zh...@mediatek.com wrote: > From: Ryder Lee > > Introduce a structure "mtk_pcie_soc" to abstract the differences between > controller generations, and the .startup() hook is used to encapsulate > some SoC-dependent related

[PATCH V2 net] Revert "vhost: cache used event for better performance"

This reverts commit 809ecb9bca6a9424ccd392d67e368160f8b76c92. Since it was reported to break vhost_net. We want to cache used event and use it to check for notification. The assumption was that guest won't move the event idx back, but this could happen in fact when 16 bit index wraps around after

Re: [PATCH V4 1/3] sched: cpufreq: Allow remote cpufreq callbacks

On 26-07-17, 19:42, Rafael J. Wysocki wrote: > On Wednesday, July 26, 2017 02:52:32 PM Viresh Kumar wrote: > > + /* Don't allow remote callbacks */ > > + if (smp_processor_id() != data->cpu) > > + return; > > You can do this check against cpu->cpu, however. > > > + /* Don't

Re: [PATCH v2 1/5] PCI: mediatek: Add a structure to abstract the controller generations

On Thu, 2017-07-27 at 11:19 +0800, Honghui Zhang wrote: > On Thu, 2017-07-27 at 10:58 +0800, honghui.zh...@mediatek.com wrote: > > From: Ryder Lee > > > > Introduce a structure "mtk_pcie_soc" to abstract the differences between > > controller generations, and the

Re: [PATCH v2 5/5] dt-bindings: PCI: add support for new generation controller

On Thu, 2017-07-27 at 10:58 +0800, honghui.zh...@mediatek.com wrote: > From: Ryder Lee > > Add support for MediaTek new generation controller and update related > properities. > > Signed-off-by: Ryder Lee > Signed-off-by: Honghui Zhang

Re: [RFC PATCH] mm: memcg: fix css double put in mem_cgroup_iter

2017-07-26 21:44 GMT+08:00 Michal Hocko : > On Wed 26-07-17 21:07:42, Wenwei Tao wrote: >> From: Wenwei Tao >> >> By removing the child cgroup while the parent cgroup is >> under reclaim, we could trigger the following kernel panic >> on kernel 3.10:

Re: [Eas-dev] [PATCH V3 1/3] sched: cpufreq: Allow remote cpufreq callbacks

On 26-07-17, 14:00, Saravana Kannan wrote: > No, the alternative is to pass it on to the CPU freq driver and let it > decide what it wants to do. That's the whole point if having a CPU freq > driver -- so that the generic code doesn't need to care about HW specific > details. Which is the point I

Re: [PATCH v2 5/5] dt-bindings: PCI: add support for new generation controller

On Thu, 2017-07-27 at 10:58 +0800, honghui.zh...@mediatek.com wrote: > From: Ryder Lee > > Add support for MediaTek new generation controller and update related > properities. > > Signed-off-by: Ryder Lee > Signed-off-by: Honghui Zhang

Re: [PATCH] cpufreq: docs: Add missing cpuinfo_cur_freq description

On 27-07-17, 02:05, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > Add a description of the cpuinfo_cur_freq policy attribute in sysfs > to the cpufreq documentation under Documentation/admin-guide/pm/ as > it is missing after commit 2a0e49279850 (cpufreq:

Re: [PATCH] cpufreq: intel_pstate: Drop ->get from intel_pstate structure

On 26-07-17, 00:42, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > The ->get callback in the intel_pstate structure was mostly there > for the scaling_cur_freq sysfs attribute to work, but after commit > f8475cef9008 (x86: use common aperfmperf_khz_on_cpu() to

[PATCH v2 1/3] media: V3s: Add support for Allwinner CSI.

Allwinner V3s SoC have two CSI module. CSI0 is used for MIPI interface and CSI1 is used for parallel interface. This is not documented in datasheet but by testing and guess. This patch implement a v4l2 framework driver for it. Currently, the driver only support the parallel interface. MIPI-CSI2,

[PATCH v2 2/3] dt-bindings: media: Add Allwinner V3s Camera Sensor Interface (CSI)

Add binding documentation for Allwinner V3s CSI. Signed-off-by: Yong Deng --- .../devicetree/bindings/media/sun6i-csi.txt| 49 ++ 1 file changed, 49 insertions(+) create mode 100644 Documentation/devicetree/bindings/media/sun6i-csi.txt diff

[PATCH v2 0/3] Initial Allwinner V3s CSI Support

This patchset add initial support for Allwinner V3s CSI. Allwinner V3s SoC have two CSI module. CSI0 is used for MIPI interface and CSI1 is used for parallel interface. This is not documented in datasheet but by testing and guess. This patchset implement a v4l2 framework driver and add a binding

Re: [PATCH v2 6/7] mailbox: bcm-flexrm-mailbox: Set msg_queue_len for each channel

On Tue, Jul 25, 2017 at 9:37 PM, Jassi Brar wrote: > On Tue, Jul 25, 2017 at 11:11 AM, Anup Patel wrote: >> On Mon, Jul 24, 2017 at 10:06 PM, Jassi Brar >> wrote: >>> On Mon, Jul 24, 2017 at 9:26 AM, Anup Patel

Re: [PATCH 0/6] Broadcom SBA-RAID driver improvements

On Wed, Jul 26, 2017 at 10:33 PM, Vinod Koul wrote: > On Wed, Jul 26, 2017 at 11:06:38AM +0530, Anup Patel wrote: >> This patchset does various improvments to Broadcom SBA-RAID >> driver and also adds SBA-RAID DT nodes for Stingray SOC. >> >> The patches are based on "[PATCH

Re: [PATCH 1/6] dma: bcm-sba-raid: Improve memory allocation in SBA RAID driver

On Wed, Jul 26, 2017 at 10:39 PM, Vinod Koul wrote: > On Wed, Jul 26, 2017 at 11:06:39AM +0530, Anup Patel wrote: >> This patch improves memory allocation in SBA RAID driver in >> following ways: >> 1. Simplify struct sba_request to reduce memory consumption > > what is the

Re: USB disk speed regression WD Elements - with bisect result 22547c4cc4fe20698a6a85a55b8788859134b8e4

[Added linux-usb mailing list to CC:] Short description of bug: In 4.12 or later, when Zdenek's Western Digital disk is attached to an EHCI controller, it ends up connecting at full speed to the companion UHCI controller instead. But when commit 22547c4cc4fe ("usb: hub: Wait for connection to be

Re: [PATCH v7 2/3] PCI: Enable PCIe Relaxed Ordering if supported

On 2017/7/27 2:26, Casey Leedom wrote: > By the way Ding, two issues: > > 1. Did we ever get any acknowledgement from either Intel or AMD > on this patch? I know that we can't ensure that, but it sure would > be nice since the PCI Quirks that we're putting in affect their >

Re: [PATCH tip/core/rcu 4/5] sys_membarrier: Add expedited option

On Wed, Jul 26, 2017 at 02:11:46PM -0700, Paul E. McKenney wrote: > On Wed, Jul 26, 2017 at 08:37:23PM +, Mathieu Desnoyers wrote: > > - On Jul 26, 2017, at 2:30 PM, Paul E. McKenney > > paul...@linux.vnet.ibm.com wrote: > > > > > On Wed, Jul 26, 2017 at 06:01:15PM +, Mathieu

[PATCH 3/3] arm: dts: mediatek: add larbid property for larb

From: Honghui Zhang Add mediatek's hardware id information for smi larb. Signed-off-by: Honghui Zhang --- arch/arm/boot/dts/mt2701.dtsi | 3 +++ 1 file changed, 3 insertions(+) diff --git a/arch/arm/boot/dts/mt2701.dtsi

[PATCH 1/3] memory: mtk-smi: add larbid init routine

From: Honghui Zhang In the commit 3c8f4ad85c4b ("memory/mediatek: add support for mt2701"), the larb->larbid was added but not initialized. Mediatek's gen1 smi need this hardware larbid information to get the register offset which controls whether enable iommu for

[PATCH 2/3] dt-bindings: mediatek: add descriptions for larbid

From: Honghui Zhang This patch add larbid descritptions for mediatek's gen1 smi larb hardware. Signed-off-by: Honghui Zhang --- .../bindings/memory-controllers/mediatek,smi-larb.txt | 15 +++ 1 file changed, 15

Re: [PATCH v2] scsi: qedf: Limit number of CQs

Thomas, > FCOE offloading failed with: > > [qed_sp_fcoe_func_start:150(sp-0-3b:00.02)]Cannot satisfy CQ amount. CQs >requested 8, CQs available 6. Aborting function start > [qed_fcoe_start:821()]Failed to start fcoe > [__qedf_probe:3041]:6: Cannot start FCoE function. > > The

[PATCH 0/3] Add larbid init routine for mediatek's gen1 smi larb driver

From: Honghui Zhang Mediatek's gen1 smi need the hardware larbid to identify the offset for the register which controls whether enable iommu for this larb. In the commit 3c8f4ad85c4b ("memory/mediatek: add support for mt2701"), the larbid was used without properly

Re: ARM64 board Hikey960 boot failure due to f2545b2d4ce1 (jump_label: Reorder hotplug lock and jump_label_lock)

On Wed, Jul 26, 2017 at 04:13:49PM +0100, Marc Zyngier wrote: > [+Mark] > > Hi Leo, > > On 24/07/17 15:34, Leo Yan wrote: > > Hi all, > > > > We found the mainline arm64 kernel boot failure on Hikey960 board, > > this is caused by patch f2545b2d4ce1 (jump_label: Reorder hotplug lock > > and

[PATCH v2 5/5] usb: xhci: Handle USB transaction error on address command

Xhci driver handles USB transaction errors on transfer events, but transaction errors are possible on address device command completion events as well. The xHCI specification (section 4.6.5) says: A USB Transaction Error Completion Code for an Address Device Command may be due to a Stall response

[PATCH v2 1/5] usb: xhci: Disable slot even virt-dev is null

xhci_disable_slot() is a helper for disabling a slot when a device goes away or recovers from error situations. Currently, it checks the corespoding virt-dev pointer and returns directly (w/o issuing disable slot command) if it's null. This is unnecessary and will cause problems in case where

[PATCH v2 0/5] usb: xhci: Handle USB transaction error on address command

Xhci driver handles USB transaction errors on transfer events, but transaction errors are possible on address device command completion events as well. The xHCI specification (section 4.6.5) says: A USB Transaction Error Completion Code for an Address Device Command may be due to a Stall response

[PATCH v2 4/5] usb: xhci: Return error when host is dead in xhci_disable_slot()

xhci_disable_slot() is a helper for disabling a slot when a device goes away or recovers from error situations. Currently, it returns success when it sees a dead host. This is not the right way to go. It should return error and let the invoker know that disable slot command was failed due to a

[PATCH v2 3/5] usb: xhci: Fix memory leak when xhci_disable_slot() returns error

If xhci_disable_slot() returns success, a disable slot command trb was queued in the command ring. The command completion handler will free the virtual device data structure associated with the slot. On the other hand, when xhci_disable_slot() returns error, the invokers should take the

[PATCH v2 2/5] usb: xhci: Fix potential memory leak in xhci_disable_slot()

xhci_disable_slot() allows the invoker to pass a command pointer as paramenter. Otherwise, it will allocate one. This will cause memory leak when a command structure was allocated inside of this function while queuing command trb fails. Another problem comes up when the invoker passed a command

[PATCH v2] security: fix description of values returned by cap_inode_need_killpriv

cap_inode_need_killpriv returns 1 if security.capability exists and has a value and inode_killpriv() is required, 0 otherwise. Fix the description of the return value to reflect this. Signed-off-by: Stefan Berger --- security/commoncap.c | 6 +++--- 1 file changed, 3

[PATCH V2] ACPI, APEI: Fixup incorrect 16-bit access width firmware bug

From: Liwei Song This is a follow up to commit f712c71f7b2b ("ACPI, APEI: Fixup common access width firmware bug") fix the following firmware bug: [Firmware Bug]: APEI: Invalid bit width + offset in GAR [0xb2/16/0/1/1] This is due to an 8-bit access width is specified

Re: [RFC/RFT PATCH] KVM: nVMX: fixes to nested virt interrupt injection

2017-07-24 22:20 GMT+08:00 Paolo Bonzini : > There are three issues in nested_vmx_check_exception: > > 1) it is not taking PFEC_MATCH/PFEC_MASK into account, as reported > by Wanpeng Li; > > 2) it should rebuild the interruption info and exit qualification fields > from

Re: [PATCH v3 3/3] power: wm831x_power: Support USB charger current limit management

Hi, On 26 July 2017 at 20:08, Sebastian Reichel wrote: > Hi, > > On Wed, Jul 26, 2017 at 11:05:25AM +0800, Baolin Wang wrote: >> On 25 July 2017 at 17:59, Sebastian Reichel >> wrote: >> > On Tue, Jul 25, 2017 at 04:00:01PM

[PATCH] selftests: sigaltstack: convert to use TAP13 ksft framework

Convert to use TAP13 ksft framework to output results. Signed-off-by: Shuah Khan --- tools/testing/selftests/sigaltstack/sas.c | 53 ++- 1 file changed, 31 insertions(+), 22 deletions(-) diff --git a/tools/testing/selftests/sigaltstack/sas.c

Re: [PATCH v7 2/3] PCI: Enable PCIe Relaxed Ordering if supported

On 2017/7/27 3:05, Casey Leedom wrote: > | From: Alexander Duyck > | Sent: Wednesday, July 26, 2017 11:44 AM > | > | On Jul 26, 2017 11:26 AM, "Casey Leedom" wrote: > | | > | | I think that the patch will need to be extended to modify > | |

[PATCH v3/resubmit 3/3] staging: gs_fpgaboot: return valid error codes

The return values on error are modified to be valid error codes. Theses error codes are propagated back to the init function's return. Signed-off-by: Jacob von Chorus --- drivers/staging/gs_fpgaboot/gs_fpgaboot.c | 14 +++--- 1 file changed, 7 insertions(+), 7

[PATCH v3/resubmit 1/3] staging: gs_fpgaboot: add buffer overflow checks

Four fields in struct fpgaimage are char arrays of length MAX_STR (256). The amount of data read into these buffers is controlled by a length field in the bitstream file read from userspace. If a corrupt or malicious firmware file was supplied, kernel data beyond these buffers can be overwritten

[PATCH v3/resubmit 2/3] staging: gs_fpgaboot: change char to u8

The bitstream storage variables were changed from char to u8 arrays to prevent issues such as negative lengths. This change makes the code compatible with the "data" field in "struct firmware" which is of type u8. Signed-off-by: Jacob von Chorus v3: - reduce temporary

Re: [Question]: try to fix contention between expire_timers and try_to_del_timer_sync

On 2017年07月26日 22:16, Thomas Gleixner wrote: On Wed, 26 Jul 2017, qiaozhou wrote: Cc'ed ARM folks. I want to ask you for suggestions about how to fix one contention between expire_timers and try_to_del_timer_sync. Thanks in advance. The issue is a hard-lockup issue detected on our

Re: [PATCH 1/4] can: dev: Add support for limiting configured bitrate

Hi Kurt, On 07/26/2017 03:04 PM, Kurt Van Dijck wrote: > Hi, > > I know my response is late ... > >> Hi Oliver >> On 07/20/2017 02:43 AM, Oliver Hartkopp wrote: >>> Hi Franklin, >>> >>> On 07/20/2017 01:36 AM, Franklin S Cooper Jr wrote: >>> +#ifdef CONFIG_OF +void

[PATCH] staging: unisys: visorchipset: constify attribute_group structure

Functions working with attribute_groups provided by work with const attribute_group. These attribute_group structures do not change at runtime so mark them as const. File size before: text data bss dec hex filename 24124 6216 448 307887844

Re: [patch 0/5] scsi/bnx2*: Plug hotplug race, correct locking and simplify hotplug code

Thomas, > The conversion of the cpu hotplug locking to a percpu rwsem does not > longer allow recursive locking of the hotplug lock. > > The BNX2I and BNX2FC drivers install/remove hotplug states with the > hotplug lock held. The install/removal code acquired the hotplug lock > as well. > >

Re: [PATCH 05/11] powerpc/topology: Remove the unused parent_node() macro

Dou Liyang writes: > Commit a7be6e5a7f8d ("mm: drop useless local parameters of > __register_one_node()") removes the last user of parent_node(). > > The parent_node() macro in POWERPC platform is unnecessary. > > Remove it for cleanup. > > Reported-by: Michael

Re: gigantic hugepages vs. movable zones

Michal Hocko writes: > Hi, > I've just noticed that alloc_gigantic_page ignores movability of the > gigantic page and it uses any existing zone. Considering that > hugepage_migration_supported only supports 2MB and pgd level hugepages > then 1GB pages are not migratable and as

Re: [PATCH v8 1/3] perf: cavium: Support memory controller PMU counters

On Wed, Jul 26, 2017 at 02:02:42PM -0700, David Daney wrote: > On 07/26/2017 01:08 PM, Greg KH wrote: > > On Wed, Jul 26, 2017 at 01:02:38PM -0700, David Daney wrote: > > > On 07/26/2017 10:33 AM, Greg KH wrote: > > > > On Wed, Jul 26, 2017 at 06:30:49PM +0200, Borislav Petkov wrote: > > > > > On

Re: [PATCH v2] security: fix description of values returned by cap_inode_need_killpriv

On Wed, Jul 26, 2017 at 10:27:05PM -0400, Stefan Berger wrote: > cap_inode_need_killpriv returns 1 if security.capability exists and > has a value and inode_killpriv() is required, 0 otherwise. Fix the > description of the return value to reflect this. > > Signed-off-by: Stefan Berger

Re: [PATCH v12 5/8] virtio-balloon: VIRTIO_BALLOON_F_SG

On 07/27/2017 01:02 AM, Michael S. Tsirkin wrote: On Wed, Jul 26, 2017 at 11:48:41AM +0800, Wei Wang wrote: On 07/23/2017 09:45 AM, Michael S. Tsirkin wrote: On Fri, Jul 14, 2017 at 03:12:43PM +0800, Wei Wang wrote: On 07/14/2017 04:19 AM, Michael S. Tsirkin wrote: On Thu, Jul 13, 2017 at

Re: [PATCH 05/11] powerpc/topology: Remove the unused parent_node() macro

Hi Michael, At 07/27/2017 10:21 AM, Michael Ellerman wrote: Dou Liyang writes: Commit a7be6e5a7f8d ("mm: drop useless local parameters of __register_one_node()") removes the last user of parent_node(). The parent_node() macro in POWERPC platform is unnecessary.

Re: [PATCH] f2fs: let __get_victim successfully get a segno in corner case

Hi, Jay, Sorry for the mistake in last mail, the ovp is 462, and the reserved is 235. I check the code and have not found problems with p.max_search yet. Just forget the this patch, since there is still 870 segments below, so it should not be the assumed case of this patch. By the way, I

[PATCH v2 0/5] PCI: MediaTek: Add support for new generation host controller

From: Honghui Zhang MediaTek's PCIe host controller has two generation HWs, the new generation HW has two root ports, it shares most probing flow with the legacy controller. But the read/write config space logical is different from the lagacy controller. This patchset

[Kein Betreff]

unsubscribe linux-kernel

Re: Qemu problems in -next with 's390/spinlock: add niai spinlock hints'

On Wed, Jul 26, 2017 at 07:40:44AM +0200, Martin Schwidefsky wrote: > On Wed, 26 Jul 2017 07:00:33 +0200 > Heiko Carstens wrote: > > > On Tue, Jul 25, 2017 at 06:14:51PM -0700, Guenter Roeck wrote: > > > Hi Martin, > > > > > > my s390 qemu tests in linux-next stopped working a few days ago. > >

Re: [PATCH V3 3/9] cpufreq: Cap the default transition delay value to 10 ms

On 25-07-17, 14:54, Leonard Crestez wrote: Thanks for reporting Leonard, really appreciate it. > This patch made it's way into linux-next and it seems to cause imx socs > to almost always hang around their max frequency with the ondemand > governor, even when almost completely idle. The lowest

linux-next: unsigned commits in the drm-misc tree

Hi all, I noticed a set of commits that have no Signed-off-by from their committer: d9864a1d2dfc ("drm/stm: drv: Rename platform driver name") to ed34d261a12a ("drm/stm: dsi: Constify phy ops structure") -- Cheers, Stephen Rothwell

linux-next: Tree for Jul 26

Hi all, Changes since 20170725: Non-merge commits (relative to Linus' tree): 2358 2466 files changed, 86994 insertions(+), 44655 deletions(-) I have created today's linux-next tree at

Re: [PATCH] ACPI, APEI: Fixup incorrect 16-bit access width firmware bug

On 07/21/2017 05:56 PM, Andy Shevchenko wrote: > On Fri, Jul 21, 2017 at 12:41 PM, Song liwei wrote: > >> [Firmware Bug]: APEI: Invalid bit width + offset in GAR [0xb2/16/0/1/1] >> >> This is due to an 8-bit access width is specified for a 16-bit register, >> Do bit_width check just like what

Re: [PATCH v5 3/7] drm/rockchip: vop: move line_flag_num to interrupt registers

On 2017年07月26日 05:54, Heiko Stuebner wrote: Hi Mark, Am Donnerstag, 20. Juli 2017, 10:43:32 CEST schrieb Mark Yao: In the hardware design process, the design of line flags register is associated with the interrupt register, placing the line flags in the interrupt definition is more reasonable,

Re: [PATCH v5 2/7] drm/rockchip: vop: move write_relaxed flags to vop register

On 2017年07月26日 05:47, Heiko Stuebner wrote: Hi Mark, Am Donnerstag, 20. Juli 2017, 10:43:27 CEST schrieb Mark Yao: Since the drm atomic framework, only a small part of the vop register needs sync write, Currently seems only following registers need sync write: cfg_done, standby and

[PATCH v6 1/7] drm/rockchip: vop: initialize registers directly

At present we are using init_table to initialize some registers, but the Register init table use un-document define, it is unreadable, and sometimes we only want to update tiny bits, init table method is not friendly, it's diffcult to reuse for difference chips. To make it clean, initialize

[PATCH v6 0/7] drm/rockchip: add all full framework vop support

These patches try to make all current rockchip full framework vop works on drm, fill missing vop on full framework. Vop Full framework now has following vops: IP versionchipname 3.1 rk3288 3.2 rk3368 3.4 rk3366 3.5 rk3399 big

[lkp-robot] [lib] e859afe1ee: kernel_BUG_at_lib/test_rhashtable.c

FYI, we noticed the following commit: commit: e859afe1ee0c5ae981c55387ccd45eba258a7842 ("lib: test_rhashtable: fix for large entry counts") https://git.kernel.org/cgit/linux/kernel/git/davem/net.git master in testcase: boot on test machine: qemu-system-x86_64 -enable-kvm -m 420M caused below

[PATCH v6 6/7] dt-bindings: display: rockchip: fill Documents for vop series

Signed-off-by: Mark Yao Acked-by: Rob Herring --- Changes in v5: - clean document commit title - move changes description out of docummit commit msg Changes in v2: - rename rk322x to rk3228 - correct some vop registers define Documentation/devicetree/bindings/display/rockchip/rockchip-vop.txt

[PATCH v6 3/7] drm/rockchip: vop: move line_flag_num to interrupt registers

In the hardware design process, the design of line flags register is associated with the interrupt register, placing the line flags in the interrupt definition is more reasonable, and it would make multi-vop define easilier. Signed-off-by: Mark Yao Reviewed-by: Sean Paul --- Changes in v6: -

[PATCH v6 2/7] drm/rockchip: vop: move write_relaxed flags to vop register

Since the drm atomic framework, only a small part of the vop register needs sync write, Currently seems only following registers need sync write: cfg_done, standby and interrupt related register. All ctrl registers are using the sync write method that is inefficient, hardcode the write_relaxed

[PATCH v6 7/7] drm/rockchip: vop: rk3328: fix overlay abnormal

It's a hardware bug, all window's overlay channel reset value is same, hardware overlay would be die. so we must initial difference id for each overlay channel. The Channel register is supported on all vop will full design. Following is the details for this register VOP_WIN0_CTRL2 bit[7:4]

[PATCH v6 4/7] drm/rockchip: vop: group vop registers

Grouping the vop registers facilitates make register definition clearer, and also is useful for different vop reuse the same group register. Signed-off-by: Mark Yao --- drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 99 drivers/gpu/drm/rockchip/rockchip_drm_vop.h | 60

[PATCH v6 5/7] drm/rockchip: vop: add a series of vop support

Vop Full framework now has following vops: IP versionchipname 3.1 rk3288 3.2 rk3368 3.4 rk3366 3.5 rk3399 big 3.6 rk3399 lit 3.7 rk3228 3.8 rk3328 The above IP version is from H/W define, some of vop support

Re: [PATCH V3 1/3] sched: cpufreq: Allow remote cpufreq callbacks

On 24-07-17, 15:47, Peter Zijlstra wrote: > I said nothing about the shared locking. That is indeed required. All I > said is that those two tests you add could be left out. I was right, I didn't understood your comment at all :( > > > That would then continue to process the iowait and other

Re: Qemu problems in -next with 's390/spinlock: add niai spinlock hints'

On Wed, 26 Jul 2017 08:05:27 +0200 Heiko Carstens wrote: > On Wed, Jul 26, 2017 at 07:40:44AM +0200, Martin Schwidefsky wrote: > > On Wed, 26 Jul 2017 07:00:33 +0200 > > Heiko Carstens wrote: > > > > > On Tue, Jul 25, 2017 at 06:14:51PM -0700, Guenter Roeck wrote: > > > > Hi Martin, > > >

[PATCH v2 1/4] dt-bindings: phy-hisi-inno-usb2: add support for hisi-inno-usb2 phy

Add support for hisi-inno-usb2 phy. Signed-off-by: Jiancheng Xue --- .../devicetree/bindings/phy/phy-hisi-inno-usb2.txt | 31 ++ 1 file changed, 31 insertions(+) create mode 100644 Documentation/devicetree/bindings/phy/phy-hisi-inno-usb2.txt diff --git

[PATCH v2 2/4] phy: add inno-usb2-phy driver for hi3798cv200 SoC

From: Pengcheng Li Add inno-usb2-phy driver for hi3798cv200 SoC. Signed-off-by: Pengcheng Li Signed-off-by: Jiancheng Xue --- drivers/phy/hisilicon/Kconfig | 11 +- drivers/phy/hisilicon/Makefile | 1 + drivers/phy/hisilicon/phy-hisi-inno-usb2.c | 236

[PATCH v2 4/4] arm64: defconfig: enable some drivers for hi3798cv200-poplar board.

Enable GMAC,I2C,USB2-PHY for hi3798cv200-poplar board. Signed-off-by: Jiancheng Xue --- arch/arm64/configs/defconfig | 4 1 file changed, 4 insertions(+) diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig index 6c7d147..93c709d7 100644 ---

[PATCH v2 3/4] arm64: dts: hisilicon: add usb2 controller and phy nodes for poplar board.

Add usb2 controller and phy nodes for poplar board. Signed-off-by: Jiancheng Xue Reviewed-by: Daniel Thompson --- .../boot/dts/hisilicon/hi3798cv200-poplar.dts | 13 + arch/arm64/boot/dts/hisilicon/hi3798cv200.dtsi | 60 ++ 2 files changed, 73 insertions(+)

[PATCH v2 0/4] Enable usb2 function on poplar board

This patchset is mainly used to enable the usb2 function on poplar board, including usb2 phy drivers, dts nodes and configs. Jiancheng Xue (3): dt-bindings: phy-hisi-inno-usb2: add support for hisi-inno-usb2 phy arm64: dts: hisilicon: add usb2 controller and phy nodes for poplar board.

Re: [PATCH v2 00/10] Constify attribute_group structures

Hi Kalle, On Tuesday 25 July 2017 06:25 PM, Kalle Valo wrote: Arvind Yadav writes: attribute_groups are not supposed to change at runtime. So mark the non-const structs as const. Arvind Yadav (10): [PATCH v2 01/10] net: cdc_ncm: constify attribute_group structures. [PATCH v2 02/10]

Re: [PATCH v2 00/10] Constify attribute_group structures

Hi Kalle, On Tuesday 25 July 2017 06:25 PM, Kalle Valo wrote: Arvind Yadav writes: attribute_groups are not supposed to change at runtime. So mark the non-const structs as const. Arvind Yadav (10): [PATCH v2 01/10] net: cdc_ncm: constify attribute_group structures. [PATCH v2 02/10]

RE: [PATCH v8 1/1] f2fs: dax: implement direct access

Hi, Considering the current interfaces of F2FS and EXT4, my thought is that we can define a generic user-modifiable flag FS_DAX_FL, which can be included in the i_flags field of [f2fs | ext4]_inode_info. Thus, DAX can be enabled in either of the two ways below: 1) mount the FS with a "dax"

<    5   6   7   8   9   10   11   12   13   14   >