Re: [PATCH v4 7/8] lockdep: Change hardirq{s_enabled,_context} to per-cpu variables

Peter Zijlstra wrote: ... > -#define lockdep_assert_irqs_disabled() do {\ > - WARN_ONCE(debug_locks && !current->lockdep_recursion && \ > - current->hardirqs_enabled,\ > - "IRQs not disabled as

RE: [PATCH v8 3/3] iommu/arm-smmu: Add global/context fault implementation hooks

> Add global/context fault hooks to allow NVIDIA SMMU implementation handle > faults across multiple SMMUs. > > Signed-off-by: Krishna Reddy Reviewed-by: Pritesh Raithatha

Re: [PATCH] kdb: prevent possible null deref in kdb_msg_write

On Mon, 29 Jun 2020 at 21:07, Daniel Thompson wrote: > > On Mon, Jun 29, 2020 at 04:50:20PM +0200, Petr Mladek wrote: > > On Mon 2020-06-29 16:59:24, Cengiz Can wrote: > > > `kdb_msg_write` operates on a global `struct kgdb_io *` called > > > `dbg_io_ops`. > > > > > > Although it is initialized

RE: [PATCH v8 1/3] iommu/arm-smmu: add NVIDIA implementation for dual ARM MMU-500 usage

> NVIDIA's Tegra194 SoC uses two ARM MMU-500s together to interleave IOVA > accesses across them. > Add NVIDIA implementation for dual ARM MMU-500s and add new compatible > string for Tegra194 SoC SMMU topology. > > Signed-off-by: Krishna Reddy Reviewed-by: Pritesh Raithatha

Re: [PATCH 2/2] can: flexcan: add support for ISO CAN-FD

[+ Oliver] Hi Joakim, Am 2020-06-30 04:42, schrieb Joakim Zhang: -Original Message- From: Michael Walle Sent: 2020年6月30日 2:18 To: linux-...@vger.kernel.org; net...@vger.kernel.org; linux-kernel@vger.kernel.org Cc: Wolfgang Grandegger ; Marc Kleine-Budde ; David S . Miller ; Jakub

[PATCH v3 15/20] raid5: Use sequence counter with associated spinlock

A sequence counter write side critical section must be protected by some form of locking to serialize writers. A plain seqcount_t does not contain the information of which lock must be held when entering a write side critical section. Use the new seqcount_spinlock_t data type, which allows to

[PATCH v3 20/20] hrtimer: Use sequence counter with associated raw spinlock

A sequence counter write side critical section must be protected by some form of locking to serialize writers. A plain seqcount_t does not contain the information of which lock must be held when entering a write side critical section. Use the new seqcount_raw_spinlock_t data type, which allows to

[PATCH v3 17/20] NFSv4: Use sequence counter with associated spinlock

A sequence counter write side critical section must be protected by some form of locking to serialize writers. A plain seqcount_t does not contain the information of which lock must be held when entering a write side critical section. Use the new seqcount_spinlock_t data type, which allows to

[PATCH v3 12/20] xfrm: policy: Use sequence counters with associated lock

A sequence counter write side critical section must be protected by some form of locking to serialize writers. If the serialization primitive is not disabling preemption implicitly, preemption has to be explicitly disabled before entering the sequence counter write side critical section. A plain

[PATCH v3 13/20] timekeeping: Use sequence counter with associated raw spinlock

A sequence counter write side critical section must be protected by some form of locking to serialize writers. A plain seqcount_t does not contain the information of which lock must be held when entering a write side critical section. Use the new seqcount_raw_spinlock_t data type, which allows to

[PATCH v3 11/20] netfilter: nft_set_rbtree: Use sequence counter with associated rwlock

A sequence counter write side critical section must be protected by some form of locking to serialize writers. A plain seqcount_t does not contain the information of which lock must be held when entering a write side critical section. Use the new seqcount_rwlock_t data type, which allows to

[PATCH v3 16/20] iocost: Use sequence counter with associated spinlock

A sequence counter write side critical section must be protected by some form of locking to serialize writers. A plain seqcount_t does not contain the information of which lock must be held when entering a write side critical section. Use the new seqcount_spinlock_t data type, which allows to

[PATCH v3 19/20] kvm/eventfd: Use sequence counter with associated spinlock

A sequence counter write side critical section must be protected by some form of locking to serialize writers. A plain seqcount_t does not contain the information of which lock must be held when entering a write side critical section. Use the new seqcount_spinlock_t data type, which allows to

[PATCH v3 18/20] userfaultfd: Use sequence counter with associated spinlock

A sequence counter write side critical section must be protected by some form of locking to serialize writers. A plain seqcount_t does not contain the information of which lock must be held when entering a write side critical section. Use the new seqcount_spinlock_t data type, which allows to

