Re: [Ksummit-discuss] [PATCH 1/2] code-of-conduct: Fix the ambiguity about collecting email addresses

On Mon, Oct 08, 2018 at 08:25:35AM +1000, Dave Airlie wrote: > This isn't a legally binding license or anything, but departing from > the upstream wording makes it tricker to merge new upstream versions > if they are considered appropriate. Nicely done, that - gotta love the passive voice use.

[PATCH -next] gpio: fix kernel-doc after devres.c file rename

From: Randy Dunlap Fix gpio kernel-doc generation after rename of the devres.c file. Fixes these errors & warning: Error: Cannot open file ../drivers/gpio/devres.c Error: Cannot open file ../drivers/gpio/devres.c WARNING: kernel-doc '../scripts/kernel-doc -rst -enable-lineno -export

Re: [Ksummit-discuss] [PATCH 1/2] code-of-conduct: Fix the ambiguity about collecting email addresses

On Mon, 8 Oct 2018 at 08:56, Al Viro wrote: > > On Mon, Oct 08, 2018 at 08:25:35AM +1000, Dave Airlie wrote: > > > This isn't a legally binding license or anything, but departing from > > the upstream wording makes it tricker to merge new upstream versions > > if they are considered appropriate.

Re: general protection fault in getname_kernel

On Sun, Oct 07, 2018 at 04:44:03PM -0700, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:c1d84a1b42ef Merge git://git.kernel.org/pub/scm/linux/kern.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=10f3c6a140 >

linux-next: manual merge of the rdma tree with the vfs tree

Hi all, Today's linux-next merge of the rdma tree got a conflict in: drivers/infiniband/Kconfig between commit: f57d445eb317 ("Make anon_inodes unconditional") from the vfs tree and commit: 914e5d7d4697 ("RDMA: Fix building with CONFIG_MMU=n") from the rdma tree. I fixed it up (see

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

Hi Herbert, After merging the crypto tree, today's linux-next build (x86_64 allmodconfig) failed like this: ERROR: "crypto_fpu_exit" [arch/x86/crypto/aesni-intel.ko] undefined! ERROR: "crypto_fpu_init" [arch/x86/crypto/aesni-intel.ko] undefined! Caused by commit 944585a64f5e ("crypto:

[PATCH] mm, oom_adj: avoid meaningless loop to find processes sharing mm

It is introduced by commit 44a70adec910 ("mm, oom_adj: make sure processes sharing mm have same view of oom_score_adj"). Most of user process's mm_users is bigger than 1 but only one thread group. In this case, for_each_process loop meaninglessly try to find processes which sharing same mm even

linux-next: manual merge of the tip tree with the pm tree

Hi all, Today's linux-next merge of the tip tree got a conflict in: drivers/idle/intel_idle.c between commit: a4a008e53c9e ("intel_idle: Get rid of custom ICPU() macro") from the pm tree and commit: f2c4db1bd807 ("x86/cpu: Sanitize FAM6_ATOM naming") from the tip tree. I fixed it up

Re: [PATCH v5 1/9] PCI: mediatek: Using slot's devfn for compare to fix mtk_pcie_find_port logic

On Tue, 2018-10-02 at 11:59 +0100, Lorenzo Pieralisi wrote: > On Mon, Oct 01, 2018 at 03:36:41PM +0100, Lorenzo Pieralisi wrote: > > On Fri, Sep 28, 2018 at 06:04:32PM +0800, honghui.zh...@mediatek.com wrote: > > > From: Honghui Zhang > > > > > > The Mediatek's host controller has two slots,

[PATCH v26 2/2] soc: mediatek: Add Mediatek CMDQ helper

Add Mediatek CMDQ helper to create CMDQ packet and assemble GCE op code. Signed-off-by: Houlong Wei Signed-off-by: HS Liao --- drivers/soc/mediatek/Kconfig | 12 ++ drivers/soc/mediatek/Makefile |1 + drivers/soc/mediatek/mtk-cmdq-helper.c | 292

[PATCH v26 1/2] arm64: dts: mt8173: Add GCE node

This patch adds the device node of the GCE hardware for CMDQ module. Signed-off-by: Houlong Wei Signed-off-by: HS Liao --- arch/arm64/boot/dts/mediatek/mt8173.dtsi | 10 ++ 1 file changed, 10 insertions(+) diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi

[PATCH v26 0/2] MediaTek MT8173 CMDQ support

Hi, This is Mediatek MT8173 Command Queue(CMDQ) driver. The CMDQ is used to help write registers with critical time limitation, such as updating display configuration during the vblank. It controls Global Command Engine (GCE) hardware to achieve this requirement. Changes since v25: -Replace

linux-next: manual merge of the drivers-x86 tree with the tip tree

