From: Tao Ren
Add hardware monitoring driver for the Maxim MAX127 chip.
MAX127 min/max range handling code is inspired by the max197 driver.
Signed-off-by: Tao Ren
---
Changes in v2:
- replace devm_hwmon_device_register_with_groups() with
devm_hwmon_device_register_with_info() API.
On Thu, 19 Nov 2020 at 00:05, Nick Desaulniers wrote:
>
> On Fri, Nov 13, 2020 at 11:34 AM Nick Desaulniers
> wrote:
> >
> > On Thu, Nov 12, 2020 at 10:06 PM Ard Biesheuvel wrote:
> > >
> > > On Fri, 13 Nov 2020 at 01:53, Nathan Chancellor
> > > wrote:
> > > >
> > > > On Thu, Nov 12, 2020 at
From: Tao Ren
The patch series adds hardware monitoring driver for the Maxim MAX127
chip.
Patch #1 adds the max127 hardware monitoring driver, and patch #2 adds
documentation for the driver.
Tao Ren (2):
hwmon: (max127) Add Maxim MAX127 hardware monitoring driver
docs: hwmon: Document
Just got the following when running perf.
[ 648.247718] ==
[ 648.247725] WARNING: possible circular locking dependency detected
[ 648.247734] 5.10.0-rc4-next-20201118+ #1 Not tainted
[ 648.247740
On 11/18/20 1:28 AM, Barnabás Pőcze wrote:
Hi
I have attached some thoughts and comments inline.
Thanks!
2020. november 15., vasárnap 20:21 keltezéssel, Maximilian Luz írta:
[...]
+/* -- Event notifier/callbacks. -
*/
+/*
+ * The notifier
On Fri, Nov 13, 2020 at 11:34 AM Nick Desaulniers
wrote:
>
> On Thu, Nov 12, 2020 at 10:06 PM Ard Biesheuvel wrote:
> >
> > On Fri, 13 Nov 2020 at 01:53, Nathan Chancellor
> > wrote:
> > >
> > > On Thu, Nov 12, 2020 at 04:44:46PM -0800, Nick Desaulniers wrote:
> > > > On Thu, Nov 12, 2020 at
Hi Greg,
On 11/18/20 9:27 AM, Grzegorz Jaszczyk wrote:
> Hi Suman,
>
> On Tue, 17 Nov 2020 at 21:40, Suman Anna wrote:
>>
>> Hi Greg,
>>
>> On 11/14/20 2:46 AM, Grzegorz Jaszczyk wrote:
>>> The firmware blob can contain optional ELF sections: .resource_table
>>> section and .pru_irq_map one.
Add binding doc for fsl,spba-bus.
Signed-off-by: Adam Ford
---
make dt_binding_check -j8 |grep spba
DTEXDocumentation/devicetree/bindings/bus/fsl,spba-bus.example.dts
DTC Documentation/devicetree/bindings/bus/fsl,spba-bus.example.dt.yaml
CHECK
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: c2e7554e1b85935d962127efa3c2a76483b0b3b6
commit: 2ac6795fcc085e8d03649f1bbd0d70aaff612cad clocksource/drivers: Add CLINT
timer driver
date: 3 months ago
config: riscv-randconfig-s032-20201118 (attached
ARE YOU IN NEED OF LOAN @3% INTEREST RATE FOR BUSINESS AND PRIVATE
PURPOSES? IF YES:
FILL AND RETURN
Name: ===
Amount needed: ===
Duration: ==
country ===
Purpose: ===
Mobile number
Dear Sir/Madam
On 11/16/20 5:33 AM, Oscar Salvador wrote:
> On Fri, Nov 13, 2020 at 06:59:35PM +0800, Muchun Song wrote:
>> +void __init hugetlb_vmemmap_init(struct hstate *h)
>> +{
>> +unsigned int order = huge_page_order(h);
>> +unsigned int vmemmap_pages;
>> +
>> +vmemmap_pages = ((1 << order) *
Hi Vincent (and all CCed), I'm sorry to ping about such "old" patch, but
we experienced a similar condition to what this patch addresses; it's an
older kernel (4.15.x) but when suggesting the users to move to an
updated 5.4.x kernel, we noticed that this patch is not there, although
similar ones
On Tue, Nov 17, 2020 at 10:29AM -0800, Paul E. McKenney wrote:
[...]
> But it would be good to get the kcompactd() people to look at this (not
> immediately seeing who they are in MAINTAINERS). Perhaps preemption is
> disabled somehow and I am failing to see it.
>
> Failing that, maybe someone
PCIe r6.0, sec 7.5.3.18, defines a new 64.0 GT/s bit in the Supported
Link Speeds Vector of Link Capabilities 2.
This does not affect the speed of the link, which should be negotiated
automatically by the hardware; it only adds decoding when showing the
speed to the user.
This patch adds the
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: c2e7554e1b85935d962127efa3c2a76483b0b3b6
commit: 4bdc0d676a643140bdf17dbf7eafedee3d496a3c remove ioremap_nocache and
devm_ioremap_nocache
date: 11 months ago
config: s390-randconfig-r023-20201119
On Tue, Nov 17, 2020 at 5:55 PM Matthew Wilcox wrote:
> On Mon, Oct 26, 2020 at 06:05:18PM +0200, Topi Miettinen wrote:
> > Writing a new value of 3 to /proc/sys/kernel/randomize_va_space
> > enables full randomization of memory mappings created with mmap(NULL,
> > ...). With 2, the base of the
On 11/13/20 2:59 AM, Muchun Song wrote:
> The purpose of introducing HUGETLB_PAGE_FREE_VMEMMAP is to configure
> whether to enable the feature of freeing unused vmemmap associated
> with HugeTLB pages. Now only support x86.
>
> Signed-off-by: Muchun Song
> ---
> arch/x86/mm/init_64.c | 2 +-
>
On Thu, Nov 12, 2020 at 4:13 PM Paul Moore wrote:
>
> On Tue, Nov 10, 2020 at 10:30 PM Lokesh Gidra wrote:
> > On Tue, Nov 10, 2020 at 6:13 PM Paul Moore wrote:
> > > On Tue, Nov 10, 2020 at 1:24 PM Lokesh Gidra
> > > wrote:
> > > > On Mon, Nov 9, 2020 at 7:12 PM Paul Moore wrote:
> > > > >
On Wed, Nov 18, 2020 at 08:12:43PM +, Ashish Kalra wrote:
> diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
> index 3511736fbc74..0f42911cea57 100644
> --- a/arch/x86/kernel/setup.c
> +++ b/arch/x86/kernel/setup.c
> @@ -1166,6 +1166,10 @@ void __init setup_arch(char **cmdline_p)
On Wed, 18 Nov 2020 at 21:27, Song Bao Hua (Barry Song)
wrote:
>
>
>
> > -Original Message-
> > From: Will Deacon [mailto:w...@kernel.org]
> > Sent: Thursday, November 19, 2020 8:15 AM
> > To: Mike Rapoport
> > Cc: Song Bao Hua (Barry Song) ;
> > catalin.mari...@arm.com;
Hi Maxime,
Sorry for the late reply.
On Fri, Nov 13, 2020 at 06:27:35PM +0100, Maxime Ripard wrote:
> Hi Sakari,
>
> On Wed, Nov 11, 2020 at 03:18:57PM +0200, Sakari Ailus wrote:
> > Hi Paul,
> >
> > On Thu, Nov 05, 2020 at 04:35:34PM +0100, Paul Kocialkowski wrote:
> > > Hi Sakari,
> > >
> >
Thanks a lot Bjorn! I confess except for PPC64 Server machines, I
never saw other "domains" or segments. Is it common in x86 to have
that? The early_quirks() are restricted to the first segment, no
matter how many host bridges we have in segment ?
Thanks again!
Fix compilation warning when ZYNQMP_FIRMWARE is not defined.
include/linux/firmware/xlnx-zynqmp.h: In function
'zynqmp_pm_get_eemi_ops':
include/linux/firmware/xlnx-zynqmp.h:363:9: error: implicit
declaration of function 'ERR_PTR'
[-Werror=implicit-function-declaration]
363 | return
On Wed, 18 Nov 2020 11:57:44 +0100 Christian König
wrote:
> Am 06.11.20 um 23:48 schrieb Andrew Morton:
> > On Fri, 6 Nov 2020 12:48:05 +0100 "Christian König"
> > wrote:
> >
> >> Patch "495c10cc1c0c CHROMIUM: dma-buf: restore args..."
> >> adds a workaround for a bug in mmap_region.
> >>
>
On Mon, Nov 16, 2020 at 01:44:44PM -0800, Rishabh Bhatnagar wrote:
> Add trace events to trace bootup/shutdown/recovery of remote
> processors. These events are useful in analyzing the time
> spent in each step in the life cycle and can be used for
> performace analysis. Also these serve as
On Thu, 19 Nov 2020 at 08:15, Daniel Vetter wrote:
>
> On Wed, Nov 18, 2020 at 11:01 PM David Laight wrote:
> >
> > From: Thomas Zimmermann
> > > Sent: 18 November 2020 19:37
> > >
> > > Hi
> > >
> > > Am 18.11.20 um 19:10 schrieb Linus Torvalds:
> > > > On Wed, Nov 18, 2020 at 4:12 AM David
On Wed, Nov 18, 2020 at 7:40 AM Aisheng Dong wrote:
>
> > From: Greg Kroah-Hartman
> > Sent: Wednesday, November 18, 2020 6:46 PM
> >
> > On Wed, Nov 18, 2020 at 10:23:42AM +, Aisheng Dong wrote:
> > > Hi Greg,
> > >
> > > > From: Greg Kroah-Hartman
> > > > Sent: Monday, November 9, 2020
Hi Babu,
On 11/6/2020 12:14 PM, Babu Moger wrote:
When the AMD QoS feature CDP(code and data prioritization) is enabled
or disabled, the CDP bit in MSR _0C81 is written on one of the
cpus in L3 domain(core complex). That is not correct. The CDP bit needs
to be updated all the logical cpus
Hi!
> From: Hannes Reinecke
>
> [ Upstream commit 5faf50e9e9fdc2117c61ff7e20da49cd6a29e0ca ]
>
> alua_bus_detach() might be running concurrently with alua_rtpg_work(), so
> we might trip over h->sdev == NULL and call BUG_ON(). The correct way of
> handling it is to not set h->sdev to NULL in
On Wed, Nov 18, 2020 at 11:01 PM David Laight wrote:
>
> From: Thomas Zimmermann
> > Sent: 18 November 2020 19:37
> >
> > Hi
> >
> > Am 18.11.20 um 19:10 schrieb Linus Torvalds:
> > > On Wed, Nov 18, 2020 at 4:12 AM David Laight
> > > wrote:
> > >>
> > >> I've got the 'splat' below during boot.
On Wed, 2020-11-18 at 21:29 +, Anchal Agarwal wrote:
> On Wed, Nov 18, 2020 at 03:17:20AM +, Trond Myklebust wrote:
> > CAUTION: This email originated from outside of the organization. Do
> > not click links or open attachments unless you can confirm the
> > sender and know the content is
With Clang's Link Time Optimization (LTO), the compiler can rename
static functions to avoid global naming collisions. As PCI fixup
functions are typically static, renaming can break references
to them in inline assembly. This change adds a global stub to
DECLARE_PCI_FIXUP_SECTION to fix the issue
With LTO, everything is compiled into LLVM bitcode, so we have to link
each module into native code before modpost. Kbuild uses the .lto.o
suffix for these files, which also ends up in module information. This
change strips the unnecessary .lto suffix from the module name.
Suggested-by: Bill
DYNAMIC_FTRACE_WITH_REGS uses -fpatchable-function-entry, which makes
running recordmcount unnecessary as there are no mcount calls in object
files, and __mcount_loc doesn't need to be generated.
While there's normally no harm in running recordmcount even when it's
not strictly needed, this won't
Allow CONFIG_LTO_CLANG and CONFIG_THINLTO to be enabled.
Signed-off-by: Sami Tolvanen
Reviewed-by: Kees Cook
---
arch/arm64/Kconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index c7f07978f5b6..56bd83a764f4 100644
--- a/arch/arm64/Kconfig
+++
We use objcopy to manipulate ELF binaries for the nVHE code,
which fails with LTO as the compiler produces LLVM bitcode
instead. Disable LTO for this code to allow objcopy to be used.
Signed-off-by: Sami Tolvanen
Reviewed-by: Kees Cook
---
arch/arm64/kvm/hyp/nvhe/Makefile | 4 ++--
1 file
With CONFIG_LTO_CLANG, we produce LLVM bitcode instead of ELF object
files. Since LTO is not really needed here and the Makefile assumes we
produce an object file, disable LTO for libstub.
Signed-off-by: Sami Tolvanen
Reviewed-by: Kees Cook
---
drivers/firmware/efi/libstub/Makefile | 2 ++
1
Disable LTO for rodata.o to allow objcopy to be used to
manipulate sections.
Signed-off-by: Sami Tolvanen
Acked-by: Kees Cook
---
drivers/misc/lkdtm/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/misc/lkdtm/Makefile b/drivers/misc/lkdtm/Makefile
index
Disable LTO for the vDSO by filtering out CC_FLAGS_LTO, as there's no
point in using link-time optimization for the small about of C code.
Signed-off-by: Sami Tolvanen
Reviewed-by: Kees Cook
---
arch/arm64/kernel/vdso/Makefile | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
With LTO, the compiler can rename static functions to avoid global
naming collisions. As initcall functions are typically static,
renaming can break references to them in inline assembly. This
change adds a global stub with a stable name for each initcall to
fix the issue when PREL32 relocations
With CONFIG_LTO_CLANG, clang generates LLVM IR instead of ELF object
files. As empty.o is used for probing target properties, disable LTO
for it to produce an object file instead.
Signed-off-by: Sami Tolvanen
Reviewed-by: Kees Cook
---
scripts/mod/Makefile | 1 +
1 file changed, 1 insertion(+)
With LTO, the compiler doesn't necessarily obey the link order for
initcalls, and initcall variables need globally unique names to avoid
collisions at link time.
This change exports __KBUILD_MODNAME and adds the initcall_id() macro,
which uses it together with __COUNTER__ and __LINE__ to help
LLD always splits sections with LTO, which increases module sizes. This
change adds linker script rules to merge the split sections in the final
module.
Suggested-by: Nick Desaulniers
Signed-off-by: Sami Tolvanen
Reviewed-by: Kees Cook
---
scripts/module.lds.S | 24
1
With LTO, llvm-nm prints out symbols for each archive member
separately, which results in a lot of duplicate dependencies in the
.mod file when CONFIG_TRIM_UNUSED_SYMS is enabled. When a module
consists of several compilation units, the output can exceed the
default xargs command size limit and
This change limits function inlining across translation unit boundaries
in order to reduce the binary size with LTO. The -import-instr-limit
flag defines a size limit, as the number of LLVM IR instructions, for
importing functions from other TUs, defaulting to 100.
Based on testing with arm64
With CONFIG_MODVERSIONS, version information is linked into each
compilation unit that exports symbols. With LTO, we cannot use this
method as all C code is compiled into LLVM bitcode instead. This
change collects symbol versions into .symversions files and merges
them in link-vmlinux.sh where
This change adds build system support for Clang's Link Time
Optimization (LTO). With -flto, instead of ELF object files, Clang
produces LLVM bitcode, which is compiled into native code at link
time, allowing the final binary to be optimized globally. For more
details, see:
Move function tracer options to Kconfig to make it easier to add
new methods for generating __mcount_loc, and to make the options
available also when building kernel modules.
Note that FTRACE_MCOUNT_USE_* options are updated on rebuild and
therefore, work even if the .config was generated in a
This patch series adds support for building the kernel with Clang's
Link Time Optimization (LTO). In addition to performance, the primary
motivation for LTO is to allow Clang's Control-Flow Integrity (CFI) to
be used in the kernel. Google has shipped millions of Pixel devices
running three major
HI!
> From: Dan Carpenter
>
> [ Upstream commit a6921dd524fe31d1f460c161d3526a407533b6db ]
>
> These values come from skb->data so Smatch considers them untrusted. I
> believe Smatch is correct but I don't have a way to test this.
>
> The usb_if->dev[] array has 2 elements but the index is
Hi Greg,
> -Original Message-
> From: Greg KH
> Sent: Wednesday, November 18, 2020 3:55 AM
> To: Patel, Utkarsh H
> Cc: linux-kernel@vger.kernel.org; linux-...@vger.kernel.org;
> heikki.kroge...@linux.intel.com; pmal...@chromium.org;
> enric.balle...@collabora.com; Mani, Rajmohan ;
>
From: Thomas Zimmermann
> Sent: 18 November 2020 19:37
>
> Hi
>
> Am 18.11.20 um 19:10 schrieb Linus Torvalds:
> > On Wed, Nov 18, 2020 at 4:12 AM David Laight
> > wrote:
> >>
> >> I've got the 'splat' below during boot.
> >> This is an 8-core C2758 Atom cpu using the on-board/cpu graphics.
>
On Wed, Nov 18, 2020 at 5:02 PM Bjorn Helgaas wrote:
>
> On Fri, Nov 06, 2020 at 10:39:16AM +0100, Daniel Vetter wrote:
> > On Thu, Nov 5, 2020 at 3:17 PM Bjorn Helgaas wrote:
> > > On Thu, Nov 05, 2020 at 11:46:06AM +0200, Joonas Lahtinen wrote:
> > > > Quoting Bjorn Helgaas (2020-11-04
Hi All,
On 11/10/20 12:36 PM, Hans de Goede wrote:
> Hi All,
>
> Not sure if this is a XHCI driver problem at all, but I needed to start
> somewhere with reporting this so I went with:
>
> scripts/get_maintainer.pl -f drivers/usb/host/xhci-pci.c
>
> And added a Cc: linux-...@vger.kernel.org as
Hi Greg,
On Fri, Jan 17, 2020 at 12:17:37AM +0100, Greg Kroah-Hartman wrote:
> From: Thomas Bogendoerfer
>
> commit 37640adbefd66491cb8083a438f7bf366ac09bc7 upstream.
>
>
> ---
> arch/mips/pci/pci-xtalk-bridge.c |5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> ---
On Wed, Nov 18, 2020 at 03:17:20AM +, Trond Myklebust wrote:
> CAUTION: This email originated from outside of the organization. Do not click
> links or open attachments unless you can confirm the sender and know the
> content is safe.
>
>
>
> On Wed, 2020-11-18 at 00:24 +, Anchal
From: Arnaud Pouliquen
Rename the internal function as it is internal, and as
the name will be used in rpmsg_core.
Signed-off-by: Arnaud Pouliquen
Signed-off-by: Mathieu Poirier
Reviewed-by: Guennadi Liakhovetski
---
drivers/rpmsg/virtio_rpmsg_bus.c | 6 +++---
1 file changed, 3
Hi!
> From: Gene Chen
>
> Add LED_COLOR_ID_MOONLIGHT definitions
Why is moonlight a color? Camera flashes are usually white, no?
At least it needs a comment...
Best regards,
Pavel
From: Arnaud Pouliquen
Make the RPMSG name service announcement a stand alone driver so that it
can be reused by other subsystems. It is also the first step in making the
functionatlity transport independent, i.e that is not tied to virtIO.
Co-developed-by: Mathieu Poirier
Signed-off-by:
From: Arnaud Pouliquen
Implement the create and release of the RPMsg channel
for the RPMsg virtio bus.
Signed-off-by: Arnaud Pouliquen
Signed-off-by: Mathieu Poirier
Reviewed-by: Guennadi Liakhovetski
---
drivers/rpmsg/virtio_rpmsg_bus.c | 22 ++
1 file changed, 22
From: Arnaud Pouliquen
Add the channel creation API as a first step to be able to define the
name service announcement as a rpmsg driver independent from the RPMsg
virtio bus.
Signed-off-by: Arnaud Pouliquen
Signed-off-by: Mathieu Poirier
Reviewed-by: Guennadi Liakhovetski
---
Make function rpmsg_register_device() and rpmsg_unregister_device()
functions public so that they can be used by other clients. While
doing so get rid of two obsolete function, i.e register_rpmsg_device()
and unregister_rpmsg_device(), to prevent confusion.
Signed-off-by: Mathieu Poirier
Use rpmsg byte conversion functions in order for the RPMSG
headers and generic functions to be used by external entities.
Signed-off-by: Mathieu Poirier
Reviewed-by: Arnaud Pouliquen
---
drivers/rpmsg/virtio_rpmsg_bus.c | 53 +---
1 file changed, 28 insertions(+),
Move structure rpmsg_ns_msg to its own header file so that
it can be used by other entities.
Signed-off-by: Mathieu Poirier
Reviewed-by: Arnaud Pouliquen
---
drivers/rpmsg/virtio_rpmsg_bus.c | 32 +---
include/linux/rpmsg/ns.h | 42
Introduce __rpmsg{16|32|64} types along with byte order conversion
functions based on an rpmsg_device operation as a foundation to
make RPMSG modular and transport agnostic.
Suggested-by: Guennadi Liakhovetski
Signed-off-by: Mathieu Poirier
Reviewed-by: Arnaud Pouliquen
---
This revision addresses comments received from the previous revision,
i.e V5. Please see details below.
It starts by making the RPMSG protocol transport agnostic by
moving the headers it uses to generic types and using those in the
current implementation. From there it re-uses the work that
On 11/17/2020 1:38 PM, Ahmad Fatoum wrote:
> It's arguable most people interested in configuring a PPS signal
> want it as external output, not as kernel input. PTP_CLK_REQ_PPS
> is for input though. Add documentation to nudge readers into
> the correct direction.
Agreed. I think at least one
On Wed, Nov 18, 2020 at 03:40:19AM -0800, Bernard Zhao wrote:
> Fix check_patch.pl warning:
> ERROR: do not use assignment in if condition
> + if ((HALCYON_HEADER2 == (cmd = *buf)) &&
>
> ERROR: do not use assignment in if condition
> + if
On 11/18/20 12:59 PM, Michal Kubecek wrote:
> On Wed, Nov 18, 2020 at 03:18:06PM +, Christoph Hellwig wrote:
>> On Wed, Nov 18, 2020 at 10:19:17AM +0100, Michal Kubecek wrote:
>>> While eventfd ->read() callback was replaced by ->read_iter() recently,
>>> it still provides ->write() for
On Wed, 18 Nov 2020 18:47:41 +0800, Gene Chen wrote:
> From: Gene Chen
>
> Add bindings document for LED support on MT6360 PMIC
>
> Signed-off-by: Gene Chen
> ---
> .../devicetree/bindings/leds/leds-mt6360.yaml | 164
> +
> 1 file changed, 164 insertions(+)
> create
On Wed, 18 Nov 2020, Mike Snitzer wrote:
> On Wed, Nov 18 2020 at 10:49am -0500,
> Mike Snitzer wrote:
>
> > I don't think my suggestion will help.. given it'd still leave
> > persistent_memory_claim() without a return statement.
> >
> > Think it worthwhile to just add a dummy 'return 0;'
On Wed, 18 Nov 2020 16:21:16 +0800, Chunfeng Yun wrote:
> Convert usb-device.txt to YAML schema usb-device.yaml
>
> Signed-off-by: Chunfeng Yun
> ---
> v3:
> 1. remove $nodenmae and items key word for compatilbe;
> 2. add additionalProperties;
>
> The followings are suggested by Rob:
>
On Wed, 18 Nov 2020 00:06:12 -0800, Wendy Liang wrote:
> Xilinx AI engine array can be partitioned statically for different
> applications. In the device tree, there will be device node for the AI
> engine device, and device nodes for the statically configured AI engine
> partitions. Each of the
On Wed, 11 Nov 2020 at 13:44, Aleksandr Nogikh wrote:
>
> From: Aleksandr Nogikh
>
> Fault injection
> capabilities[Documentation/fault-injection/fault-injection.rst]
> facilitate testing of the stability of the Linux kernel by providing
> means to force a number of kernel interfaces to return
On Mon, Nov 16, 2020 at 06:13:56PM +, Sudeep Holla wrote:
> The CLKSCREW attack [0] exposed security vulnerabilities in energy management
> implementations where untrusted software had direct access to clock and
> voltage hardware controls. In this attack, the malicious software was able to
>
On Wed, Nov 18 2020 at 3:47pm -0500,
Stephen Rothwell wrote:
> Hi all,
>
> Commit
>
> a1e4865b4dda ("dm writecache: remove BUG() and fail gracefully instead")
>
> is missing a Signed-off-by from its author.
Thanks, because I went in a different direction on the code changes I
adjusted
On Mon, 16 Nov 2020 18:13:56 +, Sudeep Holla wrote:
> The CLKSCREW attack [0] exposed security vulnerabilities in energy management
> implementations where untrusted software had direct access to clock and
> voltage hardware controls. In this attack, the malicious software was able to
> place
On Mon, Nov 16, 2020 at 11:01:41PM +0530, Kishon Vijay Abraham I wrote:
> Remove "syscon" nodes added for pcieX_ctrl and have the PCIe node
> point to the parent with an offset argument.
This should say breaks compatibility, but that fine because . It
only landed in 5.9 and a new platform I
On Wed, Nov 18, 2020 at 12:58 PM Thomas Gleixner wrote:
>
> Provide CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP which forces the temporary
> mapping even for lowmem pages. This needs to be a seperate config switch
> because this only works on architectures which do not have cache aliasing
> problems.
Very
On Wed, 18 Nov 2020 11:46:54 -0800 Jakub Kicinski wrote:
> > 1. The kernel is under memory pressure and allocation of
> > PAGE_FRAG_CACHE_MAX_ORDER in __page_frag_cache_refill() will fail. Instead,
> > the pfmemalloc page is allocated for page_frag_cache->va.
> >
> > 2: All skb->data from
On Mon, Nov 16, 2020 at 11:01:39PM +0530, Kishon Vijay Abraham I wrote:
> Fix binding documentation of "ti,syscon-pcie-ctrl" to take phandle with
> argument. The argument is the register offset within "syscon" used to
> configure PCIe controller.
>
> Link: Link:
>
On Wed, Nov 18, 2020 at 04:26:52PM +0100, Alexandre Belloni wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
>
> Hello,
>
> On 18/11/2020 16:03:36+0100, Ludovic Desroches wrote:
> > At first glance, there is no trivial way to register the pin
> -Original Message-
> From: Dexuan Cui
> Sent: Tuesday, November 17, 2020 7:03 PM
> To: KY Srinivasan ; Haiyang Zhang
> ; Stephen Hemminger
> ; wei@kernel.org;
> b.zolnier...@samsung.com; linux-hyp...@vger.kernel.org; dri-
> de...@lists.freedesktop.org;
On 11/18/2020 3:10 AM, Georgi Djakov wrote:
The following errors are noticed during boot on a QCS404 board:
[2.926647] qcom_icc_rpm_smd_send mas 6 error -6
[2.934573] qcom_icc_rpm_smd_send mas 8 error -6
These errors show when we try to configure the GPU and display nodes.
Since these
On Tue, Nov 17, 2020 at 09:04:07AM -0300, Guilherme Piccoli wrote:
> Also, taking here the opportunity to clarify my understanding about
> the limitations of that approach: Bjorn, in our reproducer machine we
> had 3 parents in the PCI tree (as per lspci -t), :00, :ff and
> :80 - are
On 11/18/2020 8:22 AM, Christian Eggers wrote:
> Remove driver internal defines for this.
>
> Signed-off-by: Christian Eggers
> Cc: Richard Cochran
> Cc: Kurt Kanzenbach
> ---
> drivers/ptp/ptp_ines.c | 19 +++
> 1 file changed, 7 insertions(+), 12 deletions(-)
>
> diff
Some usb type-c dongle use irq_hpd request to perform device connection
and disconnection. This patch add handling of both connection and
disconnection are based on the state of hpd_state and sink_count.
Changes in V2:
-- add dp_display_handle_port_ststus_changed()
-- fix kernel test robot
On Wed, 18 Nov 2020 08:50:09 -0600, Nishanth Menon wrote:
> At the start of driver initialization, we do not know what bias
> setting the bootloader has configured the system for and we only know
> for certain the very first time we do a transition.
>
> However, since the initial value of the
On Fri, 6 Nov 2020 16:53:36 +0800, xiakaixu1...@gmail.com wrote:
> The '>=' expression itself is bool, no need to convert it to bool.
> Fix the following coccicheck warning:
>
> ./sound/soc/codecs/wcd9335.c:3982:25-30: WARNING: conversion to bool not
> needed here
Applied to
On Wed, 11 Nov 2020 12:54:34 -0800, Guenter Roeck wrote:
> In kabylake_set_bias_level(), enabling mclk may fail if the clock has
> already been enabled by the firmware. Attempts to disable that clock
> later will fail with a warning backtrace.
>
> mclk already disabled
> WARNING: CPU: 2 PID: 108
On Wed, 11 Nov 2020 16:05:20 +0800, Jiaxin Yu wrote:
> This reverts commit 1afc60e00de3abbb6c559da409c5c1bb8c1d98ec.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: mt8192: revert "add audio afe document"
commit:
On Mon, 16 Nov 2020 20:29:00 +0800, Zou Wei wrote:
> ./sound/soc/samsung/midas_wm1811.c:534:3-8: No need to set .owner here. The
> core will do it.
>
> Remove .owner field if calls are used which set it automatically
>
> Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
Applied
On Fri, 6 Nov 2020 09:59:05 -0500, Kyle Russell wrote:
> The transmit phase register value is never cleared during hw params.
> So once hw params sets this bit to handle a two channel format, it
> remains configured for dual-phase, which is not desirable for mono
> playback.
Applied to
Hi,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on char-misc/char-misc-testing]
[also build test WARNING on kselftest/next linus/master hnaz-linux-mm/master
v5.10-rc4 next-20201118]
[If your patch is applied to the wrong git tree, kindly drop us a note
This is the outstanding set of patches for the preemptible kmap_*()
implementation. The previous version is here:
https://lore.kernel.org/r/20201103092712.714480...@linutronix.de
The following changes come with it:
- Better debugging for kmap* by enforcing the temporary mappings even for
From: Thomas Gleixner
Replace kmap_atomic_pfn() with kmap_local_pfn() which is preemptible and
can take page faults.
Remove the indirection of the dump page and the related cruft which is not
longer required.
Signed-off-by: Thomas Gleixner
---
V3: New patch
---
From: Thomas Gleixner
Similar to kmap local provide a iomap local variant which only disables
migration, but neither disables pagefaults nor preemption.
Signed-off-by: Thomas Gleixner
---
V3: Restrict migrate disable to the 32bit mapping case and update documentation.
V2: Split out from the
kmap_local() and related interfaces are NOOPs on 64bit and only create
temporary fixmaps for highmem pages on 32bit. That means the test coverage
for this code is pretty small.
CONFIG_KMAP_LOCAL can be enabled independent from CONFIG_HIGHMEM, which
allows to provide support for enforced
From: Thomas Gleixner
Now that the kmap atomic index is stored in task struct provide a
preemptible variant. On context switch the maps of an outgoing task are
removed and the map of the incoming task are restored. That's obviously
slow, but highmem is slow anyway.
The kmap_local.*() functions
From: Thomas Gleixner
Instead of storing the map per CPU provide and use per task storage. That
prepares for local kmaps which are preemptible.
The context switch code is preparatory and not yet in use because
kmap_atomic() runs with preemption disabled. Will be made usable in the
next step.
301 - 400 of 1234 matches
Mail list logo