[PATCH v3 14/20] vfs: Use sequence counter with associated spinlock

A sequence counter write side critical section must be protected by some form of locking to serialize writers. A plain seqcount_t does not contain the information of which lock must be held when entering a write side critical section. Use the new seqcount_spinlock_t data type, which allows to

[PATCH v3 07/20] dma-buf: Remove custom seqcount lockdep class key

Commit 3c3b177a9369 ("reservation: add support for read-only access using rcu") introduced a sequence counter to manage updates to reservations. Back then, the reservation object initializer reservation_object_init() was always inlined. Having the sequence counter initialization inlined meant

[PATCH v3 05/20] seqlock: lockdep assert non-preemptibility on seqcount_t write

Preemption must be disabled before entering a sequence count write side critical section. Failing to do so, the seqcount read side can preempt the write side section and spin for the entire scheduler tick. If that reader belongs to a real-time scheduling class, it can spin forever and the kernel

[PATCH v3 09/20] sched: tasks: Use sequence counter with associated spinlock

A sequence counter write side critical section must be protected by some form of locking to serialize writers. A plain seqcount_t does not contain the information of which lock must be held when entering a write side critical section. Use the new seqcount_spinlock_t data type, which allows to

[PATCH v3 10/20] netfilter: conntrack: Use sequence counter with associated spinlock

A sequence counter write side critical section must be protected by some form of locking to serialize writers. A plain seqcount_t does not contain the information of which lock must be held when entering a write side critical section. Use the new seqcount_spinlock_t data type, which allows to

[PATCH v3 01/20] Documentation: locking: Describe seqlock design and usage

Proper documentation for the design and usage of sequence counters and sequential locks does not exist. Complete the seqlock.h documentation as follows: - Divide all documentation on a seqcount_t vs. seqlock_t basis. The description for both mechanisms was intermingled, which is incorrect

[PATCH v3 04/20] lockdep: Add preemption enabled/disabled assertion APIs

Asserting that preemption is enabled or disabled is a critical sanity check. Developers are usually reluctant to add such a check in a fastpath as reading the preemption count can be costly. Extend the lockdep API with macros asserting that preemption is disabled or enabled. If lockdep is

[PATCH v3 08/20] dma-buf: Use sequence counter with associated wound/wait mutex

A sequence counter write side critical section must be protected by some form of locking to serialize writers. If the serialization primitive is not disabling preemption implicitly, preemption has to be explicitly disabled before entering the sequence counter write side critical section. The

[PATCH v3 06/20] seqlock: Extend seqcount API with associated locks

A sequence counter write side critical section must be protected by some form of locking to serialize writers. If the serialization primitive is not disabling preemption implicitly, preemption has to be explicitly disabled before entering the write side critical section. There is no built-in

[PATCH v3 03/20] seqlock: Add missing kernel-doc annotations

A small number of the the exported seqlock.h functions are kernel-doc annotated. Since seqlock.h is now included by the kernel's RST documentation, add kernel-doc annotations for all of the remaining functions. Signed-off-by: Ahmed S. Darwish --- include/linux/seqlock.h | 398

[PATCH v3 00/20] seqlock: Extend seqcount API with associated locks

Hi, This is v3 of the seqlock patch series: [PATCH v1 00/25] seqlock: Extend seqcount API with associated locks https://lore.kernel.org/lkml/20200519214547.352050-1-a.darw...@linutronix.de [PATCH v2 00/18] https://lore.kernel.org/lkml/20200608005729.1874024-1-a.darw...@linutronix.de

[PATCH v3 02/20] seqlock: Properly format kernel-doc code samples

Align the code samples and note sections inside kernel-doc comments with tabs. This way they can be properly parsed and rendered by Sphinx. It also makes the code samples easier to read from text editors. Signed-off-by: Ahmed S. Darwish --- include/linux/seqlock.h | 82

Re: [PATCH v2 10/15] exec: Remove do_execve_file

FYI, this clashes badly with my exec rework. I'd suggest you drop everything touching exec here for now, and I can then add the final file based exec removal to the end of my series.

Re: [PATCH] doc: cgroup: add f2fs and xfs to supported list for writeback

On Mon, Jun 29, 2020 at 02:08:09PM -0500, Eric Sandeen wrote: > f2fs and xfs have both added support for cgroup writeback: > > 578c647 f2fs: implement cgroup writeback support > adfb5fb xfs: implement cgroup aware writeback > > so add them to the supported list in the docs. > > Signed-off-by:

Re: [PATCH v3 1/2] remoteproc: Add remoteproc character device interface