Hi all, Today's linux-next merge of the drivers-x86 tree got a conflict in: drivers/platform/x86/intel_int0002_vgpio.c between commit: f2c4db1bd807 ("x86/cpu: Sanitize FAM6_ATOM naming") from the tip tree and commit: 96402de65afc ("platform/x86: intel_int0002_vgpio: Enable the driver

linux-next: manual merge of the kspp tree with the tip tree

Hi all, Today's linux-next merge of the kspp tree got a conflict in: Documentation/x86/x86_64/mm.txt between commits: 5b1290406579 ("x86/mm/doc: Clean up the x86-64 virtual memory layout descriptions") 32b89760ddf4 ("x86/mm/doc: Enhance the x86-64 virtual memory layout descriptions")

[PATCH v11 0/3]: perf: reduce data loss when profiling highly parallel CPU bound workloads

Currently in record mode the tool implements trace writing serially. The algorithm loops over mapped per-cpu data buffers and stores ready data chunks into a trace file using write() system call. At some circumstances the kernel may lack free space in a buffer because the other buffer's half

Re: [PATCH v2] cpufreq: dt-platdev: allow RK3399 to have separate tunables per cluster

On 05-10-18, 12:00, Dmitry Torokhov wrote: > RK3899 has one cluster with 4 small cores, and another one with 2 big > cores, with cores in different clusters having different OPPs and thus > needing separate set of tunables. Let's enable this via > "have_governor_per_policy" platform data. > >

Re: [PATCH v2] sparc: Convert to using %pOFn instead of device_node.name

From: Rob Herring Date: Tue, 28 Aug 2018 10:44:32 -0500 > In preparation to remove the node name pointer from struct device_node, > convert printf users to use the %pOFn format specifier. > > Cc: "David S. Miller" > Cc: sparcli...@vger.kernel.org > Signed-off-by: Rob Herring > --- > v2: > -

Re: [PATCH] sbus: Use of_get_child_by_name helper

From: Rob Herring Date: Wed, 29 Aug 2018 15:03:37 -0500 > Use the of_get_child_by_name() helper instead of open coding searching > for the '/options' node. This removes directly accessing the name > pointer as well. > > Cc: "David S. Miller" > Cc: sparcli...@vger.kernel.org > Signed-off-by:

Re: [PATCH] oradax: remove redundant null check before kfree

From: Colin King Date: Fri, 7 Sep 2018 11:35:00 +0100 > From: Colin Ian King > > A null check before a kfree is redundant, so remove it. > > Signed-off-by: Colin Ian King Applied.

Re: [PATCH] sparc64: viohs: Remove VLA usage

From: Kees Cook Date: Wed, 5 Sep 2018 15:03:51 -0700 > In the quest to remove all stack VLA usage from the kernel[1], this > allocates a fixed size array for the maximum number of cookies and > adds a runtime sanity check. > > [1]

[PATCH 08/19] orangefs: reorganize setattr functions to track attribute changes

OrangeFS accepts a mask indicating which attributes were changed. The kernel must not set any bits except those that were actually changed. The kernel must set the uid/gid of the request to the actual uid/gid responsible for the change. Code path for notify_change initiated setattrs is

[PATCH 01/19] orangefs: implement xattr cache

This uses the same timeout as the getattr cache. This substantially increases performance when writing files with smaller buffer sizes. When writing, the size is (often) changed, which causes a call to notify_change which calls security_inode_need_killpriv which needs a getxattr. Caching it

[PATCH 03/19] orangefs: simplify orangefs_inode_getattr interface

No need to store the received mask. It is either STATX_BASIC_STATS or STATX_BASIC_STATS & ~STATX_SIZE. If STATX_SIZE is requested, the cache is bypassed anyway, so the cached mask is unnecessary to decide whether to do a real getattr. This is a change. Previously a getattr would want size and

[PATCH 05/19] orangefs: hold i_lock during inode_getattr

This should be a no-op now. When inode writeback works, this will prevent a getattr from overwriting inode data while an inode is transitioning to dirty. Signed-off-by: Martin Brandenburg --- fs/orangefs/inode.c | 4 ++-- fs/orangefs/orangefs-utils.c | 33

[PATCH 15/19] orangefs: avoid fsync service operation on flush

Without this, an fsync call is sent to the server even if no data changed. This resulted in a rather severe (50%) performance regression under certain metadata-heavy workloads. In the past, everything was direct IO. Nothing happend on a close call. An explicit fsync call would send an fsync

linux-next: manual merge of the tip tree with the arm-soc tree

Hi all, Today's linux-next merge of the tip tree got a conflict in: MAINTAINERS between commits: 81aa283c6924 ("MAINTAINERS: Add Actions Semi S900 clk entries") 677309b0e9e6 ("MAINTAINERS: Add entry for Actions Semi Owl SoCs DMA driver") from the arm-soc tree and commit: 9d8d47ea6ec6

