On Thu, 4 Apr 2019 at 19:22, Sylwester Nawrocki wrote:
>
> From: Pankaj Dubey
>
> Exynos SoCs have Chipid, for identification of product IDs and SoC
> revisions. This patch intends to provide initialization code for all
> these functionalities, at the same time it provides some sysfs entries
> fo
Hello Stephen,
Thanks for taking care of this!
On Thu, 2019-04-04 at 14:53 -0700, Stephen Boyd wrote:
> We recently introduced a change to support devm clk lookups. That
> change
> introduced a code-path that used clk_find() without holding the
> 'clocks_mutex'. Unfortunately, clk_find() iterates
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: x86_64-rhel-7.6 (attached as
On 21.03.19 11:08:59, Robert Richter wrote:
> Our @cavium.com addresses will be switched off soon. Using
> @marvell.com addresses from now on.
>
> Cc: Jayachandran C
> Signed-off-by: Robert Richter
> ---
> MAINTAINERS | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Rob,
could you
We have got KASAN splat when tried to set /proc/sys/fs/file-max:
BUG: KASAN: global-out-of-bounds in __do_proc_doulongvec_minmax+0x3e4/0x8f0
Read of size 8 at addr 2f9b2980 by task file-max.sh/36819
Call trace:
dump_backtrace+0x0/0x3f8
show_stack+0x3c/0x60
dump_stack+0x150/
On Thu, 4 Apr 2019 at 14:38, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.0.7 release.
> There are 246 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.
>
> Respo
On 05/04/2019 06.57, Borislav Petkov wrote:
> From: Borislav Petkov
>
> ... to make its name readable to humans so that it can denote what that
> helper does.
I like the current color. It computes a*b+c with overflow checking at each
step. calc_size is
way too generic and doesn't say anything
On 05/04/19 10:55 AM, Naga Sureshkumar Relli wrote:
> 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.
On Fri, Apr 5, 2019 at 11:24 AM Christoph Hellwig wrote:
>
> 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
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 reproduced
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 f
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
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:
https://kernelci.org/build/stabl
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':
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;
> rich...@nod
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 al
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);
> >
Thanks!
Reviewed-by: Dan Carpenter
regards,
dan carpenter
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 --gi
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.
>
> Res
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:
> > 'lpfc_
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 f
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 the
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]
lpfc_nvme_lport_unr
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 wit
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() functions/macro
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
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
Documentation/device
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
b/arch/arm64/boo
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: G
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
Georg
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 stren
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(-)
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
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
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.
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
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.
-
https://lore.kernel.org/lkml/1525257003-8608-1-git-send-email-sudeep.ho...@arm.com/
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 dur
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 to
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
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 sen
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
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
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 Linus
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 t
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 hour
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
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,
^~~
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 (BITS_PER_LO
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
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.
>
> Resp
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 ref
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 a/drivers/stagi
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 Lin
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 durin
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 Linu
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 t
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 Linus
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) an
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 Linu
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
> ---
> drivers/staging/rtl8192u/ieee80211/rtl819x_TSProc
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:
> > > >>
> > > >>
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 functio
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
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
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 currentl
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 ++
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 maintai
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 bein
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 usin
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 --
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 bo
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 bo
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
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 you
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 driving
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 things
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
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 14:
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
b/driver
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 70
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
---
arch/x86/h
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 a/driver
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
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
---
arch/x86/inclu
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: Simo
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 defi
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
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 pag
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
de-assert,
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
-
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 a/Documentation/devicetree/bindings/spi/spi-bus.txt
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
--- a/dr
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 a/drivers/spi/spi-tegra114.
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
-
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 mode_b
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 interrup
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
--- a/Documen
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 b/drivers/spi/spi-
1 - 100 of 1396 matches
Mail list logo