On 6/17/2020 1:44 AM, Arnaud POULIQUEN wrote: On 6/16/20 9:56 PM, risha...@codeaurora.org wrote: On 2020-04-30 01:30, Arnaud POULIQUEN wrote: Hi Rishabh, On 4/21/20 8:10 PM, Rishabh Bhatnagar wrote: Add the character device interface into remoteproc framework. This interface can be used

Re: [EXT] Re: [PATCH 1/2] arm64: dts: ls1088a: add more thermal zone support

On Tue, Jun 30, 2020 at 10:58 AM Andy Tang wrote: > > > > > -Original Message- > > From: Amit Kucheria > > Sent: 2020年6月30日 13:12 > > To: Andy Tang > > Cc: Shawn Guo ; Leo Li ; Rob > > Herring ; lakml ; > > open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS > > ; LKML > >

Re: [PATCH] vhost: Fix documentation

On 2020/6/30 下午1:29, Eli Cohen wrote: Fix documentation to match actual function prototypes "end" used instead of "last". Fix that. Signed-off-by: Eli Cohen --- Acked-by: Jason Wang Thanks drivers/vhost/iotlb.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

Re: [PATCH] ASoC: fsl_asrc: Add an option to select internal ratio mode

On Tue, Jun 30, 2020 at 4:09 AM Nicolin Chen wrote: > > On Mon, Jun 29, 2020 at 09:58:35PM +0800, Shengjiu Wang wrote: > > The ASRC not only supports ideal ratio mode, but also supports > > internal ratio mode. > > > > For internal rato mode, the rate of clock source should be divided > > with no

Re: [PATCH 4.19 000/131] 4.19.131-rc1 review

On Mon, 29 Jun 2020 at 21:05, Sasha Levin wrote: > > > This is the start of the stable review cycle for the 4.19.131 release. > There are 131 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. > >

include/linux/compiler.h:350:38: error: call to '__compiletime_assert_453' declared with attribute error: BUILD_BUG_ON failed: IS_ENABLED(CONFIG_32BIT) && (_PFN_SHIFT > PAGE_SHIFT)

Hi Paul, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 7c30b859a947535f2213277e827d7ac7dcff9c84 commit: 05d013a0366d50f4f0dbebf8c1b22b42020bf49a MIPS: Detect bad _PFN_SHIFT values date: 9 months ago config:

[PATCH] vhost: Fix documentation

Fix documentation to match actual function prototypes "end" used instead of "last". Fix that. Signed-off-by: Eli Cohen --- drivers/vhost/iotlb.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/vhost/iotlb.c b/drivers/vhost/iotlb.c index

RE: [EXT] Re: [PATCH 1/2] arm64: dts: ls1088a: add more thermal zone support

> -Original Message- > From: Amit Kucheria > Sent: 2020年6月30日 13:12 > To: Andy Tang > Cc: Shawn Guo ; Leo Li ; Rob > Herring ; lakml ; > open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS > ; LKML > Subject: [EXT] Re: [PATCH 1/2] arm64: dts: ls1088a: add more thermal zone >

Re: [PATCH] x86/split_lock: Don't write MSR_TEST_CTRL on CPUs that aren't whitelisted

Ping. This would ideally get into 5.8, the bad behavior is quite nasty. On Fri, Jun 05, 2020 at 12:26:05PM -0700, Sean Christopherson wrote: > Choo! Choo! All aboard the Split Lock Express, with direct service to > Wreckage! > > Skip split_lock_verify_msr() if the CPU isn't whitelisted as a

[PATCH v10 09/12] spi: imx: add new i.mx6ul compatible name in binding doc

ERR009165 fixed from i.mx6ul, add its compatible name in binding doc. Signed-off-by: Robin Gong Acked-by: Mark Brown Reviewed-by: Rob Herring --- Documentation/devicetree/bindings/spi/fsl-imx-cspi.txt | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH v10 07/12] spi: imx: fix ERR009165

Change to XCH mode even in dma mode, please refer to the below errata: https://www.nxp.com/docs/en/errata/IMX6DQCE.pdf Signed-off-by: Robin Gong Acked-by: Mark Brown --- drivers/spi/spi-imx.c | 10 +++--- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/drivers/spi/spi-imx.c

[PATCH v10 08/12] spi: imx: remove ERR009165 workaround on i.mx6ul

ERR009165 fixed on i.mx6ul/6ull/6sll. All other i.mx6/7 and i.mx8m/8mm still need this errata. Please refer to nxp official errata document from https://www.nxp.com/ . For removing workaround on those chips. Add new i.mx6ul type. Signed-off-by: Robin Gong Acked-by: Mark Brown ---