Re: [tip:x86/mm] kdump, proc/vmcore: Enable kdumping encrypted memory with SME enabled

在 2018年10月07日 16:47, Borislav Petkov 写道: > On Sun, Oct 07, 2018 at 01:55:33PM +0800, lijiang wrote: >> Here, it may be have a compile error. > > Are you sure? The configs I tried worked fine but I'm open to being > shown configs which fail the build. > Yes. As previously mentioned, the correct

Re: [PATCH 2/2] clk: qcom: gcc: Add global clock controller driver for QCS404

On 07-10-18, 19:38, Stephen Boyd wrote: > Quoting Vinod (2018-10-02 23:21:03) > > Hi Stephen, > > > > Thanks for the comments, > > > > On 01-10-18, 10:19, Stephen Boyd wrote: > > > Quoting Vinod Koul (2018-09-21 11:59:36) > > > > From: Shefali Jain > > > > > > > > Add the clocks supported in

linux-next: manual merge of the drivers-x86 tree with the tip tree

Hi all, Today's linux-next merge of the drivers-x86 tree got a conflict in: drivers/platform/x86/intel_mid_powerbtn.c between commit: f2c4db1bd807 ("x86/cpu: Sanitize FAM6_ATOM naming") from the tip tree and commit: a8b60e484f3d ("platform/x86: intel_mid_powerbtn: Get rid of custom

general protection fault in getname_kernel

Hello, syzbot found the following crash on: HEAD commit:c1d84a1b42ef Merge git://git.kernel.org/pub/scm/linux/kern.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=10f3c6a140 kernel config: https://syzkaller.appspot.com/x/.config?x=c0af03fe452b65fb

RE: [PATCH v2 10/11] arch/x86: Add AMD feature bit X86_FEATURE_MBA in cpuid bits array

> -Original Message- > From: Borislav Petkov > Sent: Friday, October 5, 2018 4:31 PM > To: Moger, Babu > Cc: t...@linutronix.de; mi...@redhat.com; h...@zytor.com; > reinette.cha...@intel.com; fenghua...@intel.com; james.mo...@arm.com; > vikas.shiva...@linux.intel.com;

list iterator spacing: clang-format vs checkpatch

Hi Joe, Miguel, others, The shiny new .clang-format file lists a number of nice iterators in the ForEachMacros category, the consequence being that there is a space between the iterator name and the opening parenthesis. This strikes me as the right thing to do. However, checkpatch.pl complains

linux-next: manual merge of the tip tree with the pm tree

Hi all, Today's linux-next merge of the tip tree got a conflict in: drivers/powercap/intel_rapl.c between commit: 17ed15183c24 ("powercap: RAPL: Get rid of custom RAPL_CPU() macro") from the pm tree and commit: f2c4db1bd807 ("x86/cpu: Sanitize FAM6_ATOM naming") from the tip tree. I

Re: [PATCH v6] clk: qcom: Add lpass clock controller driver for SDM845

Quoting Taniya Das (2018-10-04 05:02:26) > Add support for the lpass clock controller found on SDM845 based devices. > This would allow lpass peripheral loader drivers to control the clocks to > bring the subsystem out of reset. > LPASS clocks present on the global clock controller would be

[PATCH 1/4] doc/layerscape-pci: update the PCIe compatible strings

From: Hou Zhiqiang The pcie compatible string for LS1043A was lost, so add it. Signed-off-by: Hou Zhiqiang --- Documentation/devicetree/bindings/pci/layerscape-pci.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/pci/layerscape-pci.txt

[PATCH 0/4] dts/layerscape-pci: removed unsuitable compatible string

From: Hou Zhiqiang Removed the compatible string "snps,dw-pcie" from FSL layerscape-pci compatible string list. Hou Zhiqiang (4): doc/layerscape-pci: update the PCIe compatible strings doc/layerscape-pci: removed unsuitable compatible string dts/arm/ls1021a: Clean PCIe controller

[PATCH 02/19] orangefs: do not invalidate attributes on inode create

When an inode is created, we fetch attributes from the server. There is no need to turn around and invalidate them. No need to initialize attributes after the getattr either. Either it'll be exactly the same, or it'll be something else and wrong. Signed-off-by: Martin Brandenburg ---

[PATCH 00/19] [V2] orangefs: page cache

V2... see https://marc.info/?l=linux-fsdevel=153721507330730=2 One important change is the following, without which an unaligned write may end up written to the beginning of its page. Surprisingly xfstests did not catch this. This was caught by an invalidate_inode_pages2 call in read_iter (not

[PATCH 13/19] orangefs: skip inode writeout if nothing to write

