From: Amey Narkhede
Stack allocated buffers cannot be used for DMA
on all architectures so allocate hci_packet buffer
using kzalloc().
Signed-off-by: Amey Narkhede
---
drivers/staging/gdm724x/gdm_usb.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git
Applied. Thanks!
Alex
On Mon, Feb 8, 2021 at 5:17 AM Jiapeng Chong
wrote:
>
> Fix the following coccicheck warning:
>
> ./drivers/gpu/drm/radeon/rs690.c:190:6-35: WARNING: Comparison to bool.
>
> Reported-by: Abaci Robot
> Signed-off-by: Jiapeng Chong
> ---
> drivers/gpu/drm/radeon/rs690.c
On Tue, Feb 9, 2021 at 6:46 PM Luca Risolia
wrote:
>
> On 09/02/21 17:50, Richard Weinberger wrote:
> > Well, I think having a generic mmap() for CUSE is hard to achieve.
>
> Hard or not it did work for what I can tell you. I was not the original
> author but I certainly contributed with testing
On Tue, Feb 09, 2021 at 02:01:37PM +0100, Greg Kroah-Hartman wrote:
> On Tue, Feb 09, 2021 at 01:52:52PM +0100, Pavel Machek wrote:
> > Hi!
> >
> > > From: Arnd Bergmann
> > >
> > > commit 6e7b64b9dd6d96537d816ea07ec26b7dedd397b9 upstream.
> > >
> > > kernel/elfcore.c only contains weak
On Wed, 27 Jan 2021 12:49:01 +0100, Martin Kepplinger wrote:
> Add optional interconnect properties for the dram path requests.
>
> Signed-off-by: Martin Kepplinger
> ---
> Documentation/devicetree/bindings/display/fsl,lcdif.yaml | 8
> 1 file changed, 8 insertions(+)
>
Reviewed-by:
On Tue, 9 Feb 2021 16:11:23 +0100 David Sterba wrote:
> On Fri, Feb 05, 2021 at 03:23:00PM -0800, ira.we...@intel.com wrote:
> > From: Ira Weiny
> >
> > There are many places where kmap//kunmap patterns occur. We lift
> > these various patterns to core common functions and use them in the
On Thu, Jan 28, 2021 at 11:08:26AM +0800, Xin Ji wrote:
> Add 'bus-type' and 'data-lanes' define for port0, add HDCP support
> flag and DP tx lane0 and lane1 swing register array define.
>
> Signed-off-by: Xin Ji
> ---
> .../bindings/display/bridge/analogix,anx7625.yaml | 54
>
On 2/9/2021 12:14 PM, Greg KH wrote:
On Tue, Feb 09, 2021 at 12:05:05PM -0700, Dave Jiang wrote:
When the auxiliary device code is built into the kernel, it can be executed
before the auxiliary bus is registered. This causes bus->p to be not
allocated and triggers a NULL pointer dereference
On Thu, Jan 28, 2021 at 12:11:05PM +0530, Prasanna Vengateshan wrote:
> Documentation in .yaml format and updates to the MAINTAINERS
> Also 'make dt_binding_check' is passed
>
> Signed-off-by: Prasanna Vengateshan
> ---
> .../bindings/net/dsa/microchip,lan937x.yaml | 115 ++
>
On Mon, 8 Feb 2021 at 20:35, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.9.257 release.
> There are 43 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.
>
>
Hi Jassi,
The following is a minor revision of the series [1] that extends the OMAP
Mailbox driver for the IP on TI K3 AM64x SoCs.
Only change is in patch 1 to drop the example in the dt-bindings patch.
regards
Suman
[1]
Hi Gustavo,
[...]
> > That's true, there are a lot of drivers that don't verify that pointer.
> > What do you suggest?
> > 1) To remove the verification so that is aligned with the other drivers
> > 2) Leave it as is. Or even to add this verification to the other drivers?
> >
> > Either way, I
The AM64x SoC contains a Mailbox IP instance with multiple clusters
in the MAIN domain, and is a variant of the IP on current AM65x and
J721E SoCs. The AM64x SoC has only 8 clusters with no interrupts
routed to the A53 core on the first 2 clusters. The interrupt outputs
from the IP do not go
Update the existing OMAP Mailbox binding to include the info for
AM64x SoCs. There are some minor IP integration differences between
the AM64x SoCs and the previous AM65x and J721E SoC families.
Signed-off-by: Suman Anna
---
v2: Remove AM64x example as per Rob's comments
v1:
Enable dwc3 usb for A95X Z2.
Signed-off-by: Johan Jonker
---
Changed V2:
remove node wrapper
---
arch/arm64/boot/dts/rockchip/rk3318-a95x-z2.dts | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/rockchip/rk3318-a95x-z2.dts
For rk3399 dwc3 usb the wrapper node for only clocks makes no sense,
so restyle the rk3399 usbdrd3_1 node before more new SoC types are
added with the same IP.
Signed-off-by: Johan Jonker
---
Changed V3:
remove aclk_usb3_rksoc_axi_perf
remove aclk_usb3
---
Add description for "rockchip,rk3328-dwc3".
Signed-off-by: Johan Jonker
---
Changed V5:
add select
---
Documentation/devicetree/bindings/usb/rockchip,dwc3.yaml | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/usb/rockchip,dwc3.yaml
From: Cameron Nemo
RK3328 SoCs have one USB 3.0 OTG controller which uses DWC_USB3
core's general architecture. It can act as static xHCI host
controller, static device controller, USB 3.0/2.0 OTG basing
on ID of USB3.0 PHY.
Signed-off-by: William Wu
Signed-off-by: Heiko Stuebner
For rk3399 dwc3 usb the wrapper node for only clocks makes no sense,
so restyle the rk3399 usbdrd3_0 node before more new SoC types are
added with the same IP.
Signed-off-by: Johan Jonker
---
Changed V3:
remove aclk_usb3_rksoc_axi_perf
remove aclk_usb3
---
On Wed, 27 Jan 2021 19:25:05 +0100, Konrad Dybcio wrote:
> MDM9607 TSENS IP is very similar to the one of MSM8916, with
> minor adjustments to various tuning values.
>
> Signed-off-by: Konrad Dybcio
> ---
> Changes since v1:
> - Move the defines so as not to cut into the middle of 8974 regs
>
>
On Wed, Jan 27, 2021 at 01:55:59PM -0600, Suman Anna wrote:
> Update the existing OMAP Mailbox binding to include the info for
> AM64x SoCs. There are some minor IP integration differences between
> the AM64x SoCs and the previous AM65x and J721E SoC families.
>
> Signed-off-by: Suman Anna
> ---
On Tue, Feb 09, 2021 at 07:17:59PM +0100, David Hildenbrand wrote:
> On 09.02.21 18:50, Minchan Kim wrote:
> > __alloc_contig_migrate_range already has lru_add_drain_all call
> > via migrate_prep. It's necessary to move LRU taget pages into
> > LRU list to be able to isolated. However,
On Wed, Jan 27, 2021 at 02:28:40PM +0100, Geert Uytterhoeven wrote:
> Convert the Renesas R-Mobile System Controller (SYSC) Device Tree
> binding documentation to json-schema.
>
> Document missing properties.
> Drop consumer example, as it does not belong here.
>
> Signed-off-by: Geert
On Wed, Feb 10, 2021 at 12:39:15AM +0530, karthek wrote:
> On Tue, Feb 09, 2021 at 07:59:02PM +0100, Greg Kroah-Hartman wrote:
> > On Wed, Feb 10, 2021 at 12:23:17AM +0530, karthik alapati wrote:
> > > fix checkpatch.pl warning for "block comments should align the * on each
> > > line"
> > >
> >
On Wed, 27 Jan 2021 16:51:25 +0800, Liu Ying wrote:
> This patch adds bindings for i.MX8qm/qxp LVDS display bridge(LDB).
>
> Signed-off-by: Liu Ying
> ---
> v2->v3:
> * Drop 'fsl,syscon' property. (Rob)
> * Mention the CSR module controls LDB.
>
> v1->v2:
> * Use graph schema. (Laurent)
> *
On Wed, 27 Jan 2021 13:45:43 +0200, Claudiu Beznea wrote:
> Document slew-rate DT binding for SAMA7G5.
>
> Signed-off-by: Claudiu Beznea
> Acked-by: Ludovic Desroches
> ---
> .../devicetree/bindings/pinctrl/atmel,at91-pio4-pinctrl.txt | 8
> +---
> 1 file changed, 5 insertions(+), 3
On Wed, Feb 10, 2021 at 12:23:17AM +0530, karthik alapati wrote:
> fix checkpatch.pl warning for "block comments should align the * on each line"
>
> Signed-off-by: karthik alapati
> ---
> .../staging/rtl8723bs/hal/rtl8723b_phycfg.c | 204 +-
> 1 file changed, 102
On Tue, Feb 09, 2021 at 08:27:24PM +0200, Vladimir Oltean wrote:
> But there's an interesting side effect of allowing
> br_switchdev_set_port_flag to run concurrently (notifier call chains use
> a rw_semaphore and only take the read side). Basically now drivers that
> cache the brport flags in
So I'm looking at this early, because I have more time now than I will
have during the merge window, and honestly, your pull requests have
been problematic in the past.
The PG_fscache bit waiting functions are completely crazy. The comment
about "this will wake up others" is actively wrong, and
fdt_appendprop_addrrange() function adds a property, with the given name,
to the device tree at the given node offset, and also sets the address
and size of the property. This function should be used to add
"linux,ima-kexec-buffer" property to the device tree and set the address
and size of the
"atmel,sama5d2-pmc"
> > arch/arm/boot/dts/sama5d2.dtsi: compatible =
> > "atmel,sama5d2-pmc", "syscon";
> > arch/arm/mach-at91/pm.c:{ .compatible = "atmel,sama5d2-pmc",
> > .data = _infos[1] },
> > drivers/cl
On Fri, Feb 05, 2021 at 09:52:56AM -0800, Saravana Kannan wrote:
> On Fri, Feb 5, 2021 at 6:14 AM Greg Kroah-Hartman
> wrote:
> >
> > From: "Rafael J. Wysocki"
> >
> > commit 3d1cf435e201d1fd63e4346b141881aed086effd upstream
> >
> > If the device passed as the target (second argument) to
> >
When the auxiliary device code is built into the kernel, it can be executed
before the auxiliary bus is registered. This causes bus->p to be not
allocated and triggers a NULL pointer dereference when the auxiliary bus
device gets added with bus_add_device(). Change the init of auxiliary bus
to
On Wed, 27 Jan 2021 14:25:36 +0530, Anshuman Khandual wrote:
> From: Suzuki K Poulose
>
> Document the device tree bindings for Trace Buffer Extension (TRBE).
>
> Cc: Anshuman Khandual
> Cc: Mathieu Poirier
> Cc: Rob Herring
> Cc: devicet...@vger.kernel.org
> Signed-off-by: Suzuki K Poulose
On Tue, 9 Feb 2021 17:02:56 + Catalin Marinas
wrote:
> On Tue, Feb 09, 2021 at 04:32:30PM +0100, Andrey Konovalov wrote:
> > diff --git a/arch/arm64/kernel/mte.c b/arch/arm64/kernel/mte.c
> > index a66c2806fc4d..788ef0c3a25e 100644
> > --- a/arch/arm64/kernel/mte.c
> > +++
From: Linus Lüssing
When trying to set the noise floor via debugfs, a "data bus error"
crash like the following can happen:
[ 88.433133] Data bus error, epc == 80221c28, ra == 83314e60
[ 88.438895] Oops[#1]:
[ 88.441246] CPU: 0 PID: 7263 Comm: sh Not tainted 4.14.195 #0
[ 88.447174]
On 2021-02-08 12:24 p.m., Mimi Zohar wrote:
Hi Tushar,
On Fri, 2021-01-29 at 16:45 -0800, Tushar Sugandhi wrote:
diff --git a/security/integrity/ima/ima_queue.c
b/security/integrity/ima/ima_queue.c
index c096ef8945c7..fbf359495fa8 100644
--- a/security/integrity/ima/ima_queue.c
+++
On Tue, 2021-02-09 at 10:23 -0800, Tushar Sugandhi wrote:
> > On Mon, 2021-02-08 at 15:22 -0500, Mimi Zohar wrote:
> >> On Fri, 2021-01-29 at 16:45 -0800, Tushar Sugandhi wrote:
> >>> IMA does not measure duplicate buffer data since TPM extend is a very
> >>> expensive operation. However, in some
On Tue, Feb 09, 2021 at 03:28:16PM +, Gustavo Pimentel wrote:
> On Mon, Feb 8, 2021 at 22:53:54, Krzysztof Wilczyński
> wrote:
> > [...]
> > > Thanks for your review. I will wait for a couple of days, before sending
> > > a new version of this patch series based on your feedback.
> >
> >
fix checkpatch.pl warning for "block comments should align the * on each line"
Signed-off-by: karthik alapati
---
.../staging/rtl8723bs/hal/rtl8723b_phycfg.c | 204 +-
1 file changed, 102 insertions(+), 102 deletions(-)
diff --git
On 2021-02-08 12:45 p.m., Mimi Zohar wrote:
Hi Tushar,
On Fri, 2021-01-29 at 16:45 -0800, Tushar Sugandhi wrote:
IMA needs to support duplicate measurements of integrity
critical data to accurately determine the current state of that data
on the system. Further, since measurement of
On Tue, Feb 09, 2021 at 05:19:29PM +0200, Vladimir Oltean wrote:
> So switchdev drivers operating in standalone mode should disable address
> learning. As a matter of practicality, we can reduce code duplication in
> drivers by having the bridge notify through switchdev of the initial and
> final
On Mon, Feb 08, 2021 at 04:00:32PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.4.97 release.
> There are 65 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
On Sun, Feb 07, 2021 at 10:07:31AM +0100, Wilken Gottwalt wrote:
> On Wed, 23 Dec 2020 15:49:19 -0700
> Rob Herring wrote:
>
> > On Wed, Dec 23, 2020 at 4:34 AM Wilken Gottwalt
> > wrote:
> > >
> > > Adds documentation on how to use the sun6i_hwspinlock driver for sun6i
> > > compatible SoCs.
>
On Tue, Feb 9, 2021 at 10:26 AM Andy Lutomirski wrote:
> >
> > Anything else would just be insanely complicated, I feel.
>
> The other model is “don’t do that then.”
Hmm. I guess all the code that does int3 patching could just be taught
to always go to the next instruction instead.
I don't
On Tue, Feb 09, 2021 at 11:26:17PM +0530, karthek wrote:
> On Tue, Feb 09, 2021 at 06:23:39PM +0100, Greg Kroah-Hartman wrote:
> > On Tue, Feb 09, 2021 at 09:50:50PM +0530, karthek wrote:
> > > On Sun, Feb 07, 2021 at 04:26:40PM +0100, Greg Kroah-Hartman wrote:
> > > > On Sun, Feb 07, 2021 at
On Tue, Feb 09, 2021 at 06:23:39PM +0100, Greg Kroah-Hartman wrote:
> On Tue, Feb 09, 2021 at 09:50:50PM +0530, karthek wrote:
> > On Sun, Feb 07, 2021 at 04:26:40PM +0100, Greg Kroah-Hartman wrote:
> > > On Sun, Feb 07, 2021 at 08:54:49PM +0530, karthek wrote:
> > > > On Sun, Feb 07, 2021 at
It turns out that reasoning for lowering max. supported frequency is
wrong. Scrambling works just fine. Several now fixed bugs prevented
proper functioning, even with rates lower than 340 MHz. Issues were just
more pronounced with higher frequencies.
Fix that by allowing max. supported frequency
BPF programs explicitly initialise global variables to 0 to make sure
clang (v10 or older) do not put the variables in the common section.
Skip "initialise globals to 0" check for BPF programs to elimiate error
messages like:
ERROR: do not initialise globals to 0
#19: FILE:
delete_fdt_mem_rsv() defined in "arch/powerpc/kexec/file_load.c"
has been renamed to fdt_find_and_del_mem_rsv(), and moved to
"drivers/of/kexec.c".
Remove delete_fdt_mem_rsv() in "arch/powerpc/kexec/file_load.c".
Co-developed-by: Prakhar Srivastava
Signed-off-by: Prakhar Srivastava
> On Feb 9, 2021, at 10:09 AM, Linus Torvalds
> wrote:
>
> On Tue, Feb 9, 2021 at 8:55 AM Andy Lutomirski wrote:
>>
>> Or we hack up #CP to handle this case. I don’t quite know how I feel about
>> this.
>
> I think that's the sane model - if we've replaced the instruction with
> 'int3',
On Mon, Feb 08, 2021 at 03:59:47PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.15 release.
> There are 120 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
On Tue, Feb 09, 2021 at 05:19:27PM +0200, Vladimir Oltean wrote:
> From: Vladimir Oltean
>
> The br_switchdev_set_port_flag function uses the atomic notifier call
> chain because br_setport runs in an atomic section (under br->lock).
> This is because port flag changes need to be synchronized
On 2/9/21 8:03 AM, Peter Zijlstra wrote:
> On Tue, Feb 09, 2021 at 01:24:30PM +, Mark Rutland wrote:
>> On Tue, Feb 09, 2021 at 09:34:10AM +0100, Peter Zijlstra wrote:
>>>
>>> Subject: lockdep: Noinstr annotate warn_bogus_irq_restore()
>>> From: Peter Zijlstra
>>> Date: Tue Feb 9 09:30:03 CET
On Tue, 9 Feb 2021 16:05:24 +0530 Hariprasad Kelam wrote:
> v4:
> - Corrected indentation issues
> - Use FEC_OFF if user requests for FEC_AUTO mode
> - Do not clear fec stats in case of user changes
> fec mode
> - dont hide fec stats depending on interface mode
>
Thank you Mimi for reviewing this series.
On 2021-02-08 1:10 p.m., Mimi Zohar wrote:
Hi Tushar,
On Mon, 2021-02-08 at 15:22 -0500, Mimi Zohar wrote:
On Fri, 2021-01-29 at 16:45 -0800, Tushar Sugandhi wrote:
IMA does not measure duplicate buffer data since TPM extend is a very
expensive
Update CONFIG_KEXEC_FILE to select CONFIG_HAVE_IMA_KEXEC, if CONFIG_IMA
is enabled, to indicate that the IMA measurement log information is
present in the device tree for ARM64.
Co-developed-by: Prakhar Srivastava
Signed-off-by: Prakhar Srivastava
Signed-off-by: Lakshmi Ramasubramanian
The fields ima_buffer_addr and ima_buffer_size in "struct kimage_arch"
for powerpc are used to carry forward the IMA measurement list across
kexec system call. These fields are not architecture specific, but are
currently limited to powerpc.
arch_ima_add_kexec_buffer() defined in
The functions defined in "arch/powerpc/kexec/ima.c" handle setting up
and freeing the resources required to carry over the IMA measurement
list from the current kernel to the next kernel across kexec system call.
These functions do not have architecture specific code, but are
currently limited to
On Tue, Feb 09 2021 at 10:22, Josh Poimboeuf wrote:
> On Tue, Feb 09, 2021 at 04:12:33PM +0100, Thomas Gleixner wrote:
>> On Mon, Feb 08 2021 at 14:42, Josh Poimboeuf wrote:
>> > On Thu, Feb 04, 2021 at 09:49:08PM +0100, Thomas Gleixner wrote:
>> >> #ifdef CONFIG_X86_64
>> >> +
>> >> +#ifdef
CONFIG_HAVE_IMA_KEXEC is enabled to indicate that the IMA measurement
log information is present in the device tree. This should be selected
only if CONFIG_IMA is enabled.
Update CONFIG_KEXEC_FILE to select CONFIG_HAVE_IMA_KEXEC, if CONFIG_IMA
is enabled, to indicate that the IMA measurement log
> On Feb 9, 2021, at 9:24 AM, Joe Perches wrote:
>
> On Tue, 2021-02-09 at 09:00 -0800, Song Liu wrote:
>> BPF programs explicitly initialise global variables to 0 to make sure
>> clang (v10 or older) do not put the variables in the common section.
>> Skip "initialise globals to 0" check for
From: Rob Herring
The architecture specific field, elfcorehdr_addr in struct kimage_arch,
that holds the address of the buffer in memory for ELF core header for
powerpc has a different name than the one used for arm64. This makes
it hard to have a common code for setting up the device tree for
On Tue, Feb 09, 2021 at 11:12:34AM -0600, Eddie James wrote:
> Initialize the sequence number at one, rather than zero, in order
> to prevent false matches with the zero-initialized OCC SRAM
> buffer before the OCC is fully initialized.
>
> Signed-off-by: Eddie James
Acked-by: Guenter Roeck
On Tue, Feb 9, 2021 at 8:55 AM Andy Lutomirski wrote:
>
> Or we hack up #CP to handle this case. I don’t quite know how I feel about
> this.
I think that's the sane model - if we've replaced the instruction with
'int3', and we end up getting #CP due to that, just do the #BP
handling.
Anything
On Mon, Feb 08, 2021 at 04:00:26PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.257 release.
> There are 43 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
On Mon, Feb 08, 2021 at 04:00:47PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.175 release.
> There are 38 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
On Tue, Feb 09, 2021 at 11:12:35AM -0600, Eddie James wrote:
> In order to better debug problems starting up the driver, print
> the response status from the OCC in the error logged when the first
> poll command fails.
>
> Signed-off-by: Eddie James
Acked-by: Guenter Roeck
> ---
>
Dear RT folks!
I'm pleased to announce the v5.10.14-rt28 patch set.
Changes since v5.10.14-rt27:
- Lazy preemption fix for 64bit PowerPC. It was broken since
v5.9-rc2-rt1. Reported by John Ogness.
- Two patches for chelsio/cxgb network driver to avoid
tasklet_disable() usage in
On Mon, Feb 08, 2021 at 04:00:22PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.257 release.
> There are 38 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
On Mon, Jan 18, 2021 at 11:53:37AM -0600, Josh Poimboeuf wrote:
> On Thu, Jan 14, 2021 at 02:09:28PM +0300, Andrey Ryabinin wrote:
> >
> >
> > On 1/14/21 1:59 PM, Peter Zijlstra wrote:
> > > On Mon, Jan 04, 2021 at 04:13:17PM +0100, Peter Zijlstra wrote:
> > >> On Tue, Dec 22, 2020 at 11:04:54PM
Fix typo in 'compatible' property name.
Signed-off-by: Mans Rullgard
---
Documentation/devicetree/bindings/usb/usb-device.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/usb/usb-device.yaml
On 2/9/21 4:13 PM, Marco Elver wrote:
> We cannot rely on CONFIG_DEBUG_KERNEL to decide if we're running a
> "debug kernel" where we can safely show potentially sensitive
> information in the kernel log.
>
> Therefore, add the option CONFIG_KFENCE_REPORT_SENSITIVE to decide if we
> should add
From: Rob Herring
Both arm64 and powerpc do essentially the same FDT /chosen setup for
kexec. The differences are either omissions that arm64 should have
or additional properties that will be ignored. The setup code can be
combined and shared by both powerpc and arm64.
The differences
On kexec file load Integrity Measurement Architecture (IMA) subsystem
may verify the IMA signature of the kernel and initramfs, and measure
it. The command line parameters passed to the kernel in the kexec call
may also be measured by IMA. A remote attestation service can verify
a TPM quote
From: Rob Herring
The code for setting up the /chosen node in the device tree
and updating the memory reservation for the next kernel has been
moved to of_kexec_alloc_and_setup_fdt() defined in "drivers/of/kexec.c".
Use the common of_kexec_alloc_and_setup_fdt() to setup the device tree
and
From: Rob Herring
The code for setting up the /chosen node in the device tree
and updating the memory reservation for the next kernel has been
moved to of_kexec_alloc_and_setup_fdt() defined in "drivers/of/kexec.c".
Use the common of_kexec_alloc_and_setup_fdt() to setup the device tree
and
Hi,
On 2/9/21 3:28 PM, Prasanth, KSR wrote:
> From: "Prasanth KSR"
>
> Perform BIOS Management calls on supported Dell machines
> through the Dell WMI System Management interface.
>
> This interface provides IOCTL's to perform bundled
> BIOS Setting transactions.
Why?
Adding new userspace
On Tue, Feb 09, 2021 at 05:19:26PM +0200, Vladimir Oltean wrote:
> From: Vladimir Oltean
>
> When a struct switchdev_attr is notified through switchdev, there is no
> way to report informational messages, unlike for struct switchdev_obj.
>
> Signed-off-by: Vladimir Oltean
Reviewed-by: Ido
On 2/9/21 5:28 PM, Catalin Marinas wrote:
>> I don't think though you can "check" with IRQs disabled so I suspect
>> that TFSR_EL1 has to be saved/restored (which means that there is a
>> black out period where we run kernel code without being able to detect
>> faults but there is no solution to
On Mon, Feb 08, 2021 at 04:00:46PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.221 release.
> There are 30 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
On 09/02/21 09:58, Vincent Guittot wrote:
> On Thu, 28 Jan 2021 at 19:32, Valentin Schneider
>> Giving group_misfit_task a higher group_classify() priority than
>> group_imbalance doesn't seem like the right thing to do. Instead, make
>
> Could you explain why ?
>
Morten had intentionally placed
On Tue, Feb 09, 2021 at 08:24:15PM +0530, ameynarkhed...@gmail.com wrote:
> From: Amey Narkhede
>
> Stack allocated buffers cannot be used for DMA
> on all architectures so allocate usbdev buffer
> using kmalloc().
>
> Signed-off-by: Amey Narkhede
> ---
> drivers/staging/gdm724x/gdm_usb.c | 6
On 09.02.21 18:50, Minchan Kim wrote:
__alloc_contig_migrate_range already has lru_add_drain_all call
via migrate_prep. It's necessary to move LRU taget pages into
LRU list to be able to isolated. However, lru_add_drain_all call
after __alloc_contig_migrate_range is called is pointless.
This
Hi Gustavo,
[...]
> > This "pcim_iomap_table(dev)[n]" pattern is extremely common. There
> > are over 100 calls of pcim_iomap_table(), and
> >
> > $ git grep "pcim_iomap_table(.*)\[.*\]" | wc -l
> >
> > says about 75 of them are of this form, where we dereference the
> > result before
On 2/8/21 11:11 PM, Miaohe Lin wrote:
> All callers know they are operating on a hugetlb head page. So this
> VM_BUG_ON_PAGE can not catch anything useful.
>
> Signed-off-by: Miaohe Lin
> ---
> mm/hugetlb.c | 1 -
> 1 file changed, 1 deletion(-)
Thanks,
Reviewed-by: Mike Kravetz
--
Mike
On Wed, Jan 27, 2021 at 04:51:23PM +0800, Liu Ying wrote:
> This patch adds a drm bridge driver for i.MX8qxp pixel link to display
> pixel interface(PXL2DPI). The PXL2DPI interfaces the pixel link 36-bit
> data output and the DSI controller’s MIPI-DPI 24-bit data input, and
> inputs of LVDS
Hi Dexuan,
On 05/02/2021 19:36, Dexuan Cui wrote:
>> From: Rafael J. Wysocki
>> Sent: Friday, February 5, 2021 5:06 AM
>> To: Dexuan Cui
>> Cc: linux-a...@vger.kernel.org; linux-kernel@vger.kernel.org;
>> linux-hyp...@vger.kernel.org; Michael Kelley
>> Subject: Re: How can a userspace program
On Tue, Feb 9, 2021 at 1:43 AM wangyanan (Y) wrote:
>
>
> On 2021/2/9 4:29, Ben Gardon wrote:
> > On Mon, Feb 8, 2021 at 1:08 AM Yanan Wang wrote:
> >> This test serves as a performance tester and a bug reproducer for
> >> kvm page table code (GPA->HPA mappings), so it gives guidance for
> >>
On Tue, Feb 9, 2021 at 9:46 AM Christian König wrote:
>
>
>
> Am 09.02.21 um 18:33 schrieb Suren Baghdasaryan:
> > On Tue, Feb 9, 2021 at 4:57 AM Christian König
> > wrote:
> >> Am 09.02.21 um 13:11 schrieb Christian König:
> >>> [SNIP]
> >> +void drm_page_pool_add(struct drm_page_pool
On Tue, 26 Jan 2021 10:01:15 +0100, gabriel.fernan...@foss.st.com wrote:
> From: Gabriel Fernandez
>
> Add ID to SCMI0 to exposes reset controller for the MCU HOLD BOOT resource.
>
> Signed-off-by: Arnaud Pouliquen
> Signed-off-by: Gabriel Fernandez
> ---
>
On Tue, 26 Jan 2021 10:01:19 +0100, gabriel.fernan...@foss.st.com wrote:
> From: Gabriel Fernandez
>
> Introduce new compatible string "st,stm32mp1-rcc-secure" for
> stm32mp1 clock driver when the device is configured with RCC
> security support hardened.
>
> Signed-off-by: Etienne Carriere
>
On Tue, 26 Jan 2021 10:32:51 -0600, Suman Anna wrote:
> The current PRUSS Interrupt Controller binding doesn't exactly specify
> the convention for the node name. These interrupt-controllers will always
> have a unit address. Update the binding with the '$nodename' using the
> expected generic
On Tue, Feb 09, 2021 at 06:23:39PM +0100, Greg Kroah-Hartman wrote:
> On Tue, Feb 09, 2021 at 09:50:50PM +0530, karthek wrote:
> > On Sun, Feb 07, 2021 at 04:26:40PM +0100, Greg Kroah-Hartman wrote:
> > > On Sun, Feb 07, 2021 at 08:54:49PM +0530, karthek wrote:
> > > > On Sun, Feb 07, 2021 at
On Mon, Feb 08, 2021 at 10:02:29PM -0500, Peter Xu wrote:
> This is the last missing piece of the COW-during-fork effort when there're
> pinned pages found. One can reference 70e806e4e645 ("mm: Do early cow for
> pinned pages during fork() for ptes", 2020-09-27) for more information, since
> we
On Tue, 26 Jan 2021 10:01:14 +0100, gabriel.fernan...@foss.st.com wrote:
> From: Gabriel Fernandez
>
> stm32mp15 TZ secure firmware provides SCMI reset domains for
> secure resources. This change defines the SCMI reset domain
> identifiers used by SCMI agents and servers.
>
> Stm32mp15 TZ
On Tue, 26 Jan 2021 10:01:13 +0100, gabriel.fernan...@foss.st.com wrote:
> From: Gabriel Fernandez
>
> stm32mp15 TZ secure firmware provides SCMI clocks for oscillators, some
> PLL output and few secure aware interfaces.
> This change defines the SCMI clock identifiers used by SCMI agents
> and
On Tue, Feb 9, 2021 at 4:11 AM Christian König wrote:
>
>
>
> Am 05.02.21 um 21:46 schrieb John Stultz:
> > On Fri, Feb 5, 2021 at 12:47 AM Christian König
> > wrote:
> >> Am 05.02.21 um 09:06 schrieb John Stultz:
> >>> diff --git a/drivers/gpu/drm/page_pool.c b/drivers/gpu/drm/page_pool.c
> >>>
__alloc_contig_migrate_range already has lru_add_drain_all call
via migrate_prep. It's necessary to move LRU taget pages into
LRU list to be able to isolated. However, lru_add_drain_all call
after __alloc_contig_migrate_range is called is pointless.
This patch removes it.
Signed-off-by: Minchan
On Wed, 3 Feb 2021 17:50:12 +0800
Yue Hu wrote:
> From: Yue Hu
>
> Since SCHED_WARN_ON() is provided as a wrapper for WARN_ON_ONCE().
Reviewed-by: Steven Rostedt (VMware)
Peter, care to take this?
Also, looks like we can get rid of the #ifdef CONFIG_SCHED_DEBUG in
set_task_cpu() by
601 - 700 of 1488 matches
Mail list logo