[PATCH v10 12/12] dmaengine: imx-sdma: add uart rom script

For the compatibility of NXP internal legacy kernel before 4.19 which is based on uart ram script and upstreaming kernel based on uart rom script, add both uart ram/rom script in latest sdma firmware. By default uart rom script used. Besides, add two multi-fifo scripts for SAI/PDM on i.mx8m/8mm

[PATCH v10 04/12] dmaengine: imx-sdma: remove duplicated sdma_load_context

Since sdma_transfer_init() will do sdma_load_context before any sdma transfer, no need once more in sdma_config_channel(). Signed-off-by: Robin Gong Acked-by: Vinod Koul --- drivers/dma/imx-sdma.c | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/drivers/dma/imx-sdma.c

[PATCH v10 11/12] dma: imx-sdma: add i.mx6ul compatible name

Add i.mx6ul compatible name in binding doc. Signed-off-by: Robin Gong Reviewed-by: Rob Herring --- Documentation/devicetree/bindings/dma/fsl-imx-sdma.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/dma/fsl-imx-sdma.txt

[PATCH v10 05/12] dmaengine: dma: imx-sdma: add fw_loaded and is_ram_script

Add 'fw_loaded' and 'is_ram_script' to check if the script used by channel is ram script and it's loaded or not, so that could prevent meaningless following malloc dma descriptor and bd allocate in sdma_transfer_init(), otherwise memory may be consumed out potentially without free in case that spi

[PATCH v10 06/12] dmaengine: imx-sdma: add mcu_2_ecspi script

Add mcu_2_ecspi script to fix ecspi errata ERR009165. Signed-off-by: Robin Gong Acked-by: Vinod Koul --- drivers/dma/imx-sdma.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/dma/imx-sdma.c b/drivers/dma/imx-sdma.c index ce1c83e..337143f 100644 --- a/drivers/dma/imx-sdma.c +++

[PATCH v10 10/12] dmaengine: imx-sdma: remove ERR009165 on i.mx6ul

ECSPI issue fixed from i.mx6ul at hardware level, no need ERR009165 anymore on those chips such as i.mx8mq. Signed-off-by: Robin Gong Acked-by: Vinod Koul --- drivers/dma/imx-sdma.c | 29 - 1 file changed, 28 insertions(+), 1 deletion(-) diff --git

[PATCH v10 00/12] add ecspi ERR009165 for i.mx6/7 soc family

There is ecspi ERR009165 on i.mx6/7 soc family, which cause FIFO transfer to be send twice in DMA mode. Please get more information from: https://www.nxp.com/docs/en/errata/IMX6DQCE.pdf. The workaround is adding new sdma ram script which works in XCH mode as PIO inside sdma instead of SMC mode,

[PATCH v10 02/12] Revert "ARM: dts: imx6: Use correct SDMA script for SPI cores"

There are two ways for SDMA accessing SPBA devices: one is SDMA->AIPS ->SPBA(masterA port), another is SDMA->SPBA(masterC port). Please refer to the 'Figure 58-1. i.MX 6Dual/6Quad SPBA connectivity' of i.mx6DQ Reference Manual. SDMA provide the corresponding app_2_mcu/mcu_2_app and

[PATCH v10 01/12] Revert "ARM: dts: imx6q: Use correct SDMA script for SPI5 core"

There are two ways for SDMA accessing SPBA devices: one is SDMA->AIPS ->SPBA(masterA port), another is SDMA->SPBA(masterC port). Please refer to the 'Figure 58-1. i.MX 6Dual/6Quad SPBA connectivity' of i.mx6DQ Reference Manual. SDMA provide the corresponding app_2_mcu/mcu_2_app and

[PATCH v10 03/12] Revert "dmaengine: imx-sdma: refine to load context only once"

This reverts commit ad0d92d7ba6aecbe2705907c38ff8d8be4da1e9c, because in spi-imx case, burst length may be changed dynamically. Signed-off-by: Robin Gong Acked-by: Sascha Hauer --- drivers/dma/imx-sdma.c | 8 1 file changed, 8 deletions(-) diff --git a/drivers/dma/imx-sdma.c

Re: [PATCH 5.4 000/178] 5.4.50-rc1 review

On Mon, 29 Jun 2020 at 20:55, Sasha Levin wrote: > > > This is the start of the stable review cycle for the 5.4.50 release. > There are 178 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. > >

Re: input maintainer -- are you there? was Re: [PATCH 1/2] Input: add `SW_MACHINE_COVER`