Would happen if an inode is dirty but whatever happened is not something that can be written out to OrangeFS. Signed-off-by: Martin Brandenburg --- fs/orangefs/orangefs-utils.c | 5 + 1 file changed, 5 insertions(+) diff --git a/fs/orangefs/orangefs-utils.c b/fs/orangefs/orangefs-utils.c

[PATCH 07/19] orangefs: let setattr write to cached inode

This is a fairly big change, but ultimately it's not a lot of code. Implement write_inode and then avoid the call to orangefs_inode_setattr within orangefs_setattr. Signed-off-by: Martin Brandenburg --- fs/orangefs/inode.c | 11 +++ fs/orangefs/super.c | 16 2 files

[PATCH 19/19] orangefs: do writepages_work if a single page must be written

Otherwise the next page can't possibly be an append and it'll just sit there and write pages one by one until it flushes the saved region at the very end. Signed-off-by: Martin Brandenburg --- fs/orangefs/inode.c | 8 1 file changed, 8 insertions(+) diff --git a/fs/orangefs/inode.c

[PATCH 06/19] orangefs: set up and use backing_dev_info

Signed-off-by: Martin Brandenburg --- fs/orangefs/super.c | 21 ++--- 1 file changed, 14 insertions(+), 7 deletions(-) diff --git a/fs/orangefs/super.c b/fs/orangefs/super.c index 4c36481208f5..61bec955b285 100644 --- a/fs/orangefs/super.c +++ b/fs/orangefs/super.c @@ -406,15

[PATCH 09/19] orangefs: remove orangefs_readpages

It's a copy of the loop which would run in read_pages from mm/readahead.c. Signed-off-by: Martin Brandenburg --- fs/orangefs/inode.c | 39 +-- 1 file changed, 1 insertion(+), 38 deletions(-) diff --git a/fs/orangefs/inode.c b/fs/orangefs/inode.c index

[PATCH 14/19] orangefs: write range tracking

This is necessary to ensure the uid/gid responsible for the write is communicated with the server. Only one uid/gid may have outstanding changes at a time. If another uid/gid writes while there are outstanding changes, the changes must be written out before the new data is put into the page.

[PATCH 10/19] orangefs: service ops done for writeback are not killable

Signed-off-by: Martin Brandenburg --- fs/orangefs/orangefs-kernel.h | 1 + fs/orangefs/orangefs-utils.c | 2 +- fs/orangefs/waitqueue.c | 18 ++ 3 files changed, 12 insertions(+), 9 deletions(-) diff --git a/fs/orangefs/orangefs-kernel.h b/fs/orangefs/orangefs-kernel.h

[PATCH 12/19] orangefs: implement writepage

Now orangefs_inode_getattr fills from cache if an inode has dirty pages. also if attr_valid and dirty pages and !flags, we spin on inode writeback before returning if pages still dirty after: should it be other way Signed-off-by: Martin Brandenburg --- fs/orangefs/file.c | 77

[PATCH 17/19] orangefs: implement writepages

Go through pages and look for a consecutive writable region. After finding 128 consecutive writable pages or when finding a non-consecutive region, do the write. Signed-off-by: Martin Brandenburg --- fs/orangefs/file.c| 1 + fs/orangefs/inode.c | 144

[PATCH 16/19] orangefs: use kmem_cache for orangefs_write_request

Signed-off-by: Martin Brandenburg --- fs/orangefs/inode.c | 10 +- fs/orangefs/orangefs-cache.c | 24 ++-- fs/orangefs/orangefs-kernel.h | 6 -- fs/orangefs/orangefs-mod.c| 10 +- 4 files changed, 36 insertions(+), 14 deletions(-) diff

[PATCH 11/19] orangefs: migrate to generic_file_read_iter

Remove orangefs_inode_read. It was used by readpage. Calling wait_for_direct_io directly serves the purpose just as well. There is now no check of the bufmap size in the readpage path. There are already other places the bufmap size is assumed to be greater than PAGE_SIZE. Important to call

[PATCH 04/19] orangefs: update attributes rather than relying on server

This should be a no-op now, but once inode writeback works, it'll be necessary to have the correct attribute in the dirty inode. Previously the attribute fetch timeout was marked invalid and the server provided the updated attribute. When the inode is dirty, the server cannot be consulted since

[PATCH 18/19] orangefs: use client-core buffer size to determine writepages count

The previous fixed count of 128 was arbitrary. I see about a 10% performance increase on large block size I/O since the count is now 1024 (given the default four megabyte client-core buffer). Signed-off-by: Martin Brandenburg --- fs/orangefs/inode.c | 27 --- 1 file

RE: [PATCH V2 2/2] cpufreq: imx6q: read OCOTP through nvmem for imx6ul/imx6ull

