Hi Bjorn,
On 15. 10. 19 1:23, Bjorn Helgaas wrote:
> On Tue, Oct 08, 2019 at 08:46:52AM -0700, Christoph Hellwig wrote:
>>> diff --git a/drivers/pci/Kconfig b/drivers/pci/Kconfig
>>> index a304f5ea11b9..9d259372fbfd 100644
>>> --- a/drivers/pci/Kconfig
>>> +++ b/drivers/pci/Kconfig
>>> @@ -52,7
The paths thermal_zone%d and cooling_device%d are not intuitive and the
numbers are subject to change due to device tree change. This usually
leads to tree traversal in userspace code.
The patch creates `tz-by-name' and `cdev-by-name' for thermal zone and
cooling_device respectively.
[ 943.034988] Unable to handle kernel paging request at virtual address
003106f2003c
[ 943.043653] Mem abort info:
[ 943.046679] ESR = 0x9645
[ 943.050428] Exception class = DABT (current EL), IL = 32 bits
[ 943.056643] SET = 0, FnV = 0
[ 943.060168] EA = 0, S1PTW = 0
[
On 2019/10/14 5:44, Pavel Machek wrote:
> On Sat 2019-10-12 21:55:24, Andrew Macks wrote:
>> Sorry for version typo in the previous message.
>>
>> In addition to 4.19, the issue was also backported to 4.14 and 5.2.
>>
>> 4.14, 4.19 and 5.2 are all missing the EINVAL fix from 5.3.
>
> Ouch.
>
>
Mark Rutland writes:
> On Tue, Oct 01, 2019 at 04:58:30PM +1000, Daniel Axtens wrote:
>> Hook into vmalloc and vmap, and dynamically allocate real shadow
>> memory to back the mappings.
>>
>> Most mappings in vmalloc space are small, requiring less than a full
>> page of shadow space.
On Sat 12 Oct 07:58 PDT 2019, nikitos...@gmail.com wrote:
> From: Nikita Travkin
>
> WCNSS is used on L8150 for WiFi and BT.
> Its firmware isn't relocatable and must be loaded at specific address.
>
> Signed-off-by: Nikita Travkin
Both patches applied
Thank you,
Bjorn
> ---
>
>>> @@ -2497,6 +2533,9 @@ void *__vmalloc_node_range(unsigned long size,
>>> unsigned long align,
>>> if (!addr)
>>> return NULL;
>>>
>>> + if (kasan_populate_vmalloc(real_size, area))
>>> + return NULL;
>>> +
>>
>> KASAN itself uses __vmalloc_node_range() to
> There is a potential problem here, as Will Deacon wrote up at:
>
>
> https://lore.kernel.org/linux-arm-kernel/20190827131818.14724-1-w...@kernel.org/
>
> ... in the section starting:
>
> | *** Other architecture maintainers -- start here! ***
>
> ... whereby the CPU can spuriously fault on
last_timestamp is not initialized and is zero after boot, or stop
to forward when nmi watchdog is disabled; and false positives still
is possible when restart NMI timer after stopping 120 seconds
so reassign last_timestamp always when enable nmi event
Fixes: 7edaeb6841df ("kernel/watchdog:
Hi,
On 10/15/19 7:57 AM, Simon Horman wrote:
> On Mon, Oct 14, 2019 at 11:04:28PM +0800, kbuild test robot wrote:
>> From: kbuild test robot
>>
>> drivers/net/can/m_can/m_can.c:783:9-10: WARNING: return of 0/1 in function
>> 'is_protocol_err' with return type bool
>>
>> Return statements in
On October 15, 2019 12:44:23 AM GMT+02:00, Andrew Morton
wrote:
>On Sun, 13 Oct 2019 00:31:01 +0300 Mike Rapoport
>wrote:
>
>> Until commit 92d12f9544b7 ("memblock: refactor internal allocation
>> functions") the maximal address for memblock allocations was forced
>to
>> memblock.current_limit
Hi Stephen,
On Fri, Oct 11, 2019 at 3:04 AM Stephen Rothwell wrote:
>
> Hi all,
>
> After merging the sound-asoc tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> In file included from include/sound/sof/dai-imx.h:11,
> from :
>
Hi Miquel,
> > > >
> > > > > Macronix AC series support using SET/GET_FEATURES to change
> > > > > Block Protection and Unprotection.
> > > > >
> > > > > MTD default _lock/_unlock function replacement by manufacturer
> > > > > postponed initialization.
> > > >
> > > > Why would we do that?
On Tue, Oct 15, 2019 at 05:04:28PM +1100, Michael . wrote:
> Good afternoon kernel developers
> Please accept my apology for contacting you directly about this. A
> small group of friends, some of whom are CCed here, have come together
> to try and find a solution to a problem that originated with
Add NOFAIL check for the strdup call, since the function
allocates memory and can return NULL. All strdup calls in
modpost are checked with NOFAIL.
Signed-off-by: Denis Efremov
---
scripts/mod/modpost.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/mod/modpost.c
Hi Joe,
On Mon, Oct 14, 2019 at 4:48 PM Joe Perches wrote:
> On Mon, 2019-10-14 at 11:20 +0200, Geert Uytterhoeven wrote:
> > On Tue, Oct 8, 2019 at 8:10 PM Geert Uytterhoeven
> > wrote:
> > > On Tue, Oct 8, 2019 at 7:02 PM Joe Perches wrote:
> > > > On Tue, 2019-10-08 at 17:28 +0200, Geert
From: Peter Ujfalusi
commit f90ec6cdf674248dcad85bf9af6e064bf472b841 upstream
Set memory bandwidth limit to filter out resolutions above 720p@60Hz to
avoid underflow errors due to the bandwidth needs of higher resolutions.
am43xx can not provide enough bandwidth to DISPC to correctly handle
From: Roger Quadros
commit 163be6ff7739b12ff300d77897d340f661821da2 upstream
If a gadget driver is in the pending drivers list, a UDC
becomes available and udc_bind_to_driver() fails, then it
gets deleted from the pending list.
i.e. list_del(>pending) in check_pending_gadget_drivers().
Then if
From: Peter Ujfalusi
commit 7b2db65b59c30d58c129d3c8b2101feca686155a upstream
24 bits is supported in all modes and 16 bit only when the codec is slave
and the DAI is set to RIGHT_J.
Remove the unsupported sample format.
Signed-off-by: Peter Ujfalusi
Link:
From: Suman Anna
commit 389ce1a7c5279ebfb682fab220b4021b2bd49c8b upstream
The gic-its node unit-address has an additional zero compared
to the actual reg value. Fix it.
Fixes: ea47eed33a3f ("arm64: dts: ti: Add Support for AM654 SoC")
Reported-by: Robert Tivy
Signed-off-by: Suman Anna
Thank you for your prompt reply Dominik, I have asked everyone in the
discussion on Notebook review to gather the information required and
either post it there so I can reply or post it here in the list if it
is from someone in the CC list.
Also thank you for replying to us all and not just
On Sun, Oct 6, 2019 at 8:22 AM Hans de Goede wrote:
>
> Anyways back the code to add a usb role switch notifier. I do
> not think that this is a good idea, this is making "core" changes
> to deal with a special case. If you are going to use a notfier for
> this then IMHO the notifier should be
From: Peng Fan
The PLL enum definition is not used, so drop it.
Signed-off-by: Peng Fan
---
drivers/clk/imx/clk-imx8mn.c | 14 --
1 file changed, 14 deletions(-)
diff --git a/drivers/clk/imx/clk-imx8mn.c b/drivers/clk/imx/clk-imx8mn.c
index 28467db10c69..6ab6e9228962 100644
---
On Mon, 2019-10-14 at 12:31 +0530, Vinod Koul wrote:
> [External]
>
Hey,
> On 13-09-19, 17:54, Alexandru Ardelean wrote:
> > From: Rodrigo Alencar
> >
> > dmaengine_slave_config is called by dmaengine_pcm_hw_params when using
> > axi-i2s with axi-dmac. If device_config is NULL, -ENOSYS is
On Tue, Oct 15, 2019 at 06:37:54AM +, Jeroen Hofstee wrote:
> Hi,
>
> On 10/15/19 7:57 AM, Simon Horman wrote:
> > On Mon, Oct 14, 2019 at 11:04:28PM +0800, kbuild test robot wrote:
> >> From: kbuild test robot
> >>
> >> drivers/net/can/m_can/m_can.c:783:9-10: WARNING: return of 0/1 in
On Mon, Oct 14, 2019 at 06:26:04PM -0700, Davidlohr Bueso wrote:
> On Sat, 12 Oct 2019, Manfred Spraul wrote:
> > Invalid would be:
> > smp_mb__before_atomic();
> > atomic_set();
>
> fyi I've caught a couple of naughty users:
>
> drivers/crypto/cavium/nitrox/nitrox_main.c
>
accuratly => accurately
while at it change `clock source` to clocksource to make
it align with its usage at other places.
Signed-off-by: Mukesh Ojha
---
kernel/time/jiffies.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/time/jiffies.c b/kernel/time/jiffies.c
witin => within
Signed-off-by: Mukesh Ojha
---
kernel/time/time.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/time/time.c b/kernel/time/time.c
index 5c54ca6..d31661c4 100644
--- a/kernel/time/time.c
+++ b/kernel/time/time.c
@@ -179,7 +179,7 @@ int
iterrupts => interrupts
stratight => straight
Minor comment correction.
Signed-off-by: Mukesh Ojha
---
kernel/sched/idle.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/sched/idle.c b/kernel/sched/idle.c
index 8dad5aa..2df8ae1 100644
--- a/kernel/sched/idle.c
I am just going to use the word "O-S" here. So now its called O-S Varanger, and
that is probably the last of detail added on this.
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Sunday 13. October 2019 kl. 23:14, Ywe Cærlyn wrote:
> Gracified it even a bit more 0S!
Hi, Jonathan
On 2019/10/14 下午6:32, Jonathan Cameron wrote:
On Mon, 14 Oct 2019 14:48:54 +0800
Zhangfei Gao wrote:
From: Kenneth Lee
Uacce (Unified/User-space-access-intended Accelerator Framework) targets to
provide Shared Virtual Addressing (SVA) between accelerators and processes.
So
On October 15, 2019 2:46:59 AM GMT+02:00, Will Deacon wrote:
>On Sat, Sep 28, 2019 at 11:02:26AM +0300, Mike Rapoport wrote:
>> From: Mike Rapoport
>>
>> arm64 calls memblock_free() for the initrd area in its implementation
>of
>> free_initrd_mem(), but this call has no actual effect that late
Hi Minchan,
On Mon, Oct 14, 2019 at 6:41 PM Minchan Kim wrote:
>
> On Thu, Oct 10, 2019 at 11:04:14PM +0300, Vitaly Wool wrote:
> > The coming patchset is a new take on the old issue: ZRAM can currently be
> > used only with zsmalloc even though this may not be the optimal combination
> > for
On Fri, Oct 11, 2019 at 06:51:29PM +0200, Nicolas Saenz Julienne wrote:
> It's more explicit and lets dma-direct handle the specifics of how to
> translate addresses.
>
> On top of that get rid of warnings as, since the introduction of commit
> 6fa1d28e38c ("sh: use generic dma_noncoherent_ops"),
On Mon, Oct 14, 2019 at 01:15:53PM -0600, Tuowen Zhao wrote:
> On Tue, 2019-10-15 at 02:46 +0800, kbuild test robot wrote:
> > -O ~/bin/make.cross
> > chmod +x ~/bin/make.cross
> > # save the attached .config to linux build tree
> > GCC_VERSION=7.4.0 make.cross ARCH=sparc64
On Mon, Oct 14, 2019 at 08:58:03AM -0700, Bart Van Assche wrote:
> On 10/14/19 5:16 AM, Colin King wrote:
> > const char *ret = trace_seq_buffer_ptr(p);
> > sector_t lba = 0, txlen = 0;
> > - lba |= (cdb[2] << 24);
> > + lba |= ((u64)cdb[2] << 24);
> > lba |= (cdb[3] << 16);
> >
On Mon 2019-10-14 11:17:19, Steven Rostedt wrote:
> On Mon, 14 Oct 2019 12:59:23 +0200
> Miroslav Benes wrote:
>
> > int
> > ftrace_enable_sysctl(struct ctl_table *table, int write,
> > void __user *buffer, size_t *lenp,
> > @@ -6740,8 +6754,6 @@ ftrace_enable_sysctl(struct
> -Original Message-
> From: Russell King - ARM Linux admin
> Sent: 2019年9月25日 0:39
> To: Xiaowei Bao
> Cc: Z.q. Hou ; bhelg...@google.com;
> robh...@kernel.org; mark.rutl...@arm.com; shawn...@kernel.org; Leo Li
> ; kis...@ti.com; lorenzo.pieral...@arm.com; M.h. Lian
> ;
On Mon, Oct 14, 2019 at 07:49:56PM +0200, Manfred Spraul wrote:
> From 61c85a56994e32ea393af9debef4cccd9cd24abd Mon Sep 17 00:00:00 2001
> From: Manfred Spraul
> Date: Fri, 11 Oct 2019 10:33:26 +0200
> Subject: [PATCH] Update Documentation for _{acquire|release|relaxed}()
>
> When adding the
> -Original Message-
> From: Russell King - ARM Linux admin
> Sent: 2019年9月25日 0:50
> To: Xiaowei Bao
> Cc: Z.q. Hou ; bhelg...@google.com;
> robh...@kernel.org; mark.rutl...@arm.com; shawn...@kernel.org; Leo Li
> ; kis...@ti.com; lorenzo.pieral...@arm.com; M.h. Lian
> ;
On Thu, Oct 10, 2019 at 12:47:31PM +0200, Michal Simek wrote:
> On 08. 10. 19 17:46, Christoph Hellwig wrote:
> > On Tue, Oct 08, 2019 at 12:34:47PM +0200, Michal Simek wrote:
> >> index e5c9170a07fc..83417105c00a 100644
> >> --- a/arch/microblaze/include/asm/Kbuild
> >> +++
On Okt 15 2019, Atish Patra wrote:
> Nope. This is only reproducible in RISC-V Fedora Gnome desktop image on
> a HiFive Unleashed + Microsemi Expansion. Just to clarify, there is no
> issue with OpenEmbedded disk image related to memory layout. It was a
> userspace thing.
Does it also happen
Hi,
On 15/10/19 12:08 AM, Faiz Abbas wrote:
> Add a write memory barrier to make sure that descriptors are actually
> written to memory before ringing the doorbell.
>
> Signed-off-by: Faiz Abbas
> ---
>
> This patch fixes a very infrequent ADMA error (1 out of 100 times) that
> I have been
On Sun 13-10-19 14:28:06, syzbot wrote:
> syzbot has found a reproducer for the following crash on:
>
> HEAD commit:da940012 Merge tag 'char-misc-5.4-rc3' of git://git.kernel..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=12cfdf4f60
> kernel
Hi Mason,
masonccy...@mxic.com.tw wrote on Tue, 15 Oct 2019 10:33:29 +0800:
> Hi Boris,
>
>
> > > > > + nand_select_target(chip, 0);
> > > >
> > > > On several NAND controllers there is no way to act on the CS line
> > > > without actually writing bytes to the NAND chip. So basically
On Fri, Oct 11, 2019 at 10:21 AM Oded Gabbay wrote:
> Add a new opcode to the INFO IOCTL to allow the user application to
> retrieve the ASIC's current and maximum clock rate. The rate is
> returned in MHz.
>
> Signed-off-by: Oded Gabbay
Reviewed-by: Tomer Tayar
On 10/14/2019 5:38 PM, Rafael J. Wysocki wrote:
On Friday, October 11, 2019 3:30:41 PM CEST Yin, Fengwei wrote:
On 10/11/2019 5:05 PM, Rafael J. Wysocki wrote:
Sorry for the delay.
No problem.
On Monday, September 9, 2019 9:39:37 AM CEST Yin Fengwei wrote:
In function
In function acpi_idle_do_entry(), an ioport access is used for dummy
wait to guarantee hardware behavior. But it could trigger unnecessary
vmexit in virtualization environment.
If we run linux as guest and export all available native C state to
guest, we did see many PM timer access triggered
On Tue, Oct 15, 2019 at 5:00 AM Stephen Rothwell wrote:
> After merging the drivers-x86 tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/platform/x86/huawei-wmi.c: In function 'huawei_wmi_exit':
> drivers/platform/x86/huawei-wmi.c:890:41: error: 'struct
On Fri 11-10-19 18:00:39, Ben Dooks wrote:
> The declarations of __block_write_begin_int and guard_bio_eod
> are needed from internal.h so include it to fix the following
> sparse warnings:
>
> fs/buffer.c:1930:5: warning: symbol '__block_write_begin_int' was not
> declared. Should it be static?
On Tue, 2019-10-15 at 00:43 -0700, Christoph Hellwig wrote:
> On Fri, Oct 11, 2019 at 06:51:29PM +0200, Nicolas Saenz Julienne wrote:
> > It's more explicit and lets dma-direct handle the specifics of how to
> > translate addresses.
> >
> > On top of that get rid of warnings as, since the
On Sat, Oct 12, 2019 at 12:15:56PM -0700, Daniel Colascione wrote:
> Add functions forwarding from the old names to the new ones so we
> don't need to change any callers.
Independent of the usefulness of the interface (I'll let other comment,
but you defintively want to talk to Al Viro), adding a
On Sat, Oct 12, 2019 at 12:15:57PM -0700, Daniel Colascione wrote:
> A secure anonymous file is one we hooked up to its own inode (as
> opposed to the shared inode we use for non-secure anonymous files). A
> new selinux hook gives security modules a chance to initialize, label,
> and veto the
On Wed 09-10-19 17:45:09, Kirill A. Shutemov wrote:
> THPs on deferred split queue got split by shrinker if memory pressure
> comes.
>
> In absence of memory pressure, there is no bound on how long the
> deferred split queue can be. In extreme cases, deferred queue can grow
> to tens of
Mapped, dirty and writeback pages are also counted in per-lruvec stats.
These counters needs update when page is moved between cgroups.
Fixes: 00f3ca2c2d66 ("mm: memcontrol: per-lruvec stats infrastructure")
Signed-off-by: Konstantin Khlebnikov
---
mm/memcontrol.c | 18 --
1
When using following operations:
date -s "21190910 19:20:00"
hwclock -w
to change date from 2019 to 2119 for test, it will fail on Hygon
Dhyana and AMD Zen CPUs, while the same operations run ok on Intel i7
platform.
MC146818 driver use function mc146818_set_time() to set register
Hi Linus,
Please pull dmi subsystem fixes for Linux v5.4 from:
git://git.kernel.org/pub/scm/linux/kernel/git/jdelvare/staging.git dmi-for-linus
drivers/firmware/dmi_scan.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
---
Jean Delvare (1):
firmware: dmi: Fix
On 15/10/2019 00:29, Sasha Levin wrote:
On Mon, Oct 14, 2019 at 07:56:01PM +0800, John Garry wrote:
From: Jeremy Linton
Commit bbd1b70639f785a970d998f35155c713f975e3ac upstream.
ACPI 6.3 adds a flag to the CPU node to indicate whether
the given PE is a thread. Add a function to return that
On Tue, Oct 15, 2019 at 08:29:22AM +0530, Pankaj Dubey wrote:
> From: Anvesh Salveru
>
> In some platforms, PCIe PHY may have issues which will prevent linkup
> to happen in GEN3 or higher speed. In case equalization fails, link will
> fallback to GEN1.
>
> DesignWare controller gives
On Tue 15-10-19 11:09:59, Konstantin Khlebnikov wrote:
> Mapped, dirty and writeback pages are also counted in per-lruvec stats.
> These counters needs update when page is moved between cgroups.
Please describe the user visible effect.
> Fixes: 00f3ca2c2d66 ("mm: memcontrol: per-lruvec stats
On Tue, Oct 15, 2019 at 7:11 AM Daniel Drake wrote:
>
> On Mon, Oct 14, 2019 at 7:25 PM Rafael J. Wysocki wrote:
> > Since there is no reason for that difference to exist, modify
> > pci_power_up() to follow pci_set_power_state() more closely and
> > invoke __pci_start_power_transition() from
On 15/10/19 05:16, Sean Christopherson wrote:
> I think short and sweet is enough for the prompt, with the details of how
> build both buried in the help text.
>
> choice
> prompt "KVM built-in support"
> help
> Here be a long and detailed help text.
>
> config KVM_AMD_STATIC
On Tue, Oct 15, 2019 at 10:08:55AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the pm tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> In file included from include/linux/irqchip.h:14,
> from arch/arm/kernel/irq.c:26:
>
Hi,
On 03/10/2019 02:16, John Stultz wrote:
From: Yu Chen
The Type-C drivers use USB role switch API to inform the
system about the negotiated data role, so registering a role
switch in the DRD code in order to support platforms with
USB Type-C connectors.
Cc: Greg Kroah-Hartman
Cc: Rob
Oh come on, you sent that patch only a week ago and v2 had a so obvious
mistake that my trust in your code quality is now very low.
On 15/10/2019 16:08:27+0800, Jinke Fan wrote:
> When using following operations:
> date -s "21190910 19:20:00"
> hwclock -w
> to change date from 2019 to 2119 for
On 28/09/19 19:23, Andrea Arcangeli wrote:
> Reducing this list to only EXIT_REASON_MSR_WRITE,
> EXIT_REASON_PREEMPTION_TIMER, EXIT_REASON_EPT_MISCONFIG,
> EXIT_REASON_IO_INSTRUCTION increases the computation time of the
> hrtimer guest testcase on Haswell i5-4670T CPU @ 2.30GHz by 7% with
> the
Both build_mem_topology() and rm_rf_depth_pat() have resource leak of
closedir() on the error paths.
Fix this by calling closedir() before function returns.
Fixes: e2091cedd51b ("perf tools: Add MEM_TOPOLOGY feature to perf data file")
Fixes: cdb6b0235f17 ("perf tools: Add pattern name checking
On Mon, Oct 14, 2019 at 01:03:08PM -0400, Joel Fernandes (Google) wrote:
> In current mainline, the degree of access to perf_event_open(2) system
> call depends on the perf_event_paranoid sysctl. This has a number of
> limitations:
>
> 1. The sysctl is only a single value. Many types of accesses
Hello Simon,
On 10/15/19 9:13 AM, Simon Horman wrote:
> On Tue, Oct 15, 2019 at 06:37:54AM +, Jeroen Hofstee wrote:
>> Hi,
>>
>> On 10/15/19 7:57 AM, Simon Horman wrote:
>>> On Mon, Oct 14, 2019 at 11:04:28PM +0800, kbuild test robot wrote:
From: kbuild test robot
On 15/10/19 05:18, Sean Christopherson wrote:
>> The KVM config option should be changed to a bool and its help text
>> updated. Maybe something similar to the help for VIRTUALIZATION to make
>> it clear that enabling KVM on its own does nothing.
> Making KVM a bool doesn't work well, keeping it
On Mon, Oct 14, 2019 at 03:27:35PM -0700, Luck, Tony wrote:
> You need a plausible start point for the "when to worry the user"
> message. Maybe that is your "max value"?
Yes, that would be a good start.
You need that anyway because the experimentations you guys did to get
your numbers have
Add support for rk3308 SoC from rockchip.
Jianqun Xu (2):
dt-bindings: pinctrl: rockchip: add rk3308 SoC support
pinctrl: rockchip: add rk3308 SoC support
.../bindings/pinctrl/rockchip,pinctrl.txt | 1 +
drivers/pinctrl/pinctrl-rockchip.c| 382 +-
2 files
Add rk3308 SoC support to rockchip pinctrl.
Acked-by: Rob Herring
Reviewed-by: Heiko Stuebner
Signed-off-by: Jianqun Xu
---
changes since v2:
- Add Acked-by: Rob Herring
changes since v1:
- Add Reviewed-by: Heiko Stuebner
Documentation/devicetree/bindings/pinctrl/rockchip,pinctrl.txt | 1
This patch do support pinctrl for RK3308 SoCs.
Reviewed-by: Heiko Stuebner
Signed-off-by: Jianqun Xu
---
changes since v2:
- Fix increase offset according to iomux width
changes since v1:
- Add type case for pull get/set
- Add Reviewed-by: Heiko Stuebner
drivers/pinctrl/pinctrl-rockchip.c |
On 26/09/2019 20:30, Anders Roxell wrote:
When building allmodconfig KCONFIG_ALLCONFIG=$(pwd)/arch/arm64/configs/defconfig
CONFIG_CMDLINE_FORCE gets enabled. Which forces the user to pass the
full cmdline to CONFIG_CMDLINE="...".
Rework so that we disable CONFIG_CMDLINE_FORCE in the defconfig
> On Oct 15, 2019, at 12:52 AM, Guilherme G. Piccoli
> wrote:
>
> Kdump kernels won't benefit from hugepages - in fact it's quite opposite,
> it may be the case hugepages on kdump kernel can lead to OOM if kernel
> gets unable to allocate demanded pages due to the fact the preallocated
>
On Thu, Oct 10, 2019 at 7:55 PM Paolo Bonzini wrote:
>
> On 10/10/19 09:30, Suleiman Souhlal wrote:
> > +kvm_hostclock_enable(struct clocksource *cs)
> > +{
> > + pv_timekeeper_enabled = 1;
> > +
> > + old_vclock_mode = kvm_clock.archdata.vclock_mode;
> > +
I don't think it makes sense for "end" to be negative or for even for it
to be less than "start". That also means that "start" can't be more
than 100 which is good.
Fixes: b7527d0f4502 ("platform/x86: huawei-wmi: Add battery charging
thresholds")
Signed-off-by: Dan Carpenter
---
On Tue, Oct 15, 2019 at 01:33:48PM +0800, Jin Yao wrote:
SNIP
> +enum {
> + PERF_HPP_REPORT__BLOCK_TOTAL_CYCLES_COV,
> + PERF_HPP_REPORT__BLOCK_LBR_CYCLES,
> + PERF_HPP_REPORT__BLOCK_CYCLES_PCT,
> + PERF_HPP_REPORT__BLOCK_AVG_CYCLES,
> + PERF_HPP_REPORT__BLOCK_RANGE,
> +
Hi Chuhong,
Thanks for the patch.
On Mon 14 Oct 2019 at 03:08, Chuhong Yuan wrote:
> devm_regulator_get may return an error but mipi_csis_phy_init misses
> a check for it.
> This may lead to problems when regulator_set_voltage uses the unchecked
> pointer.
> This patch adds a check for
On platforms implementing CPU power management, the CPUidle subsystem
can allow CPUs to enter idle states where local timers logic is lost on power
down. To keep the software timers functional the kernel relies on an
always-on broadcast timer to be present in the platform to relay the
interrupt
On 15/10/2019 11.20, Michal Hocko wrote:
On Tue 15-10-19 11:09:59, Konstantin Khlebnikov wrote:
Mapped, dirty and writeback pages are also counted in per-lruvec stats.
These counters needs update when page is moved between cgroups.
Please describe the user visible effect.
Surprisingly I
On Tue, Oct 15, 2019 at 04:30:08PM +0800, Yunfeng Ye wrote:
> Both build_mem_topology() and rm_rf_depth_pat() have resource leak of
> closedir() on the error paths.
>
> Fix this by calling closedir() before function returns.
>
> Fixes: e2091cedd51b ("perf tools: Add MEM_TOPOLOGY feature to perf
On Mon, Oct 14, 2019 at 03:41:38PM -0700, Srinivas Pandruvada wrote:
> So some users who had issues in their systems can try with this patch.
> We can get rid of this, till it becomes real issue.
We don't add command line parameters which we maybe can get rid of
later.
> The temperature is
On Mon, Oct 14, 2019 at 12:10:47PM -0500, Gustavo A. R. Silva wrote:
> Store SYMBOL_ANNOTATE_ERRNO__BPF_MISSING_BTF in variable *ret*, instead
> of returning in the middle of the function and leaking multiple
> resources: prog_linfo, btf, s and bfdf.
>
> Addresses-Coverity-ID: 1454832
On 15/10/2019 04:06, Hanjun Guo wrote:
-/*
> - * PMCG model identifiers for use in smmu pmu driver. Please note
> - * that this is purely for the use of software and has nothing to
> - * do with hardware or with IORT specification.
> - */
> -#define IORT_SMMU_V3_PMCG_GENERIC0x /*
On 15. 10. 19 9:47, Christoph Hellwig wrote:
> On Thu, Oct 10, 2019 at 12:47:31PM +0200, Michal Simek wrote:
>> On 08. 10. 19 17:46, Christoph Hellwig wrote:
>>> On Tue, Oct 08, 2019 at 12:34:47PM +0200, Michal Simek wrote:
index e5c9170a07fc..83417105c00a 100644
---
Add cast to fix the following sparse warning:
warning: restricted __be16 degrades to integer
Signed-off-by: Wambui Karuga
---
drivers/staging/octeon/ethernet-tx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/octeon/ethernet-tx.c
On Tue, Oct 15, 2019 at 10:54:14AM +0800, Yunfeng Ye wrote:
> There is a memory leak problem in the failure paths of
> build_cl_output(), so fix it.
>
> Signed-off-by: Yunfeng Ye
Acked-by: Jiri Olsa
thanks,
jirka
> ---
> tools/perf/builtin-c2c.c | 14 +-
> 1 file changed, 9
Add the LX2160A PCIe EP node.
Signed-off-by: Xiaowei Bao
---
v2:
- No change.
arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi | 56 ++
1 file changed, 56 insertions(+)
diff --git a/arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi
This patch set are for adding Mobiveil EP driver and adding PCIe Gen4
EP driver of NXP Layerscape platform.
This patch set depends on:
https://patchwork.kernel.org/project/linux-pci/list/?series=159139
Xiaowei Bao (6):
PCI: mobiveil: Add the EP driver support
dt-bindings: Add DT binding for
Add the documentation for the Device Tree binding of the layerscape
PCIe GEN4 controller with EP mode.
Signed-off-by: Xiaowei Bao
---
v2:
- remove the status entry in EP Example.
.../bindings/pci/layerscape-pcie-gen4.txt | 27 +-
1 file changed, 26 insertions(+),
Add the layerscape PCIE GEN4 EP device support in pci_endpoint_test driver.
Signed-off-by: Xiaowei Bao
---
v2:
- No change.
drivers/misc/pci_endpoint_test.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/misc/pci_endpoint_test.c b/drivers/misc/pci_endpoint_test.c
index
Errata: unsupported request error on inbound posted write
transaction, PCIe controller reports advisory error instead
of uncorrectable error message to RC.
Signed-off-by: Xiaowei Bao
---
v3:
- Use BIT replce the expression.
drivers/pci/controller/mobiveil/pcie-layerscape-gen4-ep.c | 13
Add the EP driver support for Mobiveil base on endpoint framework.
Signed-off-by: Xiaowei Bao
---
v2:
- Modify the Copyright.
MAINTAINERS| 1 +
drivers/pci/controller/mobiveil/Kconfig| 5 +
drivers/pci/controller/mobiveil/Makefile
This PCIe controller is based on the Mobiveil GPEX IP, it work in EP
mode if select this config opteration.
Signed-off-by: Xiaowei Bao
---
v2:
- Modify the Copyright.
MAINTAINERS| 2 +
drivers/pci/controller/mobiveil/Kconfig| 17 ++-
On Mon, Oct 14, 2019 at 02:21:00PM -0700, Srinivas Pandruvada wrote:
> Some modern systems have very tight thermal tolerances. Because of this
> they may cross thermal thresholds when running normal workloads (even
> during boot). The CPU hardware will react by limiting power/frequency
> and using
On Fri, Oct 11, 2019 at 01:31:08PM -0700, Jim Mattson wrote:
> On Tue, Sep 17, 2019 at 1:52 AM Yang Weijiang wrote:
> >
> > Co-developed-by: yi.z.zh...@linux.intel.com
> > Signed-off-by: yi.z.zh...@linux.intel.com
> > Signed-off-by: Yang Weijiang
> > ---
> >
On Mon, Oct 14, 2019 at 03:27:35PM -0700, Luck, Tony wrote:
> On Mon, Oct 14, 2019 at 11:36:18PM +0200, Borislav Petkov wrote:
> > This description is already *begging* for this delay value to be
> > automatically set by the kernel. Putting yet another knob in front of
> > the user who doesn't
> -Original Message-
> From: Christoph Hellwig
> Sent: Tuesday, October 15, 2019 1:46 PM
> To: Pankaj Dubey
> Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org;
> bhelg...@google.com; andrew.mur...@arm.com; lorenzo.pieral...@arm.com;
> gustavo.pimen...@synopsys.com;
1 - 100 of 1039 matches
Mail list logo