On Mon, Jun 29, 2020 at 03:36:44PM +0200, Pavel Machek wrote: > Hi! > > > Looks like we're blocking on this input patch. > > > > On 16/06/2020 12:50, Pavel Machek wrote: > > > On Fri 2020-06-12 14:53:58, Merlijn Wajer wrote: > > >> This event code represents the state of a removable cover of a

Re: [PATCH] kernel/trace: Add TRACING_ALLOW_PRINTK config option

On Sun, Jun 28, 2020 at 07:43:34PM -0400, Steven Rostedt wrote: > On Sun, 28 Jun 2020 18:28:42 -0400 > Steven Rostedt wrote: > > > You create a bpf event just like you create any other event. When a bpf > > program that uses a bpf_trace_printk() is loaded, you can enable that > > event from

Re: [PATCH] Input: elan_i2c - only increment wakeup count on touch

On Mon, Jun 29, 2020 at 05:57:07PM -0700, Derek Basehore wrote: > This moves the wakeup increment for elan devices to the touch report. > This prevents the drivers from incorrectly reporting a wakeup when the > resume callback resets then device, which causes an interrupt to > occur. This also

Re: [PATCH 5.7 000/265] 5.7.7-rc1 review

On Mon, 29 Jun 2020 at 20:48, Sasha Levin wrote: > > > This is the start of the stable review cycle for the 5.7.7 release. > There are 265 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. > >

Re: [PATCH 1/2] arm64: dts: ls1088a: add more thermal zone support

On Tue, Jun 30, 2020 at 8:56 AM wrote: > > From: Yuantian Tang > > There are 2 thermal zones in ls1088a soc. Add the other thermal zone > node to enable it. > Also update the values in calibration table to make the temperatures > monitored more precise. > > Signed-off-by: Yuantian Tang > --- >

Re: [PATCH v4 10/23] ASoC: simple-card: Wrong daifmt for CPU end of DPCM DAI link

Hi Sameer > For DPCM links I don't want to flip based on one Codec reference. My > goal was to make the binding work for multiple CPU/Codec link. Hence I > thought it would be better to explicitly describe the 'Master' DAI. We > can eventually get rid of 'codec' argument from >

Re: [PATCH v3 00/15] HWPOISON: soft offline rework

On Wed, Jun 24, 2020 at 03:01:22PM +, nao.horigu...@gmail.com wrote: > I rebased soft-offline rework patchset [1][2] onto the latest mmotm. The > rebasing required some non-trivial changes to adjust, but mainly that was > straightforward. I confirmed that the reported problem doesn't

Re: [PATCH net] xsk: remove cheap_dma optimization

On Mon, Jun 29, 2020 at 05:18:38PM +0200, Daniel Borkmann wrote: > On 6/29/20 5:10 PM, Björn Töpel wrote: >> On 2020-06-29 15:52, Daniel Borkmann wrote: >>> >>> Ok, fair enough, please work with DMA folks to get this properly integrated >>> and >>> restored then. Applied, thanks! >> >> Daniel,

Re: [PATCH v4 4/7] iio: core: move debugfs data on the private iio dev info

