In order to ease preparation for CONFIG_VMAP_STACK, reorder
a few instruction, especially save r1 into stack frame earlier.
Signed-off-by: Christophe Leroy
---
arch/powerpc/kernel/head_40x.S | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
On Fri, Jan 22, 2021 at 09:55:44AM +, 吳昊澄 Ricky wrote:
> > -Original Message-
> > From: Greg KH
> > Sent: Friday, January 22, 2021 4:28 PM
> > To: 吳昊澄 Ricky
> > Cc: a...@arndb.de; bhelg...@google.com; vaibhavgupt...@gmail.com;
> > linux-kernel@vger.kernel.org; sta...@vger.kernel.org
Hi,
On Fri, Jan 22, 2021 at 03:03:11PM +0800, Mingchuang Qiao wrote:
> On Thu, 2021-01-21 at 16:31 -0600, Bjorn Helgaas wrote:
> > [+cc Alex and Mingchuang et al from
> > https://lore.kernel.org/r/20210112072739.31624-1-mingchuang.q...@mediatek.com]
> >
> > On Tue, Jan 19, 2021 at 04:14:10PM
Hi,
On 1/21/21 11:29 PM, Laurent Pinchart wrote:
> Hi Michal,
>
> I've just realized I forgot to reply to this e-mail, sorry.
>
> On Tue, Dec 08, 2020 at 08:26:41AM +0100, Michal Simek wrote:
>> On 07. 12. 20 23:16, Laurent Pinchart wrote:
>>> On Mon, Dec 07, 2020 at 10:39:25AM +0100, Michal
On Fri, Jan 22, 2021 at 10:30:52AM +0100, Vincent Guittot wrote:
> Hi Mel,
>
> On Tue, 19 Jan 2021 at 13:02, Mel Gorman wrote:
> >
> > On Tue, Jan 19, 2021 at 12:33:04PM +0100, Vincent Guittot wrote:
> > > On Tue, 19 Jan 2021 at 12:22, Mel Gorman
> > > wrote:
> > > >
> > > > Changelog since v2
On 1/22/21 2:48 PM, David Hildenbrand wrote:
>
>> +/*
>> + * Platforms should define arch_get_mappable_range() that provides
>> + * maximum possible addressable physical memory range for which the
>> + * linear mapping could be created. The platform returned address
>> + * range must adhere to
This patch refines the interrupt related code to support new chips.
Signed-off-by: Hsin-Hsiung Wang
Acked-for-MFD-by: Lee Jones
---
changes since v4: no changes
---
drivers/mfd/mt6358-irq.c| 65 +++--
include/linux/mfd/mt6358/core.h | 8 ++--
2 files
Commit 61b8b2a834bf ("dm integrity: introduce the "fix_hmac" argument")
adds some new part to dm-integrity.rst, but this causes make htmldocs warn:
dm-integrity.rst:192: WARNING: Unexpected indentation.
dm-integrity.rst:193: WARNING: Block quote ends without a blank line; \
unexpected
If the name of this function changes, you can easily
forget to modify the code in the corresponding place.
In fact, such errors already exist in spte_write_protect
and spte_clear_dirty.
Signed-off-by: Stephen Zhang
---
arch/x86/kvm/mmu/mmu.c | 16
1 file changed, 8
This adds support for the MediaTek MT6359 PMIC. This is a
multifunction device with the following sub modules:
- Codec
- Interrupt
- Regulator
- RTC
It is interfaced to the host controller using SPI interface
by a proprietary hardware called PMIC wrapper or pwrap.
MT6359 MFD is a child device of
On 1/21/21 5:38 PM, Andrey Konovalov wrote:
>> + if (unlikely(tfsr_el1 & SYS_TFSR_EL1_TF1)) {
>> + /*
>> +* Note: isb() is not required after this direct write
>> +* because there is no indirect read subsequent to it
>> +* (per
Hi Mark and Boyd,
Thanks for your time on this issue.
In my opinion, It 's better not to apply this patch.
I will post patch with changing size in sc7180.dtsi file.
On 1/22/2021 1:09 AM, Mark Brown wrote:
On Fri, 15 Jan 2021 12:33:29 -0800, Stephen Boyd wrote:
Suspending/resuming with an
On 1/21/21 5:40 PM, Andrey Konovalov wrote:
>> diff --git a/lib/test_kasan.c b/lib/test_kasan.c
>> index 7285dcf9fcc1..1306f707b4fe 100644
>> --- a/lib/test_kasan.c
>> +++ b/lib/test_kasan.c
>> @@ -52,6 +52,11 @@ static int kasan_test_init(struct kunit *test)
>> return -1;
>>
On 1/21/21 5:34 PM, Andrey Konovalov wrote:
>> +- ``kasan.mode=sync`` or ``=async`` controls whether KASAN is configured in
>> + synchronous or asynchronous mode of execution (default: ``sync``).
>> + ``synchronous mode``: an exception is triggered if a tag check fault
>> occurs.
>
From: Wen Su
The MT6359 is a regulator found on boards based on MediaTek MT6779 and
probably other SoCs. It is a so called pmic and connects as a slave to
SoC using SPI, wrapped inside the pmic-wrapper.
Signed-off-by: Wen Su
Signed-off-by: Hsin-Hsiung Wang
---
changes since v4:
- add enable
Am 2021-01-22 10:10, schrieb claudiu.bez...@microchip.com:
On 21.01.2021 11:41, Michael Walle wrote:
EXTERNAL EMAIL: Do not click links or open attachments unless you know
the
content is safe
Hi Claudiu,
Am 2021-01-21 10:19, schrieb claudiu.bez...@microchip.com:
On 20.01.2021 21:43, Michael
This patchset includes refactoring interrupt and adding support to MT6359 PMIC.
MT6359 is the primary PMIC for MT6779 and probably other SOCs.
The series[1] sent by Wen will continue to upstream in this patchset afterwards.
[1]
On 2021-01-20 13:54:03 [-0800], Paul E. McKenney wrote:
> > > +// Record ptr in a page managed by krcp, with the pre-krc_this_cpu_lock()
> > > +// state specified by flags. If can_alloc is true, the caller must
> > > +// be schedulable and not be holding any locks or mutexes that might be
> > >
On 1/22/21 10:02 AM, Mark Rutland wrote:
> On Thu, Jan 21, 2021 at 01:43:14PM -0800, Paul E. McKenney wrote:
>> On Thu, Jan 21, 2021 at 09:31:10PM +, Will Deacon wrote:
>>> On Thu, Jan 21, 2021 at 10:55:21AM -0800, Paul E. McKenney wrote:
On Thu, Jan 21, 2021 at 10:37:21PM +0530,
Intel Moorestown and Medfield are quite old Intel Atom based
32-bit platforms, which were in limited use in some Android phones,
tablets and consumer electronics more than eight years ago.
There are no bugs or problems ever reported outside from Intel
for breaking any of that platforms for years.
On 22/01/21 11:09, Song Bao Hua (Barry Song) wrote:
>> -Original Message-
>> From: Dietmar Eggemann [mailto:dietmar.eggem...@arm.com]
>> > For example, every cpu with the below numa_distance can have
>> > "groups don't span domain->span":
>> > node 0 1 2 3
>> > 0: 10 12 20 22
On Wed, Jan 20, 2021 at 04:57:56PM +0800, Nicolas Boichat wrote:
> On Tue, Jan 12, 2021 at 4:59 PM Xin Ji wrote:
> >
> > Hi Rob Herring, thanks for the comments.
> >
> > On Mon, Jan 11, 2021 at 04:14:35PM -0600, Rob Herring wrote:
> > > On Thu, Dec 31, 2020 at 10:21:12AM +0800, Xin Ji wrote:
> >
Hello,
On 22.01.21 12:24, Oleksij Rempel wrote:
> Add simple GPIO base pulse counter. This device is used to measure
> rotation speed of some agricultural devices, so no high frequency on the
> counter pin is expected.
>
> The maximal measurement frequency depends on the CPU and system load. On
On Fri, Jan 15, 2021 at 04:07:23PM -0800, Jakub Kicinski wrote:
> On Fri, 15 Jan 2021 15:30:35 +0100 Oleksij Rempel wrote:
> > Since 20dd3850bcf8 ("can: Speed up CAN frame receiption by using
> > ml_priv") the CAN framework uses per device specific data in the AF_CAN
> > protocol. For this purpose
Hi Yanan,
On 2021-01-22 10:13, Yanan Wang wrote:
Hi, Will, Marc,
Is there any further comment on the v3 series I post previously?
None, I was planning to queue them for 5.12 over the weekend.
If they are not fine to you, then I think maybe we should just turn
back to the original solution
Randy found that with the following Kconfig settings we have duplicate
definitions (e.g. __inittest()) in sdhci-of-aspeed due to competing
module_init()/module_exit() calls from kunit and driver the itself.
```
CONFIG_MMC_SDHCI_OF_ASPEED=m
CONFIG_MMC_SDHCI_OF_ASPEED_TEST=y
```
Conditionally
On Fri, Jan 22, 2021 at 10:44 AM mtk15103 wrote:
>
> On Thu, 2021-01-21 at 20:13 +0800, Nicolas Boichat wrote:
> > On Thu, Jan 21, 2021 at 8:09 PM mtk15103 wrote:
> > >
> > > On Thu, 2021-01-21 at 16:55 +0800, Nicolas Boichat wrote:
> > > > On Thu, Jan 21, 2021 at 3:52 PM Hailong Fan
> > > >
On Fri, 22 Jan 2021 11:03:48 +0100,
Jamie Heilman wrote:
>
> Takashi Iwai wrote:
> > You seem hitting a firmware bug, and it doesn't look like the only
> > case. Interestingly, the backport of 5.11 USB-audio stuff on 5.3
> > kernel on openSUSE Leap 15.2 caused a similar bug on Steinberg device,
On Tue, Jan 19, 2021 at 06:57:26PM +, Bae, Chang Seok wrote:
> This series attempts to save the AMX state in the context switch buffer only
What is the context switch buffer?
I think you mean simply the xstate per-task buffer which is switched on
context switches...
> when needed -- so it
On Fri, Jan 22, 2021 at 12:43 PM Andy Shevchenko
wrote:
>
> Intel Moorestown and Medfield are quite old Intel Atom based
> 32-bit platforms, which were in limited use in some Android phones,
> tablets and consumer electronics more than eight years ago.
>
> There are no bugs or problems ever
On Thu, Jan 21, 2021 at 04:39:41PM +, Vincenzo Frascino wrote:
> MTE provides a mode that asynchronously updates the TFSR_EL1 register
> when a tag check exception is detected.
>
> To take advantage of this mode the kernel has to verify the status of
> the register at:
> 1. Context
On Fri, Jan 8, 2021 at 10:23 AM Zheng Yongjun wrote:
>
> Replace a comma between expression statements by a semicolon.
>
> Signed-off-by: Zheng Yongjun
> ---
> drivers/gpio/gpio-tegra186.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpio/gpio-tegra186.c
On Fri, Jan 22, 2021 at 10:11:57AM +, Mark Rutland wrote:
> On Thu, Jan 21, 2021 at 05:04:16PM +0100, Thomas Bogendoerfer wrote:
> > When there's a fatal signal pending, MIPS's do_page_fault()
> > implementation returns. The intent is that we'll return to the
> > faulting userspace
On Thu, Jan 21, 2021 at 05:04:16PM +0100, Thomas Bogendoerfer wrote:
> When there's a fatal signal pending, MIPS's do_page_fault()
> implementation returns. The intent is that we'll return to the
> faulting userspace instruction, delivering the signal on the way.
>
> However, if we take a fatal
On Fri, Jan 22, 2021 at 03:53:18PM +0800, Tiezhu Yang wrote:
> The kernel definitions of MIPSInst_FMA_FUNC and MIPSInst_FMA_FFMT are not
> consistent with MADD.fmt, NMADD.fmt and NMSUB.fmt in the MIPS64 manual [1],
> the field func is bit 5..3 and fmt is bit 2..0, fix them. Otherwise there
>
Add an optional "clock-names" property, it's not used to get the clock,
but some DTS files (e.g. mt8183) provide it.
Cc: Chun-Kuang Hu
Cc: Philipp Zabel
Signed-off-by: Chunfeng Yun
---
v2: new patch separated from [3/15] suggested by CK
---
This is used to fix dtbs_check warning
Signed-off-by: Chunfeng Yun
---
v2: no changes
---
arch/arm/boot/dts/mt2701.dtsi | 19 +++
1 file changed, 11 insertions(+), 8 deletions(-)
diff --git a/arch/arm/boot/dts/mt2701.dtsi b/arch/arm/boot/dts/mt2701.dtsi
index
The compatilbe "mediatek,mt7623-mipi-tx" is not supported in driver,
and in fact uses "mediatek,mt2701-mipi-tx" instead on MT7623, so changes
the compatible items to make dependence clear.
Cc: Chun-Kuang Hu
Cc: Philipp Zabel
Signed-off-by: Chunfeng Yun
---
v2: separate two patches suggested by
Add two compatible for mt2701 and mt7623;
Signed-off-by: Chunfeng Yun
---
v2: new patch separated from [6/15]
---
Documentation/devicetree/bindings/usb/mediatek,mtk-xhci.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/usb/mediatek,mtk-xhci.yaml
Add support mt8516 compatbile
Signed-off-by: Chunfeng Yun
---
v2: no changes
---
Documentation/devicetree/bindings/usb/mediatek,musb.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/usb/mediatek,musb.yaml
Harmonize nodes names, compatibles and remove unused property.
Signed-off-by: Chunfeng Yun
---
v2: no changes
---
arch/arm64/boot/dts/mediatek/mt8173-evb.dts | 4 +---
arch/arm64/boot/dts/mediatek/mt8173.dtsi| 13 +++--
2 files changed, 8 insertions(+), 9 deletions(-)
diff --git
This is used to fix dtbs_check warning
Signed-off-by: Chunfeng Yun
---
v2: no changes
---
arch/arm64/boot/dts/mediatek/mt7622.dtsi | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/arch/arm64/boot/dts/mediatek/mt7622.dtsi
b/arch/arm64/boot/dts/mediatek/mt7622.dtsi
Borislav Petkov writes:
> On Fri, Jan 22, 2021 at 11:11:24AM +0100, Borislav Petkov wrote:
>> Hi,
>>
>> this triggers is on 5.11-rc3 + tip/x86/urgent (shouldn't matter tho),
>> 32-bit kernel:
>
> This looks like a multiple wireless drivers issue, this is on another
> 32-bit machine with ath5k
Add SPDX-Licence-Identifier.
Signed-off-by: Claudiu Beznea
---
drivers/soc/atmel/soc.c | 1 +
drivers/soc/atmel/soc.h | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/soc/atmel/soc.c b/drivers/soc/atmel/soc.c
index 728d461ad6d6..1a6cb4bc7d67 100644
--- a/drivers/soc/atmel/soc.c
+++
On Thu, Jan 21, 2021 at 11:11:17AM +, Mark Rutland wrote:
[ . . . ]
> I've given this a spin atop v5.11-rc4, building natively on arm64 on a
> Debian 10.7 system, and with the whole series applied I'm able to run
> the rcutorture kvm.sh script without issue (the CONFIG warnings are
>
The driver core ignores the return value of the remove callback, so
don't give isa drivers the chance to provide a value.
Adapt all isa_drivers with a remove callbacks accordingly; they all
return 0 unconditionally anyhow.
Acked-by: Marc Kleine-Budde # for
drivers/net/can/sja1000/tscan1.c
From: Archie Pusaka
Hi linux-bluetooth,
This series of patches manages the hardware offloading part of MSFT
extension API. The full documentation can be accessed by this link:
Hi,
On 1/22/21 1:50 PM, Linus Walleij wrote:
> On Tue, Jan 19, 2021 at 6:28 AM Sai Krishna Potthuri
> wrote:
>
>> Add pinctrl support to query platform specific information (pins)
>> from firmware.
>>
>> Signed-off-by: Sai Krishna Potthuri
>
> I need an ACK from the maintainer of this file to
For RLIMIT_NPROC and some other rlimits the user_struct that holds the
global limit is kept alive for the lifetime of a process by keeping it
in struct cred. Add a ucounts reference to struct cred, so that
RLIMIT_NPROC can switch from using a per user limit to using a per user
per user namespace
Hi Maxime
On Mon, 11 Jan 2021 at 14:23, Maxime Ripard wrote:
>
> The BCM2711 has two different interrupt sources to transmit and receive
> CEC messages, provided through an external interrupt chip shared between
> the two HDMI interrupt controllers.
>
> The rest of the CEC controller is
Hi Maxime
On Mon, 11 Jan 2021 at 14:23, Maxime Ripard wrote:
>
> The HDMI controller found in the BCM2711 has an external interrupt
> controller for the CEC and hotplug interrupt shared between the two
> instances.
>
> Let's add a variant flag to register a single interrupt handler and
> deals
On Thu, Jan 21, 2021 at 4:19 AM Bjorn Andersson
wrote:
> On Wed 20 Jan 01:29 CST 2021, Jiapeng Zhong wrote:
>
> > Fix the following coccicheck warnings:
> >
> > ./drivers/pinctrl/qcom/pinctrl-ssbi-gpio.c:340:3-15: WARNING:
> > Assignment of 0/1 to bool variable.
> >
> > Reported-by: Abaci Robot
On Fri, Jan 22, 2021 at 09:21:20PM +0800, Leizhen (ThunderTown) wrote:
> On 2021/1/22 21:00, Robin Murphy wrote:
> > On 2021-01-22 12:51, Will Deacon wrote:
> >> On Thu, Nov 26, 2020 at 11:42:30AM +0800, Zhen Lei wrote:
> >>> - tblp = ptep - ARM_LPAE_LVL_IDX(iova, lvl, data);
> >>> -
Hi,
On 1/22/21 2:04 PM, Charles Keepax wrote:
> On Fri, Jan 22, 2021 at 01:23:44PM +0100, Hans de Goede wrote:
>> On 1/22/21 12:26 PM, Charles Keepax wrote:
>>> On Thu, Jan 21, 2021 at 05:55:00PM +0100, Hans de Goede wrote:
On 1/19/21 10:51 AM, Richard Fitzgerald wrote:
> On 18/01/2021
Hi Jyoti,
a few remarks below.
On Thu, Jan 21, 2021 at 11:21:47PM +, Jyoti Bhayana wrote:
> This change provides ARM SCMI Protocol based IIO device.
> This driver provides support for Accelerometer and Gyroscope using
> new SCMI Sensor Protocol defined by the upcoming SCMIv3.0
I'd say:
new
On Thu, Jan 21, 2021 at 10:24:10PM -0800, Alistair Francis wrote:
> On Mon, Jan 18, 2021 at 4:32 AM Mark Brown wrote:
> > On Sat, Jan 16, 2021 at 08:25:37PM -0800, Alistair Francis wrote:
> > > +static int get_vcom_voltage_op(struct regulator_dev *rdev)
> > > +{
> > > + int ret =
On Fri, Jan 22, 2021 at 02:19:07PM +0100, Linus Walleij wrote:
> On Thu, Jan 21, 2021 at 7:26 AM Manivannan Sadhasivam
> wrote:
>
> > The Actions Semi pinctrl drivers are a mix of both ARM32 and ARM64
> > platforms. So let's add the correct platform dependency to avoid them
> > being selected on
On Fri, Jan 22, 2021 at 2:35 PM Gerd Hoffmann wrote:
>
> On Fri, Jan 22, 2021 at 09:13:42AM +0100, Thomas Zimmermann wrote:
> > Hi
> >
> > Am 20.01.21 um 12:12 schrieb Gerd Hoffmann:
> > > Balances the qxl_create_bo(..., pinned=true, ...);
> > > call in qxl_release_bo_alloc().
> > >
> > >
This patchset implements the asynchronous mode support for ARMv8.5-A
Memory Tagging Extension (MTE), which is a debugging feature that allows
to detect with the help of the architecture the C and C++ programmatic
memory errors like buffer overflow, use-after-free, use-after-return, etc.
MTE is
KASAN provides an asynchronous mode of execution.
Add reporting functionality for this mode.
Cc: Dmitry Vyukov
Cc: Andrey Ryabinin
Cc: Alexander Potapenko
Cc: Andrey Konovalov
Reviewed-by: Andrey Konovalov
Signed-off-by: Vincenzo Frascino
---
include/linux/kasan.h | 2 ++
MTE provides an asynchronous mode for detecting tag exceptions. In
particular instead of triggering a fault the arm64 core updates a
register which is checked by the kernel after the asynchronous tag
check fault has occurred.
Add support for MTE asynchronous mode.
The exception handling
MTE provides a mode that asynchronously updates the TFSR_EL1 register
when a tag check exception is detected.
To take advantage of this mode the kernel has to verify the status of
the register at:
1. Context switching
2. Return to user/EL0 (Not required in entry from EL0 since the kernel
On Thu, 21 Jan 2021 16:56:58 +0100, Mike Looijmans wrote:
> This adds the device-tree bindings for the Bosch Sensortec BMI088 IMU,
> the accelerometer part.
>
> Signed-off-by: Mike Looijmans
>
> ---
>
> Changes in v7:
> Add additionalProperties
> Change bmi088_accel to bmi088-accel
> Add
Architectures supported by KASAN_HW_TAGS can provide a sync or async mode
of execution. On an MTE enabled arm64 hw for example this can be identified
with the synchronous or asynchronous tagging mode of execution.
In synchronous mode, an exception is triggered if a tag check fault occurs.
In
Local variable 'zone_start_pfn' is not needed since there's only
one call site in free_area_init_core(). Let's remove it and pass
zone->zone_start_pfn directly to init_currently_empty_zone().
Signed-off-by: Baoquan He
Reviewed-by: Mike Rapoport
Reviewed-by: David Hildenbrand
---
Parameter 'zone' has got needed information, let's remove other
unnecessary parameters.
Signed-off-by: Baoquan He
Reviewed-by: Mike Rapoport
Reviewed-by: David Hildenbrand
---
mm/page_alloc.c | 17 +++--
1 file changed, 7 insertions(+), 10 deletions(-)
diff --git
The current memmap_init_zone() only handles memory region inside one zone,
actually memmap_init() does the memmap init of one zone. So rename both of
them accordingly.
Signed-off-by: Baoquan He
---
arch/ia64/mm/init.c | 6 +++---
include/linux/mm.h | 4 ++--
mm/memory_hotplug.c | 2 +-
As David suggested, simply passing 'struct zone *zone' is enough. We can
get all needed information from 'struct zone*' easily.
Suggested-by: David Hildenbrand
Signed-off-by: Baoquan He
---
arch/ia64/mm/init.c | 12 +++-
include/linux/mm.h | 3 +--
mm/page_alloc.c | 24
This adds NTFS journal
Signed-off-by: Konstantin Komarov
---
fs/ntfs3/fslog.c | 5204 ++
1 file changed, 5204 insertions(+)
create mode 100644 fs/ntfs3/fslog.c
diff --git a/fs/ntfs3/fslog.c b/fs/ntfs3/fslog.c
new file mode 100644
index
From: Aya Levin
[ Upstream commit b210de4f8c97d57de051e805686248ec4c6cfc52 ]
There are cases where GSO segment's length exceeds the egress MTU:
- Forwarding of a TCP GRO skb, when DF flag is not set.
- Forwarding of an skb that arrived on a virtualisation interface
(virtio-net/vhost/tap)
From: Nicolas Ferre
Arnd, Olof,
I'm taking back the lead on sending the pull-requests for AT91 and hope that I
didn't loose the knowledge in the meantime. Tell me if there's something I'm
missing. Thanks a lot to Alexandre who kept our flow steady and very
predictable during all those years!
From: Vladimir Oltean
[ Upstream commit 91158e1680b164c8d101144ca916a3dca10c3e17 ]
Florian reported a use-after-free bug in devlink_nl_port_fill found with
KASAN:
(devlink_nl_port_fill)
(devlink_port_notify)
(devlink_port_unregister)
(dsa_switch_teardown.part.3)
(dsa_tree_teardown_switches)
From: Geert Uytterhoeven
[ Upstream commit f97844f9c518172f813b7ece18a9956b1f70c1bb ]
The merge resolution of the interaction of commits 307eea32b202864c
("dt-bindings: net: renesas,ravb: Add support for r8a774e1 SoC") and
d7adf6331189cbe9 ("dt-bindings: net: renesas,etheravb: Convert to
From: Felix Fietkau
commit 2463ec86cd0338a2c2edbfb0b9d50c52ff76ff43 upstream.
ieee80211_tx_h_select_key drops any non-mgmt packets without a key when
encryption is used. This is wrong for nulldata packets that can't be
encrypted and are sent out for probing clients and indicating 4-address
On Fri, Jan 22, 2021 at 3:38 PM Vincenzo Frascino
wrote:
>
> With the introduction of KASAN_HW_TAGS, kasan_report() dereferences
> the address passed as a parameter.
It doesn't dereference the address, it accesses the metadata. And only
when addr_has_metadata() succeeds.
>
> Add a comment to
From: Jesper Dangaard Brouer
commit f6351c3f1c27c80535d76cac2299aec44c36291e upstream.
The old way of changing the conntrack hashsize runtime was through changing
the module param via file /sys/module/nf_conntrack/parameters/hashsize. This
was extended to sysctl change in commit 3183ab8997a4
From: Qinglang Miao
[ Upstream commit ca4c6ebeeb50112f5178f14bfb6d9e8ddf148545 ]
If alloc_canfd_skb() returns NULL, 'cfg' is an uninitialized variable, so we
should check 'skb' rather than 'cfd' after calling alloc_canfd_skb(priv->ndev,
).
Fixes: 55e5b97f003e ("can: mcp25xxfd: add driver for
From: Michael Hennerich
commit 4d163ad79b155c71bf30366dc38f8d2502f78844 upstream.
The issue is that using SPI from a callback under the CCF lock will
deadlock, since this code uses clk_get_rate().
Fixes: c474b38665463 ("spi: Add driver for Cadence SPI controller")
Signed-off-by: Michael
From: Christophe Leroy
commit 7a2da5d7960a64ee923fe3e31f01a1101052c66f upstream.
Commit 766c6b63aa04 ("spi: fix client driver breakages when using GPIO
descriptors") broke fsl spi driver.
As now we fully rely on gpiolib for handling the polarity of
chip selects, the driver shall not alter the
On Fri, 22 Jan 2021 09:20:40 +0100, corentin wrote:
>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] drivers: spi: spi-au1550: Fix various whitespace warnings
commit: 21f68c8259a8100ddee985c1536f32a19ed521df
All being well this
From: Greg Kroah-Hartman
This reverts commit 17a08680ab6a6c057949cb48c352933e09ea377a which is
commit 9bba03d4473df0b707224d4d2067b62d1e1e2a77 upstream.
As Pavel says at Link:
https://lore.kernel.org/r/20210119182837.ga18...@duo.ucw.cz
I don't believe this is suitable for stable.
And
From: Colin Ian King
Currently when there are other connectors on the port using HDCP the
function _intel_hdcp_disable returns a garbage uninitialized value in
variable ret. I believe the intention is to return 0, so return this
literal value instead of the value in ret.
Addresses-Coverity:
On Mon, Dec 28, 2020 at 2:50 PM Zheng Yongjun wrote:
>
> spinlock can be initialized automatically with DEFINE_SPINLOCK()
> rather than explicitly calling spin_lock_init().
>
> Signed-off-by: Zheng Yongjun
> ---
> drivers/pnp/pnpbios/bioscalls.c | 3 +--
> 1 file changed, 1 insertion(+), 2
From: Colin Ian King
Currently the ! operator is incorrectly being used to flip bits on
mask values. Fix this by using the bit-wise ~ operator instead.
Addresses-Coverity: ("Logical vs. bitwise operator")
Fixes: 3c9a7b7d6e75 ("drm/amdgpu: update mmhub mgcg for mmhub_v2_3")
Signed-off-by: Colin
On 18/01/2021 13:24, Ahmad Fatoum wrote:
The nvmem cell binding applies to all eeprom child nodes matching
"^.*@[0-9a-f]+$" without taking a compatible into account.
Linux drivers, like at24, are even more extensive and assume
_all_ at24 eeprom child nodes to be nvmem cells since
22.01.2021 09:26, Viresh Kumar пишет:
> On 22-01-21, 00:36, Dmitry Osipenko wrote:
>> 21.01.2021 14:17, Viresh Kumar пишет:
>>> dev_pm_opp_set_bw() is getting removed and dev_pm_opp_set_opp() should
>>> be used instead. Migrate to the new API.
>>>
>>> Signed-off-by: Viresh Kumar
>>> ---
>>>
On Fri, Jan 22, 2021 at 09:31:37AM +0100, Peter Zijlstra wrote:
> On Thu, Jan 21, 2021 at 04:20:12PM -0800, Paul E. McKenney wrote:
>
> > > ---
> > > diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c
> > > index 368749008ae8..2c8d4c3e341e 100644
> > > --- a/kernel/rcu/tree.c
> > > +++
On Fri, Jan 22, 2021 at 08:43:18PM +0530, Naresh Kamboju wrote:
> On Fri, 22 Jan 2021 at 20:38, Greg Kroah-Hartman
> wrote:
> >
> > On Fri, Jan 22, 2021 at 08:32:46PM +0530, Naresh Kamboju wrote:
> > > On Fri, 22 Jan 2021 at 19:45, Greg Kroah-Hartman
> > > wrote:
> > > >
> > > > This is the
From: Tom Rix
Every FPGA has several subdevices in other subsystems.
The new FPGA subdevices section is necessary to ensure changes to
the subdevices files get reviewed within the context of the FPGA
subsystem.
Signed-off-by: Tom Rix
---
MAINTAINERS | 6 ++
1 file changed, 6 insertions(+)
On Fri, Jan 22, 2021 at 03:21:07PM +0530, Naresh Kamboju wrote:
> On Fri, 22 Jan 2021 at 03:13, Paul E. McKenney wrote:
> >
> > On Thu, Jan 21, 2021 at 09:31:10PM +, Will Deacon wrote:
> > > On Thu, Jan 21, 2021 at 10:55:21AM -0800, Paul E. McKenney wrote:
> > > > On Thu, Jan 21, 2021 at
Refactor phylink_of_phy_connect() to use phylink_fwnode_phy_connect().
Signed-off-by: Calvin Johnson
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
drivers/net/phy/phylink.c | 39 +--
1 file changed, 1 insertion(+), 38 deletions(-)
diff
On Sat, Jan 16, 2021 at 12:58 AM wrote:
>
> From: Tom Rix
>
> Defining DEBUG should only be done in development.
> So remove DEBUG.
>
> Signed-off-by: Tom Rix
> ---
> drivers/idle/intel_idle.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/idle/intel_idle.c
On Fri, Jan 22, 2021 at 08:50:43PM +0530, Naresh Kamboju wrote:
> On Fri, 22 Jan 2021 at 19:45, Greg Kroah-Hartman
> wrote:
> >
> > This is the start of the stable review cycle for the 4.14.217 release.
> > There are 50 patches in this series, all will be posted as a response
> > to this one. If
On Fri, 22 Jan 2021, Rafael J. Wysocki wrote:
> On Fri, Jan 22, 2021 at 4:48 PM Naresh Kamboju
> wrote:
> >
> > On Fri, 22 Jan 2021 at 20:39, Rafael J. Wysocki wrote:
> > >
> > > On Thu, Jan 21, 2021 at 8:01 PM Rafael J. Wysocki
> > > wrote:
> > > >
> > > > On Thu, Jan 21, 2021 at 6:23 PM
22.01.2021 16:40, Mark Brown пишет:
> On Fri, Jan 22, 2021 at 01:16:49AM +0300, Dmitry Osipenko wrote:
>
>> +/* balance only if there are regulators coupled */
>> +if (rdev->coupling_desc.n_coupled > 1) {
>> +ret = regulator_balance_voltage(rdev, PM_SUSPEND_ON);
>> +
A second CHARLCD config symbol was added instead of moving the existing
one. Fix this by removing the old one.
Fixes: 718e05ed92ecac0d ("auxdisplay: Introduce hd44780_common.[ch]")
Signed-off-by: Geert Uytterhoeven
---
drivers/auxdisplay/Kconfig | 3 ---
1 file changed, 3 deletions(-)
diff
On Fri, 22 Jan 2021, Nicolas Pitre wrote:
> On Fri, 22 Jan 2021, Rafael J. Wysocki wrote:
>
> > On Fri, Jan 22, 2021 at 4:48 PM Naresh Kamboju
> > wrote:
> > >
> > > On Fri, 22 Jan 2021 at 20:39, Rafael J. Wysocki wrote:
> > > >
> > > > On Thu, Jan 21, 2021 at 8:01 PM Rafael J. Wysocki
> > >
On Thu, Jan 21, 2021 at 08:08:24PM +, David Howells wrote:
> J. Bruce Fields wrote:
> > So, I'm still confused: there must be some case where we know fscache
> > actually works reliably and doesn't corrupt your data, right?
>
> Using ext2/3, for example. I don't know under what
On 21-01-20 22:56, Alistair Francis wrote:
> Allow the wacom-i2c device to be exposed via device tree.
You did a lot more than exposing.
> Signed-off-by: Alistair Francis
> ---
> .../input/touchscreen/wacom,wacom-i2c.yaml | 4
> drivers/input/touchscreen/wacom_i2c.c| 16
On 21/1/21 12:13 am, Joe Perches wrote:
> On Wed, 2021-01-20 at 18:23 +0530, Aditya wrote:
>> On 20/1/21 2:51 pm, Joe Perches wrote:
>>> On Wed, 2021-01-20 at 12:55 +0530, Aditya Srivastava wrote:
Local symbols prefixed with '.L' do not emit symbol table entries, as
they have special
601 - 700 of 1467 matches
Mail list logo
