From: Ranjani Sridharan
Add client APIs to invoke the platform-specific DSP probes
ops. Also, add a new API to get the SOF core device pointer
which will be used for DMA buffer allocation.
Reviewed-by: Pierre-Louis Bossart
Tested-by: Fred Oh
Signed-off-by: Ranjani Sridharan
Signed-off-by: Dav
On Fri, Nov 13, 2020 at 02:15:59PM +0100, Niklas Schnelle wrote:
>
>
> On 11/12/20 6:36 PM, Keith Busch wrote:
> > On Thu, Nov 12, 2020 at 04:45:35PM +0100, Niklas Schnelle wrote:
> >> You got to get something wrong, I hope in this case it's just the subject
> >> of the cover letter :D
> >
> > I
On Thu, Nov 12, 2020 at 02:49:19PM -0800, Andrew Morton wrote:
> On Thu, 12 Nov 2020 12:01:01 -0800 Minchan Kim wrote:
>
> >
> > On Sat, Nov 07, 2020 at 12:39:39AM -0800, Minchan Kim wrote:
> > > Hi Andrew,
> > >
> > > On Fri, Nov 06, 2020 at 05:59:33PM -0800, Andrew Morton wrote:
> > > > On Th
On Fri, 13 Nov 2020 at 17:15, Ard Biesheuvel wrote:
>
> On Fri, 13 Nov 2020 at 16:58, Russell King - ARM Linux admin
> wrote:
> >
> > On Fri, Nov 13, 2020 at 03:43:27PM +, Guillaume Tucker wrote:
> > > On 13/11/2020 10:35, Ard Biesheuvel wrote:
> > > > On Fri, 13 Nov 2020 at 11:31, Guillaume
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an
issue:
INFO: task can't die in nbd_ioctl
INFO: task syz-executor.1:10354 can't die for more than 143 seconds.
task:syz-executor.1 state:D stack:28664 pid:10354 ppid: 8887 flags:0x4004
Call Trace:
context
inline the shmem_mapping(), and use shmem_mapping()
instead of 'inode->i_mapping->a_ops == &shmem_aops'
in shmem_evict_inode().
Signed-off-by: Hui Su
---
include/linux/shmem_fs.h | 2 +-
mm/shmem.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/lin
On Fri, 2020-11-13 at 09:14 +0100, Miguel Ojeda wrote:
> On Fri, Nov 13, 2020 at 1:09 AM Nick Desaulniers
> wrote:
> >
> > Thank you for the explicit diagnostics observed. Something fishy is
> > going on though, https://godbolt.org/z/Gbxbxa is how I expect MSVC to
> > handle include/linux/compil
The OSM L3 interconnect driver is used for scaling the bus to the L3
cache on modern Qualcomm platforms, enable it.
Signed-off-by: Bjorn Andersson
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
inde
On Fri, Nov 13, 2020 at 6:36 AM Thomas Gleixner wrote:
> On Fri, Nov 13 2020 at 05:50, Max Filippov wrote:
> > On Fri, Nov 13, 2020 at 5:40 AM Thomas Gleixner wrote:
> >> What's wrong with just doing the obvious and making the fixmap defines
> >> the other way round?
> >
> > It becomes really awk
On Fri, Nov 13, 2020 at 01:18:05PM +, John Boero wrote:
> Thanks for the tips.
>
> I've spent some more time on this this morning.
> It looks like it's not the dev after all.
What isn't the dev?
> Every interface in the dev is set NULL after init.
I can't tell what this means. Please be mo
On Fri, Nov 13, 2020 at 02:42:27PM +0800, Zhang Changzhong wrote:
> Fix to return a negative error code from the error handling
> case instead of 0, as done elsewhere in this function.
>
> Fixes: 4730f4a6c6b2 ("IB/hfi1: Activate the dummy netdev")
> Reported-by: Hulk Robot
> Signed-off-by: Zhang
On Fri, 2020-11-13 at 10:11 +0100, Uwe Kleine-König wrote:
> Signed-off-by: Uwe Kleine-König
> ---
> Hello,
>
> this can also be squashed into the respective patches instead.
>
> Best regards
> Uwe
>
> scripts/checkpatch.pl | 5 +
> 1 file changed, 5 insertions(+)
>
> diff --git a/scripts
On 11/12/2020 11:26 PM, Alex Shi wrote:
> The are some kernel-doc interface issues:
> security/smack/smackfs.c:1950: warning: Function parameter or member
> 'list' not described in 'smk_parse_label_list'
> security/smack/smackfs.c:1950: warning: Excess function parameter
> 'private' description in
On Fri, Nov 13, 2020 at 01:14:45AM +0300, Dmitry Osipenko wrote:
> 12.11.2020 23:43, Thierry Reding пишет:
> >> The difference in comparison to using voltage regulator directly is
> >> minimal, basically the core-supply phandle is replaced is replaced with
> >> a power-domain phandle in a device tr
On 11/13/20 18:34, Bjorn Andersson wrote:
> The OSM L3 interconnect driver is used for scaling the bus to the L3
> cache on modern Qualcomm platforms, enable it.
>
> Signed-off-by: Bjorn Andersson
Reviewed-by: Georgi Djakov
> ---
> arch/arm64/configs/defconfig | 1 +
> 1 file changed, 1 inser
Hi Sudeep,
On Friday 13 Nov 2020 at 14:16:58 (+), Sudeep Holla wrote:
[..]
> > diff --git a/arch/arm64/kernel/topology.c b/arch/arm64/kernel/topology.c
> > index b8cb16e3a2cc..7c9b6a0ecd6a 100644
> > --- a/arch/arm64/kernel/topology.c
> > +++ b/arch/arm64/kernel/topology.c
> > @@ -147,6 +147,9
On Tue, 10 Nov 2020 21:42:33 +0800
"xuxiaoyang (C)" wrote:
> vfio_iommu_type1_pin_pages is very inefficient because
> it is processed page by page when calling vfio_pin_page_external.
> Added contiguous_vaddr_get_pfn to process continuous pages
> to reduce the number of loops, thereby improving p
d_hda_core
tegra_xudc host1x lp855x_bl at24 ip_tables x_tables ipv6
[ 153.566417] CPU: 0 PID: 300 Comm: systemd-sleep Tainted: G C
5.10.0-rc3-next-20201113-00019-g5c064d5372b0-dirty #624
[ 153.578283] Hardware name: NVIDIA Jetson TX1 Developer Kit (DT)
[ 153.5
Sorry I wanted to include a pastebin or link but was trying to follow maillist
guidelines and not include links or exceed wrap guidelines. Full contents:
https://paste.centos.org/view/3746bc40
Yes I understand the return dodges the config dereference.
Original line usb.c:281 is the original erro
On Fri, Nov 06, 2020 at 10:14:14AM -0300, Guilherme G. Piccoli wrote:
> On 23/10/2018 14:03, Bjorn Helgaas wrote:
> > On Mon, Oct 22, 2018 at 05:35:06PM -0300, Guilherme G. Piccoli wrote:
> >> On 18/10/2018 19:15, Bjorn Helgaas wrote:
> >>> On Thu, Oct 18, 2018 at 03:37:19PM -0300, Guilherme G. Pic
On Fri, 2020-11-13 at 12:54 +0200, Sakari Ailus wrote:
> Hi Joe,
>
> On Tue, Nov 03, 2020 at 08:49:36AM -0800, Joe Perches wrote:
> > On Tue, 2020-11-03 at 16:56 +0200, Sakari Ailus wrote:
> > > On Tue, Nov 03, 2020 at 04:47:47PM +0200, Andy Shevchenko wrote:
> > > > On Tue, Nov 03, 2020 at 03:34:
--
Dear Beloved One.
I am Mr. Gabriel Edgal , I'm an internal Auditor in Btci bank,I have an
abandoned fund of $9.5 million Dollars to transfer to you ,which we are
going to share 50:50 .You will only stand as the next of kin to my late
client who deposited the fund in our bank so many years ba
On Wed, Nov 11, 2020 at 3:30 AM Syed Nayyar Waris wrote:
>
> On Tue, Nov 10, 2020 at 12:43:16PM -0500, William Breathitt Gray wrote:
> > On Tue, Nov 10, 2020 at 10:52:42PM +0530, Syed Nayyar Waris wrote:
> > > On Tue, Nov 10, 2020 at 6:05 PM William Breathitt Gray
> > > wrote:
> > > >
> > > > On
From: Ioana Ciornei
In an attempt to actually support shared IRQs in phylib, we now move the
responsibility of triggering the phylib state machine or just returning
IRQ_NONE, based on the IRQ status register, to the PHY driver. Having
3 different IRQ handling callbacks (.handle_interrupt(),
.did_
From: Ioana Ciornei
In preparation of removing the .ack_interrupt() callback, we must replace
its occurrences (aka phy_clear_interrupt), from the 2 places where it is
called from (phy_enable_interrupts and phy_disable_interrupts), with
equivalent functionality.
This means that clearing interrupt
From: Ioana Ciornei
In an attempt to actually support shared IRQs in phylib, we now move the
responsibility of triggering the phylib state machine or just returning
IRQ_NONE, based on the IRQ status register, to the PHY driver. Having
3 different IRQ handling callbacks (.handle_interrupt(),
.did_
On 11/13/20 5:25 PM, Christoph Hellwig wrote:
> On Fri, Nov 13, 2020 at 02:15:59PM +0100, Niklas Schnelle wrote:
>>
>>
>> On 11/12/20 6:36 PM, Keith Busch wrote:
>>> On Thu, Nov 12, 2020 at 04:45:35PM +0100, Niklas Schnelle wrote:
You got to get something wrong, I hope in this case it's jus
From: Ioana Ciornei
In preparation of removing the .ack_interrupt() callback, we must replace
its occurrences (aka phy_clear_interrupt), from the 2 places where it is
called from (phy_enable_interrupts and phy_disable_interrupts), with
equivalent functionality.
This means that clearing interrupt
From: Ioana Ciornei
In preparation of removing the .ack_interrupt() callback, we must replace
its occurrences (aka phy_clear_interrupt), from the 2 places where it is
called from (phy_enable_interrupts and phy_disable_interrupts), with
equivalent functionality.
This means that clearing interrupt
From: Ioana Ciornei
This patch set aims to actually add support for shared interrupts in
phylib and not only for multi-PHY devices. While we are at it,
streamline the interrupt handling in phylib.
For a bit of context, at the moment, there are multiple phy_driver ops
that deal with this subject:
From: Ioana Ciornei
In preparation of removing the .ack_interrupt() callback, we must replace
its occurrences (aka phy_clear_interrupt), from the 2 places where it is
called from (phy_enable_interrupts and phy_disable_interrupts), with
equivalent functionality.
This means that clearing interrupt
From: Ioana Ciornei
In an attempt to actually support shared IRQs in phylib, we now move the
responsibility of triggering the phylib state machine or just returning
IRQ_NONE, based on the IRQ status register, to the PHY driver. Having
3 different IRQ handling callbacks (.handle_interrupt(),
.did_
From: Ioana Ciornei
In preparation of removing the .ack_interrupt() callback, we must replace
its occurrences (aka phy_clear_interrupt), from the 2 places where it is
called from (phy_enable_interrupts and phy_disable_interrupts), with
equivalent functionality.
This means that clearing interrupt
From: Ioana Ciornei
In preparation of removing the .ack_interrupt() callback, we must replace
its occurrences (aka phy_clear_interrupt), from the 2 places where it is
called from (phy_enable_interrupts and phy_disable_interrupts), with
equivalent functionality.
This means that clearing interrupt
From: Ioana Ciornei
In an attempt to actually support shared IRQs in phylib, we now move the
responsibility of triggering the phylib state machine or just returning
IRQ_NONE, based on the IRQ status register, to the PHY driver. Having
3 different IRQ handling callbacks (.handle_interrupt(),
.did_
From: Ioana Ciornei
In an attempt to actually support shared IRQs in phylib, we now move the
responsibility of triggering the phylib state machine or just returning
IRQ_NONE, based on the IRQ status register, to the PHY driver. Having
3 different IRQ handling callbacks (.handle_interrupt(),
.did_
From: Ioana Ciornei
In an attempt to actually support shared IRQs in phylib, we now move the
responsibility of triggering the phylib state machine or just returning
IRQ_NONE, based on the IRQ status register, to the PHY driver. Having
3 different IRQ handling callbacks (.handle_interrupt(),
.did_
From: Ioana Ciornei
In an attempt to actually support shared IRQs in phylib, we now move the
responsibility of triggering the phylib state machine or just returning
IRQ_NONE, based on the IRQ status register, to the PHY driver. Having
3 different IRQ handling callbacks (.handle_interrupt(),
.did_
From: Ioana Ciornei
In preparation of removing the .ack_interrupt() callback, we must replace
its occurrences (aka phy_clear_interrupt), from the 2 places where it is
called from (phy_enable_interrupts and phy_disable_interrupts), with
equivalent functionality.
This means that clearing interrupt
From: Ioana Ciornei
In an attempt to actually support shared IRQs in phylib, we now move the
responsibility of triggering the phylib state machine or just returning
IRQ_NONE, based on the IRQ status register, to the PHY driver. Having
3 different IRQ handling callbacks (.handle_interrupt(),
.did_
From: Ioana Ciornei
In preparation of removing the .ack_interrupt() callback, we must replace
its occurrences (aka phy_clear_interrupt), from the 2 places where it is
called from (phy_enable_interrupts and phy_disable_interrupts), with
equivalent functionality.
This means that clearing interrupt
From: Ioana Ciornei
In preparation of removing the .ack_interrupt() callback, we must replace
its occurrences (aka phy_clear_interrupt), from the 2 places where it is
called from (phy_enable_interrupts and phy_disable_interrupts), with
equivalent functionality.
This means that clearing interrupt
From: Ioana Ciornei
In an attempt to actually support shared IRQs in phylib, we now move the
responsibility of triggering the phylib state machine or just returning
IRQ_NONE, based on the IRQ status register, to the PHY driver. Having
3 different IRQ handling callbacks (.handle_interrupt(),
.did_
Please capitalize your subject lines consistently. [3/3] is fine, but
you didn't capitalize [1/3] and [2/3] to match.
The fact that this is a *chained* IRQ isn't really relevant to the
patch, so this would be more succinct:
PCI: altera-msi: Remove IRQ handler and data in one go
Lorenzo can li
Hi Hui,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on mmotm/master]
url:
https://github.com/0day-ci/linux/commits/Hui-Su/mm-shmem-c-make-shmem_mapping-inline/20201113-215549
base: git://git.cmpxchg.org/linux-mmotm.git master
config: arm-randconfig-s032
On Thu, 12 Nov 2020 18:49:17 -0700 David Ahern wrote:
> On 11/12/20 6:28 PM, Andrea Mayer wrote:
> > The implementation of SRv6 End.DT4 differs from the the implementation of
> > SRv6
> > End.DT6 due to the different *route input* lookup functions. For IPv6 is it
> > possible to force the routing
On 11/10/20 20:48, Cathy Avery wrote:
Move asid to svm->asid to allow for vmcb assignment
during svm_vcpu_run without regard to which level
guest is running.
Slightly more verbose commit message:
KVM does not have separate ASIDs for L1 and L2; either the nested
hypervisor and nested guests sha
On Friday, 13 November 2020, 00:02:54 CET, Vladimir Oltean wrote:
> On Thu, Nov 12, 2020 at 04:35:29PM +0100, Christian Eggers wrote:
> > Parts of ksz_common.h (struct ksz_device) will be required in
> > net/dsa/tag_ksz.c soon. So move the relevant parts into a new header
> > file.
> >
> > Signed-
On Friday 13 Nov 2020 at 16:02:34 (+), Mark Rutland wrote:
> On Fri, Nov 13, 2020 at 03:53:28PM +, Ionela Voinescu wrote:
> > Given that smp_call_function_single() can deadlock when interrupts are
> > disabled, abort the SMP call if irqs_disabled(). This scenario is
> > currently not possib
Acked-by: Andrzej Pietrasiewicz
W dniu 13.11.2020 o 17:06, Baskov Evgeiny pisze:
If an error happens in jpeg_get_drv_data(), i.e. match fails,
jpeg->variant field is NULL, so we cannot access it.
Consider device probe failed if jpeg->variant is NULL.
Found by Linux Driver Verification project
On Fri, Nov 13, 2020 at 08:36:44AM -0800, Joe Perches wrote:
> On Fri, 2020-11-13 at 10:11 +0100, Uwe Kleine-König wrote:
> > Signed-off-by: Uwe Kleine-König
> > ---
> > Hello,
> >
> > this can also be squashed into the respective patches instead.
> >
> > Best regards
> > Uwe
> >
> > scripts/c
This series adds support for the OV5648 image sensor,
as a V4L2 subdev driver.
Changes since v1:
- Used runtime pm;
- Used assigned-clock-rate;
- Removed clock name;
- Returned closest size in set_fmt;
- Removed unneeded references to v4l2 controls;
- Removed i2c device table;
- Dual-licensed bind
This introduces YAML bindings documentation for the OV5648
image sensor.
Signed-off-by: Paul Kocialkowski
---
.../bindings/media/i2c/ovti,ov5648.yaml | 112 ++
1 file changed, 112 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/i2c/ovti,ov5648.yaml
The OV5648 is a 5 Mpx CMOS image sensor, connected via MIPI CSI-2
in a one or two lane configuration.
Most of the features of the hardware are supported, including:
- Auto and manual exposition/gain
- Auto and manual white balance
- Horizontal and vertical flip
- Test patterns
But the following a
From: Jaehoon Chung
Exynos5440 SoC support has been dropped since commit 8c83315da1cf ("ARM:
dts: exynos: Remove Exynos5440"). Rework this driver to support DWC PCIe
variant found in the Exynos5433 SoCs.
The main difference in Exynos5433 variant is lack of the MSI support
(the MSI interrupt is n
Dear All,
This patchset is a resurrection of the DW PCIe support for the Exynos5433
SoCs posted long time ago here: https://lkml.org/lkml/2016/12/26/6 and
later here: https://lkml.org/lkml/2017/12/21/296 .
In meantime the support for the Exynos5440 SoCs has been completely
dropped from mainline k
Add dt-bindings for the Samsung Exynos PCIe controller (Exynos5433
variant). Based on the text dt-binding posted by Jaehoon Chung.
Signed-off-by: Marek Szyprowski
Reviewed-by: Krzysztof Kozlowski
Reviewed-by: Rob Herring
---
.../bindings/pci/samsung,exynos-pcie.yaml | 119 +
Add dt-bindings for the Samsung Exynos PCIe PHY controller (Exynos5433
variant). Based on the text dt-binding posted by Jaehoon Chung.
Signed-off-by: Marek Szyprowski
Reviewed-by: Krzysztof Kozlowski
Reviewed-by: Rob Herring
---
.../bindings/phy/samsung,exynos-pcie-phy.yaml | 51 ++
From: Jaehoon Chung
Exynos5440 SoC support has been dropped since commit 8c83315da1cf ("ARM:
dts: exynos: Remove Exynos5440"). Rework this driver to support PCIe PHY
variant found in the Exynos5433 SoCs.
Signed-off-by: Jaehoon Chung
[mszyprow: reworked the driver to support only Exynos5433 vari
Exynos5440 SoC support has been dropped since commit 8c83315da1cf ("ARM:
dts: exynos: Remove Exynos5440"). Drop the obsolete bindings for
exynos5440-pcie.
Signed-off-by: Marek Szyprowski
Reviewed-by: Rob Herring
Reviewed-by: Krzysztof Kozlowski
Reviewed-by: Jingoo Han
---
.../bindings/pci/sam
On 13/10/20 03:29, Sean Christopherson wrote:
@@ -3446,6 +3447,7 @@ static __no_kcsan fastpath_t svm_vcpu_run(struct kvm_vcpu
*vcpu)
sync_lapic_to_cr8(vcpu);
+ svm->vmcb->control.asid = svm->asid;
Related to the above, handling this in vcpu_run() feels wrong. There really
shouldn't b
On Wed, Nov 11, 2020 at 02:45:54PM -0800, Daniel Xu wrote:
> do_strncpy_from_user() may copy some extra bytes after the NUL
> terminator into the destination buffer. This usually does not matter for
> normal string operations. However, when BPF programs key BPF maps with
> strings, this matters a l
From: Kévin L'hôpital
The Bananapi M3 supports a camera module which includes an OV8865 sensor
connected via the parallel CSI interface and an OV8865 sensor connected
via MIPI CSI-2.
The I2C2 bus is shared by the two sensors as well as the (active-low)
reset signal, but each sensor has it own sh
This introduces YAML bindings documentation for the OV8865
image sensor.
Co-developed-by: Kévin L'hôpital
Signed-off-by: Kévin L'hôpital
Signed-off-by: Paul Kocialkowski
---
.../bindings/media/i2c/ovti,ov8865.yaml | 120 ++
1 file changed, 120 insertions(+)
create mode 1
On 21:19-20201113, Sekhar Nori wrote:
> From: Faiz Abbas
>
> Add configs to help enable regulators that supply power to the SD card
> on TI's J721e platform. These regulators are controlled by either
> SoC gpios or gpios over i2c expander.
>
> vmlinux size bef
On 11/13/20 10:02 AM, Stefano Salsano wrote:
> Il 2020-11-13 17:55, Jakub Kicinski ha scritto:
>> On Thu, 12 Nov 2020 18:49:17 -0700 David Ahern wrote:
>>> On 11/12/20 6:28 PM, Andrea Mayer wrote:
The implementation of SRv6 End.DT4 differs from the the
implementation of SRv6
End.DT6
The OV8865 is a 8 Mpx CMOS image sensor producing 3264x2448 at 30 fps.
Other modes (including some with sub-sampling) are available too.
It outputs 10-bit bayer CFA data through a MIPI CSI-2 interface with
up to 4 lanes supported.
Some register initialisation sequences are still needed for this dr
This series adds support for the OV8865 image sensor, as a V4L2 subdev
driver. Although an initial series was submitted by Kévin L'hôpital some
weeks ago, this version is significantly new and should be considered a
new series.
The final patch (not for merge) shows how to enable the OV8865 on the
Hi,
This series adds support for ARM SCMI Protocol based IIO Device.
This driver provides support for Accelerometer and Gyroscope sensor
using new SCMI Sensor Protocol defined by the upcoming SCMIv3.0 ARM
specification, which is available at
https://developer.arm.com/documentation/den0056/c/
Th
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
ARM specification
Signed-off-by: Jyoti Bhayana
---
MAINTAINERS | 6 +
drivers/iio/Kconfig
Hi Steve,
On Tue, 2020-11-10 at 10:38 -0500, Steven Rostedt wrote:
> 5.4.74-rt42-rc2 stable review patch.
> If anyone has any objections, please let me know.
>
> --
>
> From: Sebastian Andrzej Siewior
>
> In patch
>("net/Qdisc: use a seqlock instead seqcount")
>
> the seqc
On Fri, 2020-11-13 at 18:00 +0100, Uwe Kleine-König wrote:
> On Fri, Nov 13, 2020 at 08:36:44AM -0800, Joe Perches wrote:
> > On Fri, 2020-11-13 at 10:11 +0100, Uwe Kleine-König wrote:
> > > Signed-off-by: Uwe Kleine-König
> > > ---
> > > Hello,
> > >
> > > this can also be squashed into the resp
Il 2020-11-13 17:55, Jakub Kicinski ha scritto:
On Thu, 12 Nov 2020 18:49:17 -0700 David Ahern wrote:
On 11/12/20 6:28 PM, Andrea Mayer wrote:
The implementation of SRv6 End.DT4 differs from the the implementation of SRv6
End.DT6 due to the different *route input* lookup functions. For IPv6 is
On Fri, Nov 13, 2020 at 8:50 AM Lee Jones wrote:
>
> Fixes the following W=1 kernel build warning(s):
>
> drivers/gpu/drm/amd/amdgpu/amdgpu_ring.c:168: warning: Function parameter or
> member 'max_dw' not described in 'amdgpu_ring_init'
> drivers/gpu/drm/amd/amdgpu/amdgpu_ring.c:168: warning: E
13.11.2020 19:15, Mark Brown пишет:
> On Fri, Nov 13, 2020 at 06:55:27PM +0300, Dmitry Osipenko wrote:
>> 13.11.2020 17:29, Mark Brown пишет:
>
>>> It's not clear if it matters - it's more a policy decision on the part
>>> of the driver about what it thinks safe error handling is. If it's not
>
From: kernel test robot
Condition !A || A && B is equivalent to !A || B.
Generated by: scripts/coccinelle/misc/excluded_middle.cocci
Fixes: b76f0ea01312 ("coccinelle: misc: add excluded_middle.cocci script")
CC: Denis Efremov
Reported-by: kernel test robot
Signed-off-by: kernel test robot
S
On 10/27/20 9:27 AM, Halil Pasic wrote:
On Thu, 22 Oct 2020 13:12:00 -0400
Tony Krowiak wrote:
Let's implement the callback to indicate when an APQN
is in use by the vfio_ap device driver. The callback is
invoked whenever a change to the apmask or aqmask would
result in one or more queue de
On 11/13/20 5:00 AM, Hillf Danton wrote:
Thu, 12 Nov 2020 23:21:26 -0800
syzbot found the following issue on:
HEAD commit:9dbc1c03 Merge tag 'xfs-5.10-fixes-3' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1045303450
kernel con
On Fri, 13 Nov 2020 17:21:04 +0200, Claudiu Beznea wrote:
> This series adds support for ramp delay on mcp16502. It also adds
> some cleanup on mcp16502.
>
> Apart from that patches 1/6 fixes the selector validation in case
> the regulator::desc::linear_min_sel is not zero.
>
> Thank you,
> Claud
On Fri, 6 Nov 2020 11:52:58 +0200, Claudiu Beznea wrote:
> This series adds support for ramp delay on mcp16502. It also adds
> some cleanup on mcp16502.
>
> Apart from that patches 1/6 fixes the selector validation in case
> the regulator::desc::linear_min_sel is not zero.
>
> Thank you,
> Claudi
On Wed, 11 Nov 2020 11:06:12 +0200, Claudiu Beznea wrote:
> This series adds support for ramp delay on mcp16502. It also adds
> some cleanup on mcp16502.
>
> Apart from that patches 1/6 fixes the selector validation in case
> the regulator::desc::linear_min_sel is not zero.
>
> Thank you,
> Claud
On 13/11/20 10:34 PM, Nishanth Menon wrote:
> On 21:19-20201113, Sekhar Nori wrote:
>> From: Faiz Abbas
>>
>> Add configs to help enable regulators that supply power to the SD card
>> on TI's J721e platform. These regulators are controlled by either
>>
On Fri, Nov 13, 2020 at 01:53:32PM +0100, Peter Zijlstra wrote:
> Hi
>
> Eugenio reported
> (https://bugzilla.kernel.org/attachment.cgi?id=293659&action=edit):
>
> [ 139.226723] [ cut here ]
> [ 139.226724] WARNING: CPU: 9 PID: 2290 at kernel/rcu/tree.c:932
> __rcu_irq_
On Fri, Nov 13, 2020 at 8:50 AM Lee Jones wrote:
>
> Fixes the following W=1 kernel build warning(s):
>
> drivers/gpu/drm/amd/amdgpu/amdgpu_ib.c:66: warning: Function parameter or
> member 'adev' not described in 'amdgpu_ib_get'
> drivers/gpu/drm/amd/amdgpu/amdgpu_ib.c:66: warning: Function par
On Fri, Nov 13, 2020 at 04:45:52PM +, John Boero wrote:
> Sorry I wanted to include a pastebin or link but was trying to follow maillist
> guidelines and not include links or exceed wrap guidelines. Full contents:
> https://paste.centos.org/view/3746bc40
>
> Yes I understand the return dodges
Hello,
syzbot found the following issue on:
HEAD commit:af5043c8 Merge tag 'acpi-5.10-rc4' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13e8c90650
kernel config: https://syzkaller.appspot.com/x/.config?x=a3f13716fa0212fd
das
Hello,
syzbot found the following issue on:
HEAD commit:af5043c8 Merge tag 'acpi-5.10-rc4' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10f165e650
kernel config: https://syzkaller.appspot.com/x/.config?x=a3f13716fa0212fd
das
On 10/28/20 4:11 AM, Halil Pasic wrote:
On Thu, 22 Oct 2020 13:12:01 -0400
Tony Krowiak wrote:
The APCB is a field within the CRYCB that provides the AP configuration
to a KVM guest. Let's introduce a shadow copy of the KVM guest's APCB and
maintain it for the lifespan of the guest.
Signed
On Fri, Nov 13, 2020 at 8:50 AM Lee Jones wrote:
>
> Fixes the following W=1 kernel build warning(s):
>
> drivers/gpu/drm/amd/amdgpu/amdgpu_pll.c:121: warning: Function parameter or
> member 'freq' not described in 'amdgpu_pll_compute'
> drivers/gpu/drm/amd/amdgpu/amdgpu_pll.c:121: warning: Fun
On Fri, Nov 13, 2020 at 06:25:53AM -0800, Shakeel Butt wrote:
> On Thu, Nov 12, 2020 at 8:02 PM Roman Gushchin wrote:
> >
> > On Thu, Nov 12, 2020 at 07:25:48PM -0800, Alexei Starovoitov wrote:
> > > On Thu, Nov 12, 2020 at 7:18 PM Andrew Morton
> > > wrote:
> > > >
> > > > On Thu, 12 Nov 2020 1
On Fri, Nov 13, 2020 at 8:50 AM Lee Jones wrote:
>
> Fixes the following W=1 kernel build warning(s):
>
> drivers/gpu/drm/amd/amdgpu/amdgpu_sync.c:86: warning: Function parameter or
> member 'f' not described in 'amdgpu_sync_get_owner'
> drivers/gpu/drm/amd/amdgpu/amdgpu_sync.c:86: warning: Exc
Replace all occurences of the usage of int with the new struct
cpu_aggr_id.
No functional changes.
Signed-off-by: James Clark
Cc: Peter Zijlstra
Cc: Ingo Molnar
Cc: Arnaldo Carvalho de Melo
Cc: Mark Rutland
Cc: Alexander Shishkin
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Thomas Richter
Cc: John
Replace usages of perf_cpu_map with cpu_aggr map in
places that are involved with perf stat aggregation.
This will then later be changed to be a map of
cpu_aggr_id rather than an int so that more data can
be stored.
No functional changes.
Signed-off-by: James Clark
Cc: Peter Zijlstra
Cc: Ingo
Break up the previous v2 patchset into smaller atomic commits.
The end result is the same as the previous patchset apart from
some minor refactoring, asserting on an empty header and
calling cpu__setup_cpunode_map() in the topology self test.
Testing done:
Tested --per-core, --per-thread, --per-d
I have talked quite a bit about Fair Pay here, that we need for correct
streaming and OS developlment.
I think a new branch of OpenMandriva would be good. "Star-X".
Philosophically the problem is Tao that is a Fire Lizard, and
Theoprastus, that seems to be about the same, and nonsensical churc
Use the new cpu_aggr_id struct in the cpu map
instead of int so that it can store more data.
No functional changes.
Signed-off-by: James Clark
Cc: Peter Zijlstra
Cc: Ingo Molnar
Cc: Arnaldo Carvalho de Melo
Cc: Mark Rutland
Cc: Alexander Shishkin
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Thomas
Add core as a separate member so that it doesn't have to be
packed into the int value.
Signed-off-by: James Clark
Cc: Ingo Molnar
Cc: Arnaldo Carvalho de Melo
Cc: Mark Rutland
Cc: Alexander Shishkin
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Thomas Richter
Cc: John Garry
---
tools/perf/builtin-s
This is something I wanted to implement a long time ago, but held off until
there was a good reason to do so. Now it appears that having access to the
arguments of the function by default is very useful. As a bonus, because
arguments must be saved regardless before calling a callback, because they
From: "Steven Rostedt (VMware)"
When CONFIG_HAVE_DYNAMIC_FTRACE_WITH_ARGS is available, the ftrace call
will be able to set the ip of the calling function. This will improve the
performance of live kernel patching where it does not need all the regs to
be stored just to change the instruction poi
Add socket as a separate member so that it doesn't have to be
packed into the int value. When the socket ID was larger than
8 bits the output appeared corrupted or incomplete.
For example, here on ThunderX2 perf stat reports a socket
of -1 and an invalid die number:
./perf stat -a --per-die
T
601 - 700 of 1310 matches
Mail list logo
