Re: [PATCH v3] RISC-V: Fix Maximum Physical Memory 2GiB option for 64bit systems

On Fri, Apr 05, 2019 at 05:49:34AM +, Anup Patel wrote: > The Maximum Physical Memory 2GiB option for 64bit systems is currently > broken because kernel hangs at boot-time when this option is enabled > and the underlying system has more than 2GiB memory. > > This issue can be easily

[PATCH v3] RISC-V: Fix Maximum Physical Memory 2GiB option for 64bit systems

The Maximum Physical Memory 2GiB option for 64bit systems is currently broken because kernel hangs at boot-time when this option is enabled and the underlying system has more than 2GiB memory. This issue can be easily reproduced on SiFive Unleashed board where we have 8GiB of memory. This patch

linux-next: Tree for Apr 5

Hi all, Changes since 20190404: The at91 tree gained a conflict against the at91-fixes tree. The btrfs-kdave tree gained a conflict against the btrfs-fixes tree. The drm-misc tree gained a build failure for which I disabled a driver. Non-merge commits (relative to Linus' tree): 4926 4791

Re: [PATCH 4.19 000/187] 4.19.34-stable review

stable-rc/linux-4.19.y boot: 120 boots: 13 failed, 90 passed with 16 offline, 1 untried/unknown (v4.19.33-187-g4b338ef616b3) Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.19.y/kernel/v4.19.33-187-g4b338ef616b3/ Full Build Summary:

Re: [PATCH v2] extcon: axp288: Add a depends on ACPI to the Kconfig entry

On 4/4/2019 7:47 PM, Yue Haibing wrote: From: YueHaibing As Hans de Goede pointed, using this driver without ACPI makes little sense, so add ACPI dependency to Kconfig entry to fix a build error while CONFIG_ACPI is not set. drivers/extcon/extcon-axp288.c: In function 'axp288_extcon_probe':

RE: [LINUX PATCH v2 3/3] spi: spi-mem: Add support for Zynq QSPI controller

Hi Vignesh, Thanks for the review. > -Original Message- > From: Vignesh Raghavendra > Sent: Friday, April 5, 2019 10:14 AM > To: Naga Sureshkumar Relli ; broo...@kernel.org; > bbrezil...@kernel.org > Cc: linux-...@vger.kernel.org; dw...@infradead.org; marek.va...@gmail.com; >

Re: [PATCH 5.0 072/246] drm/amd/display: Fix reference counting for struct dc_sink.

Greg, as I mentioned in the commit message, I saw more fixes to that area in Alex Deuchers queue when I fed that to Alex. There is one fix that I can think of that interacts with my fixes. Means, we may get unwanted side effects of my patch without the fix mentioned below. With that below patch

Re: [PATCH] staging: rtl8192u: ieee80211: add space around '==' and before '('

On Fri, Apr 05, 2019 at 10:31:17AM +0800, YueHaibing wrote: > On 2019/4/5 9:56, Caio Salvador Rohwedder wrote: > > if(!list_empty(pUnusedList)) { > > (*ppTS) = list_entry(pUnusedList->next, struct > > ts_common_info, list); > >

Re: [PATCH v3] Staging: rtlwifi: Cleanup crc16_ccitt()

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

[PATCH] overflow.h: Rename __ab_c_size() to __calc_size()

From: Borislav Petkov ... to make its name readable to humans so that it can denote what that helper does. No functional changes. Signed-off-by: Borislav Petkov Cc: Kees Cook Cc: Matthew Wilcox --- include/linux/overflow.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff

Re: [PATCH 4.19 000/187] 4.19.34-stable review

On Thu, 4 Apr 2019 at 14:31, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.19.34 release. > There are 187 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > >

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

On Thu, 2019-04-04 at 21:30 -0700, Bart Van Assche wrote: > On 4/4/19 8:25 PM, Stephen Rothwell wrote: > > Hi James, > > > > After merging the scsi tree, today's linux-next build (powerpc > > ppc64_defconfig) produced this warning: > > > > drivers/scsi/lpfc/lpfc_nvme.c:2140:1: warning: > >

Re: [LINUX PATCH v2 3/3] spi: spi-mem: Add support for Zynq QSPI controller

On 01/04/19 1:29 PM, Naga Sureshkumar Relli wrote: > +/** > + * zynq_qspi_config_op - Configure QSPI controller for specified transfer > + * @xqspi: Pointer to the zynq_qspi structure > + * @qspi:Pointer to the spi_device structure > + * > + * Sets the operational mode of QSPI controller

Re: 32-bit Amlogic (ARM) SoC: kernel BUG in kfree()

Hi Liang, On Fri, Mar 29, 2019 at 8:44 AM Liang Yang wrote: > > Hi Martin, > > On 2019/3/29 2:03, Martin Blumenstingl wrote: > > Hi Liang, > [..] > >> I don't think it is caused by a different NAND type, but i have followed > >> the some test on my GXL platform. we can see the result from

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

On 4/4/19 8:25 PM, Stephen Rothwell wrote: Hi James, After merging the scsi tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: drivers/scsi/lpfc/lpfc_nvme.c:2140:1: warning: 'lpfc_nvme_lport_unreg_wait' defined but not used [-Wunused-function]

[PATCH V2] csky: Reconstruct signal.c and entry.S

From: Guo Ren Linux kernel has provided some apis for arch signal's implementation. For example: restore_saved_sigmask() set_current_blocked() restore_altstack() But in last version of csky signal.c didn't use them and some codes are confusing, so reconstruct signal.c

Re: [PATCH v8 06/20] riscv: mm: Add p?d_large() definitions

On Wed, Apr 3, 2019 at 7:47 PM Steven Price wrote: > > walk_page_range() is going to be allowed to walk page tables other than > those of user space. For this it needs to know when it has reached a > 'leaf' entry in the page tables. This information is provided by the > p?d_large()

Re: [PATCH] x86/microcode: Refactor Intel microcode loading

On Fri, Apr 05, 2019 at 12:54:31AM +0200, Jann Horn wrote: > [ 159.485731] microcode: CPU7 found a matching microcode update with > version 0x25 (current=0x19) Yeah, that printk can be kinda misleading :) > I thought I had checked /sys/devices/system/cpu/cpu0/microcode/version > afterwards. But

[PATCH 1/3] dt-bindings: interconnect: Add Qualcomm QCS404 DT bindings

The Qualcomm QCS404 platform has several buses that could be controlled and tuned according to the bandwidth demand. Signed-off-by: Georgi Djakov --- .../bindings/interconnect/qcom,qcs404.txt | 45 +++ 1 file changed, 45 insertions(+) create mode 100644

[PATCH 3/3] arm64: dts: qcs404: Add interconnect provider DT nodes

Add the DT nodes for the network-on-chip interconnect buses found on qcs404-based platforms. Signed-off-by: Georgi Djakov --- arch/arm64/boot/dts/qcom/qcs404.dtsi | 25 + 1 file changed, 25 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/qcs404.dtsi

[PATCH 2/3] interconnect: qcom: Add QCS404 interconnect provider driver

From: Bjorn Andersson Add driver for the interconnect buses found in Qualcomm QCS404-based platforms. The topology consists of three NoCs that are controlled by a remote processor that collects the aggregated bandwidth for each master-slave pairs. Signed-off-by: Bjorn Andersson Signed-off-by:

[PATCH 0/3] Add QCS404 interconnect provider driver

Add driver to support scaling of the on-chip interconnects on QCS404-based platforms. Also add the necessary device-tree nodes, so that the driver for each NoC can probe and register as interconnect-provider. Bjorn Andersson (1): interconnect: qcom: Add QCS404 interconnect provider driver

Re: [PATCH v4 4/4] pinctrl: add drive for I2C related pins on MT8183

On Mon, Apr 1, 2019 at 10:35 AM Zhiyong Tao wrote: > This patch provides the advanced drive for I2C used pins on MT8183. > The detail strength specification description of the I2C pin: > When E1=0/E0=0, the strength is 0.125mA. > When E1=0/E0=1, the strength is 0.25mA. > When E1=1/E0=0, the

[PATCH] staging: rtl8723bs: add space after enum declaration

Add space between "enum TXDESC_SC" and '{' at line 86. Fix the following error from checkpatch.pl WARNING: missing space after enum definition +enum TXDESC_SC{ Signed-off-by: William Tustumi --- drivers/staging/rtl8723bs/include/rtw_xmit.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

Re: [PATCH v4 1/4] dt-bindings: pinctrl: mt8183: add binding document

On Mon, Apr 1, 2019 at 10:35 AM Zhiyong Tao wrote: > The commit adds mt8183 compatible node in binding document. > > Signed-off-by: Zhiyong Tao > Signed-off-by: Erin Lo > Reviewed-by: Rob Herring Patch applied to the pinctrl tree. Yours, Linus Walleij

Re: [PATCH v4 3/4] arm64: dts: mt8183: add pinctrl device node

On Mon, Apr 1, 2019 at 10:35 AM Zhiyong Tao wrote: > The commit adds pinctrl device node for mt8183 > > Signed-off-by: Zhiyong Tao > Signed-off-by: Erin Lo Acked-by: Linus Walleij Yours, Linus Walleij

Re: [PATCH v4 2/4] arm64: dts: mt8183: add pinctrl file

On Mon, Apr 1, 2019 at 10:35 AM Zhiyong Tao wrote: > This patch adds pinctrl file for mt8183. Better commit message maybe? But no big deal. > Signed-off-by: Zhiyong Tao > Signed-off-by: Erin Lo > Reviewed-by: Rob Herring Acked-by: Linus Walleij Please merge this through the ARM SoC tree.

Re: [PATCH] pinctrl: axp209: Fix NULL pointer dereference after allocation

On Tue, Mar 12, 2019 at 10:19 PM Aditya Pakki wrote: > axp20x_build_funcs_groups allocates groups via devm_kcalloc and tries to > dereference without checking for NULL. This patch avoids such a > scenario. > > Signed-off-by: Aditya Pakki Patch applied. Yours, Linus Walleij

Re: [PATCH v2] drivers: firmware: psci: add support for warm reset

On 2019-04-04 00:21, Aaro Koskinen wrote: From: Aaro Koskinen Add support for warm reset using SYSTEM_RESET2 introduced in PSCI 1.1 specification. There is already a patch sent by Sudeep for this support. -

Applied "ASoC: cs42l51: change mic bias DAPM" to the asoc tree

The patch ASoC: cs42l51: change mic bias DAPM has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus

Applied "spi: tegra114: dump SPI registers during timeout" to the spi tree

The patch spi: tegra114: dump SPI registers during timeout has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent

Applied "spi: spi-mem: Add support for Zynq QSPI controller" to the spi tree

The patch spi: spi-mem: Add support for Zynq QSPI controller has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent

Applied "spi: gpio: Drop unused pdev field in struct spi_gpio" to the spi tree

The patch spi: gpio: Drop unused pdev field in struct spi_gpio has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

Applied "spi: tegra114: de-assert CS before SPI mode change" to the spi tree

The patch spi: tegra114: de-assert CS before SPI mode change has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent

Applied "spi: gpio: Don't request CS GPIO in DT use-case" to the spi tree

The patch spi: gpio: Don't request CS GPIO in DT use-case has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Applied "spi: tegra114: set supported bits per word" to the spi tree

The patch spi: tegra114: set supported bits per word has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Applied "spi: tegra114: avoid reset call in atomic context" to the spi tree

The patch spi: tegra114: avoid reset call in atomic context has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent

Applied "spi: Don't call spi_get_gpio_descs() before device name is set" to the spi tree

The patch spi: Don't call spi_get_gpio_descs() before device name is set has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

Applied "spi: gpio: Drop mflags argument from spi_gpio_request()" to the spi tree

The patch spi: gpio: Drop mflags argument from spi_gpio_request() has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

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

Hi James, After merging the scsi tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: drivers/scsi/lpfc/lpfc_nvme.c:2140:1: warning: 'lpfc_nvme_lport_unreg_wait' defined but not used [-Wunused-function] lpfc_nvme_lport_unreg_wait(struct lpfc_vport *vport,

Re: [PATCH] mm:workingset use real time to judge activity of the file page

On Thu, Apr 04, 2019 at 11:30:17AM +0800, Zhaoyang Huang wrote: > +++ b/mm/workingset.c > @@ -159,7 +159,7 @@ >NODES_SHIFT + \ >MEM_CGROUP_ID_SHIFT) > #define EVICTION_MASK(~0UL >> EVICTION_SHIFT) > - > +#define EVICTION_JIFFIES

Re: [PATCH 4.14 000/121] 4.14.111-stable review

On Thu, 4 Apr 2019 at 14:24, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.14.111 release. > There are 121 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > >

Re: [PATCH 4.9 00/91] 4.9.168-stable review

On Thu, 4 Apr 2019 at 14:20, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.9.168 release. > There are 91 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > >

Re: [PATCH] mm:workingset use real time to judge activity of the file page

resend it via the right mailling list and rewrite the comments by ZY. On Thu, Apr 4, 2019 at 3:15 PM Michal Hocko wrote: > > [Fixup email for Pavel and add Johannes] > > On Thu 04-04-19 11:30:17, Zhaoyang Huang wrote: > > From: Zhaoyang Huang > > > > In previous implementation, the number of

Re: [PATCH] MT7621-SPI: spi-mt7621: Fix alignment and style problems Fixed Coding function and style issues

Hi! On Fri, Apr 5, 2019 at 2:53 AM Nilesh Hase wrote: > > Fix checkpatch issues: "CHECK: Alignment should match open parenthesis" > > Signed-off-by: Nilesh Hase > --- > drivers/staging/mt7621-spi/spi-mt7621.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git

Applied "ASoC: meson: axg-tdmout: add g12a support" to the asoc tree

The patch ASoC: meson: axg-tdmout: add g12a support has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Applied "ASoC: meson: add g12a compatibles" to the asoc tree

The patch ASoC: meson: add g12a compatibles has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus

Applied "ASoC: meson: axg-frddr: add g12a support" to the asoc tree

The patch ASoC: meson: axg-frddr: add g12a support has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Applied "regulator: core: Avoid potential deadlock on regulator_unregister" to the regulator tree

The patch regulator: core: Avoid potential deadlock on regulator_unregister has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in

Applied "ASoC: meson: axg-fifo: add g12a support" to the asoc tree

The patch ASoC: meson: axg-fifo: add g12a support has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Applied "ASoC: meson: axg-tdm-formatter: rework quirks settings" to the asoc tree

The patch ASoC: meson: axg-tdm-formatter: rework quirks settings has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours)

Applied "ASoC: meson: axg-toddr: add g12a support" to the asoc tree

The patch ASoC: meson: axg-toddr: add g12a support has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Re: [PATCH] staging: rtl8192u: ieee80211: add space around '==' and before '('

On 2019/4/5 9:56, Caio Salvador Rohwedder wrote: > Fix checkpatch coding style errors on rtl819x_TSProc.c > - space required before the open parenthesis '(' > - spaces required around that '==' > > Signed-off-by: Caio Salvador Rohwedder > --- >

Re: shmem_recalc_inode: unable to handle kernel NULL pointer dereference

On Tue, 2 Apr 2019, Hugh Dickins wrote: > On Sun, 31 Mar 2019, Hugh Dickins wrote: > > On Sun, 31 Mar 2019, Alex Xu (Hello71) wrote: > > > Excerpts from Vineeth Pillai's message of March 25, 2019 6:08 pm: > > > > On Sun, Mar 24, 2019 at 11:30 AM Alex Xu (Hello71) > > > > wrote: > > > >> > > > >>

[PATCH v4 5/6] lib/string: Add strscpy_pad() function

We have a function to copy strings safely and we have a function to copy strings and zero the tail of the destination (if source string is shorter than destination buffer) but we do not have a function to do both at once. This means developers must write this themselves if they desire this

[PATCH v4 6/6] lib: Add test module for strscpy_pad

Add a test module for the new strscpy_pad() function. Tie it into the kselftest infrastructure for lib/ tests. Acked-by: Kees Cook Signed-off-by: Tobin C. Harding --- lib/Kconfig.debug | 3 + lib/Makefile | 1 + lib/test_strscpy.c

[PATCH v4 4/6] lib: Use new kselftest header

We just added a new C header file for use with test modules that are intended to be run with kselftest. We can reduce code duplication by using this header. Use new kselftest header to reduce code duplication in test_printf and test_bitmap test modules. Acked-by: Kees Cook Signed-off-by: Tobin

[PATCH v4 3/6] kselftest: Add test module framework header

kselftest runs as a userspace process. Sometimes we need to test things from kernel space. One way of doing this is by creating a test module. Currently doing so requires developers to write a bunch of boiler plate in the module if kselftest is to be used to run the tests. This means we

[PATCH v4 1/6] lib/test_printf: Add empty module_exit function

Currently the test_printf module does not have an exit function, this prevents the module from being unloaded. If we cannot unload the module we cannot run the tests a second time. Add an empty exit function. Acked-by: Kees Cook Signed-off-by: Tobin C. Harding --- lib/test_printf.c | 6

[PATCH v4 2/6] kselftest: Add test runner creation script

Currently if we wish to use kselftest to run tests within a kernel module we write a small script to load/unload and do error reporting. There are a bunch of these under tools/testing/selftests/lib/ that are all identical except for the test name. We can reduce code duplication and improve

[PATCH v4 0/6] lib/string: Add strscpy_pad() function

Hi Shua, Here is the set with cleanup as suggested by Kees on v3. Configured, built, and tested all modules loaded by tools/testing/selftests/lib/*.sh >From previous cover letters ... While doing the testing for strscpy_pad() it was noticed that there is duplication in how test modules are

[PATCH v3] ubsan: Avoid unnecessary 128-bit shifts

If CONFIG_ARCH_SUPPORTS_INT128, s_max is 128 bits, and variable sign-extending shifts of such a double-word data type are a non-trivial amount of code and complexity. Do a single-word sign-extension *before* the cast to (s_max), greatly simplifying the object code. Rasmus Villemoes suggested

[PATCH] staging: rtl8192u: ieee80211: add space around '==' and before '('

Fix checkpatch coding style errors on rtl819x_TSProc.c - space required before the open parenthesis '(' - spaces required around that '==' Signed-off-by: Caio Salvador Rohwedder --- drivers/staging/rtl8192u/ieee80211/rtl819x_TSProc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

Re: [GIT PULL] MFD fixes for v5.1

The pull request you sent on Thu, 4 Apr 2019 10:37:47 +0100: > git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git tags/mfd-fixes-5.1 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/9db6ce4ecefb03698cb2875c1a46b9513303a9bf Thank you! -- Deet-doot-dot, I am a

Re: [GIT PULL] Power management material for v5.1-rc3

The pull request you sent on Thu, 4 Apr 2019 22:32:04 +0200: > git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git pm-5.1-rc4 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/20ad549488d53cb6742770b49e324a3396022da2 Thank you! -- Deet-doot-dot, I am a

Re: [GIT PULL] ACPI fix for v5.1-rc4

The pull request you sent on Thu, 4 Apr 2019 22:30:24 +0200: > git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git acpi-5.1-rc4 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/b512f71221d0bcb07ab32f3e958a84e164c85881 Thank you! -- Deet-doot-dot, I am a

Re: [GIT PULL] RISC-V Patches for 5.1-rc4

The pull request you sent on Thu, 04 Apr 2019 16:29:44 -0700 (PDT): > git://git.kernel.org/pub/scm/linux/kernel/git/palmer/riscv-linux.git > tags/riscv-for-linus-5.1-rc4 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/8e22ba96d44c4ad5f9970565c54ab1876448a5ca Thank

Re: [RFC][PATCH 03/16] sched: Wrap rq::lock access

We tried to comment those lines and it doesn’t seem to get rid of the performance regression we are seeing. Can you elaborate a bit more about the test you are performing, what kind of resources it uses ? I am running 1 and 2 Oracle DB instances each running TPC-C workload. The clients

Re: [PATCH 0/6 v3] sycalls: Remove args i and n from syscall_get_arguments()

On Thu, Apr 4, 2019 at 3:28 AM Steven Rostedt wrote: > > Is this something that can go into this -rc release or would you want > me to wait till the next merge window? > > The reason I ask, is that there's two arch patches in this series that > have stable tags attached to them. But I moved

[rcu:dev.2019.04.02a 35/52] drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c:45: undefined reference to `kfd_processes_srcu'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2019.04.02a head: 82d94d0c3c616bba12f1f2a7f2ea48a3363893c8 commit: 7950d16b08477aee3ea9aa77fb99a8650bc9378d [35/52] drivers/gpu/drm/amd: Dynamically allocate kfd_processes_srcu config: i386-randconfig-m1-04050455

[GIT PULL] extcon fixes for v5.1-rc4

Dear Greg, This is extcon-fixes pull request for v5.1-rc4. I add detailed description of this pull request on below. Please pull extcon with following updates. Best Regards, Chanwoo Choi The following changes since commit 79a3aaa7b82e3106be97842dedfd8429248896e6: Linux 5.1-rc3 (2019-03-31

[PATCH 6/6] Input: hv: Remove dependencies on PAGE_SIZE for ring buffer

Define the ring buffer size as a constant expression because it should not depend on the guest page size. Signed-off-by: Maya Nakamura --- drivers/input/serio/hyperv-keyboard.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/input/serio/hyperv-keyboard.c

[PATCH 5/6] HID: hv: Remove dependencies on PAGE_SIZE for ring buffer

Define the ring buffer size as a constant expression because it should not depend on the guest page size. Signed-off-by: Maya Nakamura --- drivers/hid/hid-hyperv.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/hid/hid-hyperv.c b/drivers/hid/hid-hyperv.c index

[PATCH 4/6] x86: hv: mmu.c: Replace page definitions with Hyper-V specific ones

Replace PAGE_SHIFT, PAGE_SIZE, and PAGE_MASK with HV_HYP_PAGE_SHIFT, HV_HYP_PAGE_SIZE, and HV_HYP_PAGE_MASK, respectively, because the guest page size and hypervisor page size concepts are different, even though they happen to be the same value on x86. Signed-off-by: Maya Nakamura ---

[PATCH 3/6] hv: vmbus: Replace page definition with Hyper-V specific one

Replace PAGE_SIZE with HV_HYP_PAGE_SIZE because the guest page size may not be 4096 on all architectures and Hyper-V always runs with a page size of 4096. Signed-off-by: Maya Nakamura --- drivers/hv/hyperv_vmbus.h | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git

[PATCH 2/6] x86: hv: hv_init.c: Replace alloc_page() with kmem_cache_alloc()

Switch from the function that allocates a single Linux guest page to a different one to use a Hyper-V page because the guest page size and hypervisor page size concepts are different, even though they happen to be the same value on x86. Signed-off-by: Maya Nakamura --- arch/x86/hyperv/hv_init.c

[PATCH 1/6] x86: hv: hyperv-tlfs.h: Create and use Hyper-V page definitions

Define HV_HYP_PAGE_SHIFT, HV_HYP_PAGE_SIZE, and HV_HYP_PAGE_MASK because the Linux guest page size and hypervisor page size concepts are different, even though they happen to be the same value on x86. Also, replace PAGE_SIZE with HV_HYP_PAGE_SIZE. Signed-off-by: Maya Nakamura ---

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

Jacek On 3/31/19 12:54 PM, Jacek Anaszewski wrote: > Add common LED color identifiers for use in Device Tree. > > Signed-off-by: Jacek Anaszewski > Cc: Baolin Wang > Cc: Pavel Machek > Cc: Dan Murphy > Cc: Daniel Mack > Cc: Linus Walleij > Cc: Oleh Kravchenko > Cc: Sakari Ailus > Cc:

[PATCH 0/6] hv: Remove dependencies on guest page size

The Linux guest page size and hypervisor page size concepts are different, even though they happen to be the same value on x86. Hyper-V code mixes up the two, so this patchset begins to address that by creating and using a set of Hyper-V specific page definitions. A major benefit of those new

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

On 3/31/19 12:54 PM, Jacek Anaszewski wrote: > Add initial set of common LED function definitions for use in Device Tree. > > Signed-off-by: Jacek Anaszewski > Cc: Baolin Wang > Cc: Pavel Machek > Cc: Dan Murphy > Cc: Daniel Mack > Cc: Linus Walleij > Cc: Oleh Kravchenko > Cc: Sakari Ailus

Re: [RFC PATCH 00/25] Accelerate page migration and use memcg for PMEM management

On 4/3/19 7:00 PM, Zi Yan wrote: From: Zi Yan Thanks to Dave Hansen's patches, which make PMEM as part of memory as NUMA nodes. How to use PMEM along with normal DRAM remains an open problem. There are several patchsets posted on the mailing list, proposing to use page migration to move

[PATCH V2 03/20] spi: tegra114: de-assert CS before SPI mode change

With SW CS, during the transfer completion CS is de-asserted by writing default command1 register value to SPI_COMMAND1 register. With this both mode and CS state are set at the same time and if current transfer mode is different to default SPI mode and if mode change happens prior to CS

[PATCH V2 04/20] spi: tegra114: avoid reset call in atomic context

This patch moves SPI controller reset out of spin lock. Signed-off-by: Sowjanya Komatineni --- drivers/spi/spi-tegra114.c | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/drivers/spi/spi-tegra114.c b/drivers/spi/spi-tegra114.c index c60e40cab0a0..d928a2c92a3d 100644

[PATCH V2 10/20] Documentation: devicetree: spi: add spi-lsbyte-first propery

spi-lsbyte-first optional property allows SPI slaves to choose byte order of little endian for transfers. Signed-off-by: Sowjanya Komatineni --- Documentation/devicetree/bindings/spi/spi-bus.txt | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH V2 07/20] spi: tegra114: set bus number based on id

This patch sets SPI device id from the device tree as the bus number. Signed-off-by: Sowjanya Komatineni --- drivers/spi/spi-tegra114.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/spi/spi-tegra114.c b/drivers/spi/spi-tegra114.c index 191233eae149..58f5059b339f 100644 ---

[PATCH V2 02/20] spi: tegra114: use unpacked mode for below 4 bytes

Packed mode expects minimum transfer length of 4 bytes. This patch fixes this by using unpacked mode for transfers less than 4 bytes. Signed-off-by: Sowjanya Komatineni --- drivers/spi/spi-tegra114.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

[PATCH V2 12/20] spi: tegra114: add support for LSBYTE_FIRST

Some SPI devices expects SPI transfers to be in Least significant byte first order and some devices expect Most significant byte first order. This patch adds SPI_LSBYTE_FIRST to the supported SPI mode list and also configures Tegra SPI controller accordingly. Signed-off-by: Sowjanya Komatineni

[PATCH V2 11/20] spi: expand mode support and add LSBYTE_FIRST mode

Some SPI Master controllers support configuring Least significant byte first or Most significant byte first order for transfers. Also some SPI slave devices expect bytes to be in Least significant first order and some devices expect Most significant first order. SPI driver declares mode and

[PATCH V2 13/20] spi: tegra114: add support for interrupt mask

This patch creates tegra_spi_soc_data structure to maintain and implement SPI HW feature differences between different Tegra chips and also creates a separate compatible string for T124/T210. Tegra210 and later has a separate interrupt mask register SPI_INTR_MASK for enabling or disabling

[PATCH V2 16/20] spi-summary: document set_cs_timing

This patch documents set_cs_timing SPI master method. Signed-off-by: Sowjanya Komatineni --- Documentation/spi/spi-summary | 6 ++ 1 file changed, 6 insertions(+) diff --git a/Documentation/spi/spi-summary b/Documentation/spi/spi-summary index 1721c1b570c3..1a63194b74d7 100644 ---

[PATCH V2 14/20] spi: tegra114: add support for gpio based cs

This patch adds supports for chip select control using GPIO if valid CS gpio exists. Signed-off-by: Sowjanya Komatineni --- drivers/spi/spi-tegra114.c | 59 ++ 1 file changed, 59 insertions(+) diff --git a/drivers/spi/spi-tegra114.c

[PATCH V2 09/20] spi: tegra114: add 3 wire transfer mode support

This patch adds 3 wire transfer support to SPI mode list along with its implementation. 3 wire or Bi-directional mode uses only one serial data pin for the transfer. SPI in master mode uses MOSI data line only and MISO data line is not used. Signed-off-by: Sowjanya Komatineni ---

[PATCH V2 18/20] spi: tegra114: add support for HW CS timing

This patch implements set_cs_timing SPI controller method to allow SPI client driver to configure device specific SPI CS timings. Signed-off-by: Sowjanya Komatineni --- drivers/spi/spi-tegra114.c | 48 -- 1 file changed, 46 insertions(+), 2

[PATCH V2 17/20] spi: add a method for configuring CS timing

This patch creates set_cs_timing SPI master optional method for SPI masters to implement configuring CS timing if applicable. This patch also creates spi_cs_timing accessory for SPI clients to use for requesting SPI master controllers to configure device requested CS setup time, hold time and

[PATCH V2 20/20] spi: tegra114: add support for tuning TX and RX trimmers

Tegra SPI controller has TX_CLK_TAP_DELAY and RX_CLK_TAP_DELAY in COMMAND2 register to tune the delay of the clock going out to external device during transmit and also for the clock coming in from external device during receive. TX/RX clock tap delays may vary based on the trace lengths of the

[PATCH V2 19/20] DT bindings: spi: document tx/rx clock delay properties

Tegra SPI controller has TX and RX trimmers to tuning the delay of SPI master clock with respect to the data. TX and RX tap values are based on the platform validation across the PVT and the trimmer values vary based on the trace lengths to the corresponding SPI devices. Signed-off-by: Sowjanya

[PATCH V2 01/20] spi: tegra114: fix PIO transfer

This patch fixes PIO mode transfer to use PIO bit in SPI_COMMAND1 register. Current driver uses DMA_EN instead of PIO bit. Signed-off-by: Sowjanya Komatineni --- drivers/spi/spi-tegra114.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/drivers/spi/spi-tegra114.c

[PATCH V2 06/20] spi: tegra114: set supported bits per word

Tegra SPI supports 4 through 32 bits per word. This patch sets bits_per_word_mask accordingly to support transfer with these bits per word. Signed-off-by: Sowjanya Komatineni --- drivers/spi/spi-tegra114.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/spi/spi-tegra114.c

[PATCH V2 15/20] spi: tegra114: add support for hw based cs

Tegra SPI controller supports both HW and SW based CS control for SPI transfers. This patch adds support for HW based CS control where CS is driven to active state during the transfer and is driven inactive at the end of the transfer directly by the HW. This patch enables the use of HW based CS

[PATCH V2 08/20] spi: tegra114: add dual mode support

This patch adds support for dual mode SPI transfer. Dual mode uses both MOSI and MISO lines in parallel where the data is interleaved on MOSI and MISO lines increasing the throughput. Packet from Tx FIFO is transmitted on both MOSI and MISO lines and packet to Rx FIFO is received from both MOSI

  1   2   3   4   5   6   7   8   9   10   >