Hi, Viresh Anson Huang Best Regards! > -Original Message- > From: Viresh Kumar > Sent: Monday, October 1, 2018 1:58 PM > To: Anson Huang > Cc: shawn...@kernel.org; s.ha...@pengutronix.de; ker...@pengutronix.de; > Fabio Estevam ; robh...@kernel.org; > mark.rutl...@arm.com;

Re: [Ksummit-discuss] [PATCH] code-of-conduct: Remove explicit list of discrimination factors

On Sun, Oct 07, 2018 at 08:18:26PM +0300, Laurent Pinchart wrote: > Hi Josh, > > On Sunday, 7 October 2018 14:35:14 EEST Josh Triplett wrote: > > On Sun, Oct 07, 2018 at 10:51:02AM +0200, Geert Uytterhoeven wrote: > > > Providing an explicit list of discrimination factors may give the false > > >

Re: [PATCH v25 2/2] soc: mediatek: Add Mediatek CMDQ helper

On Sat, 2018-09-29 at 20:50 +0800, Matthias Brugger wrote: > > On 29/09/2018 11:21, Houlong Wei wrote: > [...] > > > +static int cmdq_pkt_append_command(struct cmdq_pkt *pkt, enum cmdq_code > > code, > > + u32 arg_a, u32 arg_b) > > +{ > > + u64 *cmd_ptr; > > + > >

Re: [PATCH v5 2/2] clk: qcom: Add lpass clock controller driver for SDM845

Quoting Taniya Das (2018-10-04 05:01:27) > > On 9/29/2018 12:21 AM, Stephen Boyd wrote: > > Quoting Taniya Das (2018-09-18 03:25:38) > >> @@ -3469,6 +3495,8 @@ enum { > >> [GCC_QSPI_CORE_CLK_SRC] = _qspi_core_clk_src.clkr, > >> [GCC_QSPI_CORE_CLK] = _qspi_core_clk.clkr, > >>

[PATCH v6 5/9] PCI: mediatek: Move the mtk_pcie_startup_port_v2 function's define after mtk_pcie_setup_irq

From: Honghui Zhang This is a prepare patch to fix enable MSI logic, move the function's define later to avoid forward declaration of mtk_pcie_enable_msi in the future. No functional changed. Signed-off-by: Honghui Zhang Acked-by: Ryder Lee --- drivers/pci/controller/pcie-mediatek.c | 138

[PATCH v6 1/9] PCI: mediatek: Using slot's devfn for compare to fix mtk_pcie_find_port logic

From: Honghui Zhang The Mediatek's host controller has two slots, each with it's own control registers. The host driver need to identify which slot was connected in order to access the device's configuration space. There's problem for current host driver to find out which slot was connected to

Re: [PATCH 01/13] clocksource: Convert to using %pOFn instead of device_node.name

On 5.10.2018 16:35, Daniel Lezcano wrote: > From: Rob Herring > > In preparation to remove the node name pointer from struct device_node, > convert printf users to use the %pOFn format specifier. > > Cc: Daniel Lezcano > Cc: Thomas Gleixner > Cc: Michal Simek > Cc:

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

On Mon, Oct 08, 2018 at 12:03:30PM +1100, Stephen Rothwell wrote: > Hi Herbert, > > After merging the crypto tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > ERROR: "crypto_fpu_exit" [arch/x86/crypto/aesni-intel.ko] undefined! > ERROR: "crypto_fpu_init"

Re: [PATCH] percpu: stop leaking bitmap metadata blocks

Hi Mike, On Sun, Oct 07, 2018 at 11:31:51AM +0300, Mike Rapoport wrote: > The commit ca460b3c9627 ("percpu: introduce bitmap metadata blocks") > introduced bitmap metadata blocks. These metadata blocks are allocated > whenever a new chunk is created, but they are never freed. Fix it. > > Fixes:

Re: Linux 4.19-rc7

On Sun, Oct 07, 2018 at 05:45:29PM +0200, Greg KH wrote: > Hi all, > > Yet again, it's time for a kernel -rc release. This one is bigger than > -rc6 was, for a variety of unrelated reasons it seems. Lots of > different trees being merged this week, much more so than the previous > one.

Re: [patch] mm, page_alloc: set num_movable in move_freepages()

On Fri, 5 Oct 2018, Andrew Morton wrote: > On Fri, 5 Oct 2018 13:56:39 -0700 (PDT) David Rientjes > wrote: > > > If move_freepages() returns 0 because zone_spans_pfn(), *num_movable can > > move_free_pages_block()? !zone_spans_pfn()? > move_freepages_block() more accurately,

[PATCH V3] cpufreq: imx6q: read OCOTP through nvmem for imx6ul/imx6ull

On i.MX6UL/i.MX6ULL, accessing OCOTP directly is wrong because the ocotp clock needs to be enabled first. Add support for reading OCOTP through the nvmem API, and keep the old method there to support old dtb. Signed-off-by: Anson Huang --- changes since V2: Add put node when reading

[PATCH v6 8/9] PCI: mediatek: Save the GIC IRQ in mtk_pcie_port

From: Honghui Zhang Need to save the PCIe's GIC IRQ for dispose_irq, this is a prepare patch for add mediatek PCIe module support to tear down the IRQ, no functional changed. Signed-off-by: Honghui Zhang Acked-by: Ryder Lee --- drivers/pci/controller/pcie-mediatek.c | 9 ++--- 1 file

[PATCH v6 6/9] PCI: mediatek: Fixup enable msi logic by enable msi after clock enabled

From: Honghui Zhang The commit 43e6409db64d ("PCI: mediatek: Add MSI support for MT2712 and MT7622") added MSI support but enable MSI in wrong place, clocks was not enabled when enable MSI. This patch fix this issue by calling mtk_pcie_enable_msi in mtk_pcie_startup_port_v2 since the clock was

[PATCH v6 0/9] PCI: mediatek: fixup find_port, enable_msi and add pm, module support

From: Honghui Zhang This patchset includes misc patchs: The patch 1 fixup the mtk_pcie_find_port logic which will cause system could not touch the EP's configuration space that connected to PCIe slot 1. The patch 2 fixup the class type for MT7622. The patch 6 fixup the enable msi logic, the

[PATCH v6 9/9] PCI: mediatek: Add loadable kernel module support

From: Honghui Zhang Implement remove callback function for Mediatek PCIe driver to add loadable kernel module support. Signed-off-by: Honghui Zhang Reviewed-by: Ryder Lee --- drivers/pci/controller/Kconfig | 2 +- drivers/pci/controller/pcie-mediatek.c | 52

[PATCH v6 7/9] PCI: mediatek: Add system pm support for MT2712 and MT7622

From: Honghui Zhang In order to reduce the PCIe power consuming while system suspend, the physical layer should be gated. And the PCIe link should be re-established and the related control register values should be re-initialized after system resume. Register suspend_noirq & resume_noirq

[PATCH v6 3/9] PCI: mediatek: Remove the redundant dev->pm_domain check

From: Honghui Zhang It's no needed to check whether device have pm_domain attached before calling the pm_runtime_XXX interface, remove it. Signed-off-by: Honghui Zhang Acked-by: Ryder Lee --- drivers/pci/controller/pcie-mediatek.c | 18 ++ 1 file changed, 6 insertions(+), 12

[PATCH v6 4/9] PCI: mediatek: Convert to use pci_host_probe()

From: Honghui Zhang Part of mtk_pcie_register_host is an open-coded version of pci_host_probe(). So instead of duplicating this code, use pci_host_probe() directly and remove mtk_pcie_register_host. Signed-off-by: Honghui Zhang Acked-by: Ryder Lee --- drivers/pci/controller/pcie-mediatek.c |

[PATCH v6 2/9] PCI: mediatek: Fixup class ID for MT7622 as PCI_CLASS_BRIDGE_PCI

From: Honghui Zhang The PCIe controller of MT7622 has TYPE 1 configuration space type, but the HW default class type values is invalid. The commit 101c92dc80c8 ("PCI: mediatek: Set up vendor ID and class type for MT7622") have set the class ID for MT7622 as PCI_CLASS_BRIDGE_HOST, but it's not

RE: [PATCH v2 05/11] arch/x86: Introduce a new config parameter PLATFORM_QOS

Hi Fenghua, > -Original Message- > From: Fenghua Yu > Sent: Friday, October 5, 2018 6:39 PM > To: Moger, Babu > Cc: t...@linutronix.de; mi...@redhat.com; h...@zytor.com; > reinette.cha...@intel.com; fenghua...@intel.com; james.mo...@arm.com; > vikas.shiva...@linux.intel.com;

Re: [PATCH] kvm/x86 : avoid shifting signed 32-bit value by 31 bits

On Mon, Oct 08, 2018 at 09:04:34AM +0800, peng.h...@zte.com.cn wrote: >>On Sat, Oct 06, 2018 at 11:31:04AM +0800, peng.h...@zte.com.cn wrote: On Thu, Oct 04, 2018 at 01:47:18PM -0400, Peng Hao wrote: > >From: Peng Hao > > modify AVIC_LOGICAL_ID_ENTRY_VALID_MASK to unsigned

[PATCH v4 2/2] dt-bindings: spi: Document Macronix controller bindings

From: Mason Yang Document the bindings used by the Macronix controller. Signed-off-by: Mason Yang --- Documentation/devicetree/bindings/spi/spi-mxic.txt | 34 ++ 1 file changed, 34 insertions(+) create mode 100644 Documentation/devicetree/bindings/spi/spi-mxic.txt diff

[PATCH v4 1/2] spi: Add MXIC controller driver

From: Mason Yang Add a driver for Macronix SPI controller IP. Signed-off-by: Mason Yang --- drivers/spi/Kconfig| 6 + drivers/spi/Makefile | 1 + drivers/spi/spi-mxic.c | 639 + 3 files changed, 646 insertions(+) create mode 100644

[PATCH v4 0/2] spi: Add Macronix controller driver

From: Mason Yang Hi Mark, I patched v4 spi-mxic.c for clk_ctrl() and spi_setup() according to your comments on v3. Hi Boris, I also patched clk frequency changed when the driver detects it needs to be changed. please help to review. thanks & best regards, Mason Mason Yang (2): spi: Add

linux-next: manual merge of the staging tree with the v4l-dvb tree

Hi Greg, Today's linux-next merge of the staging tree got a conflict in: drivers/staging/media/imx/imx-media-of.c between commit: 21711787045d ("media: staging/imx: of: Remove recursive graph walk") from the v4l-dvb tree and commit: f93861c2d611 ("staging: Convert to using %pOFn

Re: [PATCH] s390/qeth: fix a missing-check bug

On Sat, Oct 06, 2018 at 11:08:23AM -0500, Wenwen Wang wrote: > In qeth_snmp_command(), the length of the user request is firstly copied > from the user-space buffer 'udata' to the kernel variable 'req_len' and > checked to see whether it is too large. If the check fails, an error code > EINVAL is

Re: [PATCH] sparc64: fix fall-through annotation

From: "Gustavo A. R. Silva" Date: Tue, 2 Oct 2018 12:19:54 +0200 > Replace "fallthru" with a proper "fall through" annotation. > > This fix is part of the ongoing efforts to enabling > -Wimplicit-fallthrough > > Signed-off-by: Gustavo A. R. Silva Applied.

Re: [PATCH] sparc32: fix fall-through annotation

From: "Gustavo A. R. Silva" Date: Tue, 2 Oct 2018 12:15:17 +0200 > Replace "fallthru" with a proper "fall through" annotation. > > This fix is part of the ongoing efforts to enabling > -Wimplicit-fallthrough > > Signed-off-by: Gustavo A. R. Silva Applied.

Re: [PATCH] sparc: vdso: clean-up vdso Makefile

From: Masahiro Yamada Date: Wed, 12 Sep 2018 12:39:13 +0900 > arch/sparc/vdso/Makefile is a replica of arch/x86/entry/vdso/Makefile. > > Clean-up the Makefile in the same way as I did for x86: > > - Remove unnecessary export > - Put the generated linker script to $(obj)/ instead of $(src)/ >

Re: [Ksummit-discuss] [PATCH 1/2] code-of-conduct: Fix the ambiguity about collecting email addresses

On Sun, 7 Oct 2018 at 07:36, James Bottomley wrote: > > From 4a614e9440148894207bef5bf69e74071baceb3b Mon Sep 17 00:00:00 2001 > From: James Bottomley > Date: Sat, 6 Oct 2018 14:21:56 -0700 > Subject: [PATCH 1/2] code-of-conduct: Fix the ambiguity about collecting email > addresses > > The

Re: [Ksummit-discuss] [PATCH 1/2] code-of-conduct: Fix the ambiguity about collecting email addresses

On Sun, Oct 07, 2018 at 11:56:13PM +0100, Al Viro wrote: > We can surround it with "explanations" Sorry, "clarifications". Or whatever euphemism you prefer for exegesis, really...

Re: [PATCH] kasan: convert kasan/quarantine_lock to raw_spinlock

I applied this patch to a fairly stock 4.18-rt5 kernel and booted with no complaints, then ran rteval for 12h with no stack splats reported. I'll keep banging on it but preliminary reports look good. Clark On Fri, 5 Oct 2018 18:33:20 +0200 Sebastian Andrzej Siewior wrote: > On 2018-10-05

linux-next: manual merge of the crypto tree with the compiler-attributes tree

Hi all, Today's linux-next merge of the crypto tree got a conflict in: include/linux/compiler_types.h between commit: a3f8a30f3f00 ("Compiler Attributes: use feature checks instead of version checks") from the compiler-attributes tree and commit: f3569fd613f6 ("crypto: shash - Remove

Re: [PATCH v9 04/10] x86: refcount: prevent gcc distortions

at 2:31 AM, Ingo Molnar wrote: > > * Nadav Amit wrote: > >>> Are you using defconfig or a reasonable distro-config for your tests? >> >> I think it is best to take the kernel and run localyesconfig for testing. > > Ok, agreed - and this makes the numbers you provided pretty representative.

[PATCH] tty: check name length in tty_find_polling_driver()

From: Miles Chen The issue is found by a fuzzing test. If tty_find_polling_driver() recevies an incorrect input such as ',,' or '0b', the len becomes 0 and strncmp() always return 0. In this case, a null p->ops->poll_init() is called and it causes a kernel panic. Fix this by checking name

Re: [PATCH 2/2] clk: qcom: gcc: Add global clock controller driver for QCS404

Quoting Vinod (2018-10-02 23:21:03) > Hi Stephen, > > Thanks for the comments, > > On 01-10-18, 10:19, Stephen Boyd wrote: > > Quoting Vinod Koul (2018-09-21 11:59:36) > > > From: Shefali Jain > > > > > > Add the clocks supported in global clock controller which clock the > > > peripherals

[PATCH v2] staging: iio: ad2s1210: fix 'assignment operator' style checks

This patch fixes all "Assignment operator '=' should be on the previous line" checks found in ad2s1210.c with checkpatch.pl. Signed-off-by: Matheus Tavares --- Changes in v2: In v1, tabs were accidentally converted to whitespaces. Now, tabs were preserved.

Do You Need A Helping Hand?

Re: [tip:x86/mm] kdump, proc/vmcore: Enable kdumping encrypted memory with SME enabled

On Mon, Oct 08, 2018 at 11:30:56AM +0800, lijiang wrote: > Yes. As previously mentioned, the correct patch is this one: No, that chunk is not needed and I removed it. But I'd leave it as an exercise to you to figure out why... or to prove me wrong with a .config. :-) -- Regards/Gruss,

Re: [PATCH v2 2/2] PCI: controller: dwc: add UniPhier PCIe host controller support

Hi Lorenzo, On Friday 28 September 2018 09:13 PM, Lorenzo Pieralisi wrote: > On Fri, Sep 28, 2018 at 02:17:16PM +0100, Marc Zyngier wrote: >> On 28/09/18 12:06, Lorenzo Pieralisi wrote: >>> [+Murali, Marc] >>> >>> On Thu, Sep 27, 2018 at 04:44:26PM +0900, Kunihiko Hayashi wrote: Hi Lorenzo,

[PATCH RFC 0/1] hugetlbfs: fix truncate/fault races

Our DB team noticed negative hugetlb reserved page counts during development testing. Related meminfo fields were as follows on one system: HugePages_Total: 47143 HugePages_Free:45610 HugePages_Rsvd:18446744073709551613 HugePages_Surp:0 Hugepagesize: 2048 kB Code

[PATCH RFC 1/1] hugetlbfs: introduce truncation/fault mutex to avoid races

The following hugetlbfs truncate/page fault race can be recreated with programs doing something like the following. A huegtlbfs file is mmap(MAP_SHARED) with a size of 4 pages. At mmap time, 4 huge pages are reserved for the file/mapping. So, the global reserve count is 4. In addition, since

[PATCH 4/4] MIPS: Provide actually relaxed MMIO accessors

Improve performance for the relevant systems and remove the DMA ordering barrier from `readX_relaxed' and `writeX_relaxed' MMIO accessors, where it is not needed according to our requirements[1]. For consistency make the same arrangement with low-level port I/O accessors, but do not actually

Re: [PATCH 1/3] dt-bindings: crypto: Mention clocks for mxs-dcp

On Tue, Oct 02, 2018 at 07:18:21PM +, Leonard Crestez wrote: > Explicit clock enabling is required on 6sll and 6ull so mention that > standard clock bindings are used. > > Signed-off-by: Leonard Crestez > --- > Documentation/devicetree/bindings/crypto/fsl-dcp.txt | 2 ++ > 1 file changed, 2

[PATCH 0/4] MIPS: Ordering enforcement fixes for MMIO accessors

Hi, This patch series is a follow-up to my earlier consideration about MMIO access ordering recorded here: . As I have learnt in a recent Alpha/Linux discussion starting here:

[PATCH 2/4] MIPS: Correct `mmiowb' barrier for `wbflush' platforms

Redefine `mmiowb' in terms of `iobarrier_w' so that it works correctly for MIPS I platforms, which have no SYNC machine instruction and use a call to `wbflush' instead. This doesn't change the semantics for CONFIG_CPU_CAVIUM_OCTEON, because `iobarrier_w' expands to `wmb', which is ultimately

[PATCH 3/4] MIPS: Enforce strong ordering for MMIO accessors

Architecturally the MIPS ISA does not specify ordering requirements for uncached bus accesses such as MMIO operations normally use and therefore explicit barriers have to be inserted between MMIO accesses where unspecified ordering of operations would cause unpredictable results. For example

[PATCH 1/4] MIPS: Define MMIO ordering barriers

Define MMIO ordering barriers as separate operations so as to allow making places where such a barrier is required distinct from places where a memory or a DMA barrier is needed. Architecturally MIPS does not specify ordering requirements for uncached bus accesses such as MMIO operations

  1   2   3   4   5   >