On Tue, 2020-06-30 at 07:57 +0300, Alexandru Ardelean wrote: > This change moves all iio_dev debugfs fields to the iio_dev_priv object. > It's not the biggest advantage yet (to the whole thing of > abstractization) > but it's a start. > > The iio_get_debugfs_dentry() function (which is moved in >

[PATCH v4 6/7] iio: core: move iio_dev's buffer_list to the private iio device object

This change moves the 'buffer_list' away from the public IIO device object into the private part. Signed-off-by: Alexandru Ardelean Signed-off-by: Jonathan Cameron --- drivers/iio/industrialio-buffer.c | 38 +++ drivers/iio/industrialio-core.c | 2 +-

[PATCH v4 7/7] iio: core: move event interface on the opaque struct

Same as with other private fields, this moves the event interface reference to the opaque IIO device object, to be invisible to drivers. Signed-off-by: Alexandru Ardelean Signed-off-by: Jonathan Cameron --- drivers/iio/industrialio-core.c | 5 ++- drivers/iio/industrialio-event.c | 68

[PATCH v4 3/7] iio: core: remove padding from private information

There was a recent discussion about this code: https://lore.kernel.org/linux-iio/20200322165317.0b1f0674@archlinux/ This looks like a good time to removed this, since any issues about it should pop-up under testing, because the iio_dev is having a bit of an overhaul and stuff being moved to

[PATCH v4 5/7] iio: core: move channel list & group to private iio device object

This change bit straightforward and simple, since the 'channel_attr_list' & 'chan_attr_group' fields are only used in 'industrialio-core.c'. This change moves to the private IIO device object Signed-off-by: Alexandru Ardelean Signed-off-by: Jonathan Cameron --- drivers/iio/industrialio-core.c

[PATCH v4 4/7] iio: core: move debugfs data on the private iio dev info

This change moves all iio_dev debugfs fields to the iio_dev_priv object. It's not the biggest advantage yet (to the whole thing of abstractization) but it's a start. The iio_get_debugfs_dentry() function (which is moved in industrialio-core.c) needs to also be guarded against the CONFIG_DEBUG_FS

Re: [PATCH] phy: qcom: remove ufs qmp phy driver

Hi Bjorn, On 29-06-20, 12:24, Bjorn Andersson wrote: > On Mon 29 Jun 07:54 PDT 2020, Vinod Koul wrote: > > > UFS QMP phy drivers are duplicate as we are supposed to use common QMP > > phy driver which is working fine on various platforms. So remove the > > unused driver > > > > This describes

[PATCH v4 2/7] iio: core: wrap IIO device into an iio_dev_opaque object

There are plenty of bad designs we want to discourage or not have to review manually usually about accessing private (marked as [INTERN]) fields of 'struct iio_dev'. Sometimes users copy drivers that are not always the best examples. A better idea is to hide those fields into the framework. For

[PATCH v4 1/7] iio: core: remove iio_priv_to_dev() helper

All users of this helper have been updated to not use it. Remove it now, so that we don't need to move it when creating the iio_dev_opaque structure. Signed-off-by: Alexandru Ardelean Signed-off-by: Jonathan Cameron --- include/linux/iio/iio.h | 6 -- 1 file changed, 6 deletions(-) diff

[PATCH v4 0/7] iio: core: wrap IIO device into an iio_dev_opaque object

This change starts to hide some internal fields of the IIO device into the framework. This patchset assumes that all drivers have been addressed with respect to the use of iio_priv_to_dev(), so the first patch in the series (now) is to remove it, so that we don't need to move it. Changelog v3 ->

Re: [PATCH 3/7] iommu/vt-d: Fix PASID devTLB invalidation

On Tue, 30 Jun 2020 03:01:29 + "Tian, Kevin" wrote: > > From: Lu Baolu > > Sent: Thursday, June 25, 2020 3:26 PM > > > > On 2020/6/23 23:43, Jacob Pan wrote: > > > DevTLB flush can be used for both DMA request with and without > > > PASIDs. The former uses PASID#0 (RID2PASID), latter

Re: [PATCH] igb: reinit_locked() should be called with rtnl_lock

> Would you mind adding a fixes tag here? Probably: > > Fixes: 9d5c824399de ("igb: PCI-Express 82575 Gigabit Ethernet driver") That seems to be the commit that introduced the driver in 2.6.25. I am not familiar with the history of the driver to tell if this was a day 1 problem or if it became an

[PATCH v2 4/7] PCI: Add device even if driver attach failed

device_attach() returning failure indicates a driver error while trying to probe the device. In such a scenario, the PCI device should still be added in the system and be visible to the user. This patch partially reverts: commit ab1a187bba5c ("PCI: Check device_attach() return value always")

[PATCH v2 3/7] PCI/ACS: Enable PCI_ACS_TB for untrusted/external-facing devices

When enabling ACS, enable translation blocking for external facing ports and untrusted devices. Signed-off-by: Rajat Jain --- v2: Commit log change drivers/pci/pci.c| 4 drivers/pci/quirks.c | 11 +++ 2 files changed, 15 insertions(+) diff --git a/drivers/pci/pci.c

[PATCH v2 1/7] PCI: Keep the ACS capability offset in device

Currently this is being looked up at a number of places. Read and store it once at bootup so that it can be used by all later. Signed-off-by: Rajat Jain --- v2: Commit log cosmetic changes drivers/pci/p2pdma.c | 2 +- drivers/pci/pci.c| 21 + drivers/pci/pci.h| 2

[PATCH v2 2/7] PCI: Set "untrusted" flag for truly external devices only

The "ExternalFacing" devices (root ports) are still internal devices that sit on the internal system fabric and thus trusted. Currently they were being marked untrusted. This patch uses the platform flag to identify the external facing devices and then use it to mark any downstream devices as

[PATCH v2 7/7] PCI: Add parameter to disable attaching external devices

Introduce a PCI parameter that disables the automatic attachment of external devices to their drivers. This is needed to allow an admin to control which drivers he wants to allow on external ports. For more context, see threads at:

Re: [PATCH 3/7] iommu/vt-d: Fix PASID devTLB invalidation

On Thu, 25 Jun 2020 15:25:57 +0800 Lu Baolu wrote: > On 2020/6/23 23:43, Jacob Pan wrote: > > DevTLB flush can be used for both DMA request with and without > > PASIDs. The former uses PASID#0 (RID2PASID), latter uses non-zero > > PASID for SVA usage. > > > > This patch adds a check for PASID

[PATCH v2 6/7] PCI: Move pci_dev->untrusted logic to use device location instead

The firmware was provinding "ExternalFacing" attribute on PCI root ports, to allow the kernel to mark devices behind it as external. Note that the firmware provides an immutable, read-only property, i.e. the location of the device. The use of (external) device location as hint for (dis)trust, is

[PATCH v2 5/7] driver core: Add device location to "struct device" and expose it in sysfs

Add a new (optional) field to denote the physical location of a device in the system, and expose it in sysfs. This was discussed here: https://lore.kernel.org/linux-acpi/20200618184621.ga446...@kroah.com/ (The primary choice for attribute name i.e. "location" is already exposed as an ABI

[PATCH v2 0/7] Tighten PCI security, expose dev location in sysfs

This is a set of loosely related patches most of whom emerged out of discussion in the following threads. In a nutshell the goal was to allow an administrator to specify which driver he wants to allow on external ports, and a strategy was chalked out:

[PATCH] clk: staging: Specify IOMEM dependency for Xilinx Clocking Wizard driver

The Xilinx Clocking Wizard driver uses the devm_ioremap_resource function, but does not specify a dependency on IOMEM in Kconfig. This causes a build failure on architectures without IOMEM, for example, UML (notably with make allyesconfig). Fix this by making CONFIG_COMMON_CLK_XLNX_CLKWZRD depend

[PATCH net-next] net: dsa: Improve subordinate PHY error message

It is not very informative to know the DSA master device when a subordinate network device fails to get its PHY setup. Provide the device name and capitalize PHY while we are it. Signed-off-by: Florian Fainelli --- net/dsa/slave.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff

RE: [PATCH V2 3/9] clk: imx: Support building SCU clock driver as module

> Subject: RE: [PATCH V2 3/9] clk: imx: Support building SCU clock driver as > module > > > From: Arnd Bergmann > > Sent: Monday, June 29, 2020 4:20 PM > > > > On Mon, Jun 29, 2020 at 9:18 AM Dong Aisheng > > wrote: > > > On Thu, Jun 25, 2020 at 6:43 AM Stephen Boyd > wrote: > > > > Quoting

Re: [PATCH v2 4/4] staging: qlge: replace pr_err with netdev_err

On 2020-06-30 01:43 +0800, Coiby Xu wrote: > On Mon, Jun 29, 2020 at 02:30:04PM +0900, Benjamin Poirier wrote: > > On 2020-06-27 22:58 +0800, Coiby Xu wrote: > > [...] > > > void ql_dump_qdev(struct ql_adapter *qdev) > > > { > > > @@ -1611,99 +1618,100 @@ void ql_dump_qdev(struct ql_adapter

[PATCH 4/7] [elf-fdpic] coredump: don't bother with cyclic list for per-thread objects

From: Al Viro plain single-linked list is just fine here... Signed-off-by: Al Viro --- fs/binfmt_elf_fdpic.c | 29 +++-- 1 file changed, 11 insertions(+), 18 deletions(-) diff --git a/fs/binfmt_elf_fdpic.c b/fs/binfmt_elf_fdpic.c index a6ee92137529..bcbf756fba39

[PATCH 5/7] [elf-fdpic] move allocation of elf_thread_status into elf_dump_thread_status()

From: Al Viro Signed-off-by: Al Viro --- fs/binfmt_elf_fdpic.c | 24 ++-- 1 file changed, 10 insertions(+), 14 deletions(-) diff --git a/fs/binfmt_elf_fdpic.c b/fs/binfmt_elf_fdpic.c index bcbf756fba39..ba4f264dff3a 100644 --- a/fs/binfmt_elf_fdpic.c +++

[PATCH 3/7] kill elf_fpxregs_t

From: Al Viro all uses are conditional upon ELF_CORE_COPY_XFPREGS, which has not been defined on any architecture since 2010 Signed-off-by: Al Viro --- arch/ia64/include/asm/elf.h| 2 -- arch/powerpc/include/asm/elf.h | 2 -- arch/x86/include/asm/elf.h | 2 -- fs/binfmt_elf.c

[PATCH 7/7] [elf-fdpic] switch coredump to regsets

From: Al Viro similar to how elf coredump is working on architectures that have regsets, and all architectures with elf-fdpic support *do* have that. Signed-off-by: Al Viro --- fs/binfmt_elf_fdpic.c | 23 ++- 1 file changed, 18 insertions(+), 5 deletions(-) diff --git

[PATCH 6/7] [elf-fdpic] use elf_dump_thread_status() for the dumper thread as well

From: Al Viro the only reason to have it open-coded for the first (dumper) thread is that coredump has a couple of process-wide notes stuck right after the first (NT_PRSTATUS) note of the first thread. But we don't need to make the data collection side irregular for the first thread to handle

[PATCH 1/7] unexport linux/elfcore.h

From: Al Viro It's unusable from userland - it uses elf_gregset_t, which is not provided by exported headers. glibc has it in sys/procfs.h, but the same file defines struct elf_prstatus, so linux/elfcore.h can't be included once sys/procfs.h has been pulled. Same goes for uclibc and dietlibc

[PATCH 2/7] take fdpic-related parts of elf_prstatus out

From: Al Viro The only architecture where we might end up using both is arm, and there we definitely don't want fdpic-related fields in elf_prstatus - coredump layout of ELF binaries should not depend upon having the kernel built with the support of ELF_FDPIC ones. Just move the fdpic-modified

[RFC][PATCHES] converting FDPIC coredumps to regsets

Conversion of ELF coredumps to regsets has not touched ELF_FDPIC. Right now all architectures that support FDPIC have regsets sufficient for switching it to regset-based coredumps. A bit of backstory: original ELF (and ELF_FDPIC) coredumps reused the old helpers used by a.out coredumps.

[PATCH] clk: Specify IOMEM dependency for HSDK pll driver

The HSDK pll driver uses the devm_ioremap_resource function, but does not specify a dependency on IOMEM in Kconfig. This causes a build failure on architectures without IOMEM, for example, UML (notably with make allyesconfig). Fix this by making CONFIG_CLK_HSDK depend on CONFIG_IOMEM.

Re: [PATCH v4 11/23] ASoC: simple-card: Loop over all children for 'mclk-fs'

On 6/30/2020 7:38 AM, Kuninori Morimoto wrote: External email: Use caution opening links or attachments Hi Sameer snprintf(prop, sizeof(prop), "%smclk-fs", prefix); of_property_read_u32(node, prop, >mclk_fs); of_property_read_u32(cpu, prop, >mclk_fs); -

Re: [PATCH v4 bpf-next 2/4] bpf: introduce helper bpf_get_task_stack()

On Sun, Jun 28, 2020 at 10:58 PM Song Liu wrote: > > Introduce helper bpf_get_task_stack(), which dumps stack trace of given > task. This is different to bpf_get_stack(), which gets stack track of > current task. One potential use case of bpf_get_task_stack() is to call > it from bpf_iter__task

Re: [PATCH v3 2/7] iio: core: wrap IIO device into an iio_dev_opaque object

On Sat, 2020-06-27 at 17:40 +0100, Jonathan Cameron wrote: > On Sun, 21 Jun 2020 15:33:40 +0300 > Alexandru Ardelean wrote: > > > There are plenty of bad designs we want to discourage or not have to > > review > > manually usually about accessing private (marked as [INTERN]) fields of > >

Re: [PATCH 1/1] crypto: ux500: hash: Add namespacing to hash_init()

On Mon, Jun 29, 2020 at 01:30:03PM +0100, Lee Jones wrote: > A recent change to the Regulator consumer API (which this driver > utilises) add prototypes for the some suspend functions. These > functions require including header file include/linux/suspend.h. > > The following tree of includes

Re: [PATCH V3 04/10] clk: imx: Support building SCU clock driver as module

On Tue, Jun 30, 2020 at 5:16 AM Anson Huang wrote: > > Hi, Arnd > > > > Subject: Re: [PATCH V3 04/10] clk: imx: Support building SCU clock driver as > > module > > > > On Mon, Jun 29, 2020 at 4:52 PM Anson Huang > > wrote: > > > > Subject: Re: [PATCH V3 04/10] clk: imx: Support building SCU

Re: [PATCH v4 12/23] ASoC: simple-card: Support DPCM DAI link with multiple Codecs

On 6/30/2020 6:54 AM, Kuninori Morimoto wrote: External email: Use caution opening links or attachments Hi Sameer Maybe base issue for multiple codec support is that simple_for_each_link() is caring first codec only ? (snip) Ideally I wanted to remove above two lines and allow empty

Re: [PATCH v5 3/3] mm/page_alloc: Keep memoryless cpuless node 0 offline

* Christopher Lameter [2020-06-29 14:58:40]: > On Wed, 24 Jun 2020, Srikar Dronamraju wrote: > > > Currently Linux kernel with CONFIG_NUMA on a system with multiple > > possible nodes, marks node 0 as online at boot. However in practice, > > there are systems which have node 0 as memoryless

  1   2   3   4   5   6   7   8   9   10   >