Il 03/10/23 18:43, Rob Herring ha scritto:
The DT of_device.h and of_platform.h date back to the separate
of_platform_bus_type before it was merged into the regular platform bus.
As part of that merge prepping Arm DT support 13 years ago, they
"temporarily" include each other. They also include p
On Tue, Oct 03, 2023 at 11:43:07AM -0500, Rob Herring wrote:
> The DT of_device.h and of_platform.h date back to the separate
> of_platform_bus_type before it was merged into the regular platform bus.
> As part of that merge prepping Arm DT support 13 years ago, they
> "temporarily" include each ot
On Tue, Oct 03, 2023 at 11:43:08AM -0500, Rob Herring wrote:
> If probe is reached, we've already matched the device and in the case of
> DT matching, the struct device_node pointer will be set. Therefore, there
> is no need to call of_match_device() in probe.
>
> Signed-off-by: Rob Herring
> ---
On 03/10/23 19:12, Peter Bergner wrote:
> On 10/3/23 9:08 AM, Adhemerval Zanella Netto wrote:
>> What it is not clear to me is what kind of ABI boundary you are trying to
>> preemptively add support here. The TCB ABI for __builtin_cpu_supports is
>> userland only, so if your intention is just to
On Thu, Sep 14, 2023 at 06:58:03PM +, Sohil Mehta wrote:
> commit c35559f94ebc ("x86/shstk: Introduce map_shadow_stack syscall")
> recently added support for map_shadow_stack() but it is limited to x86
> only for now. There is a possibility that other architectures (namely,
> arm64 and RISC-V),
The pm_runtime_enable will increase power disable depth. Thus
a pairing decrement is needed on the error handling path to
keep it balanced according to context. We fix it by calling
pm_runtime_disable when error returns.
Signed-off-by: Zhang Shurong
---
sound/soc/fsl/fsl_easrc.c | 8 ++--
1
Greetings,
[linux-next] [6.6.0-rc3-next-20230929] [git bisect ->
2ad56efa80dba89162106c06ebc00b611325e584]WARNING: CPU: 0 PID: 8 at
arch/powerpc/kernel/iommu.c:407 __iommu_free+0x1e4/0x1f0
--- Traces ---
[ 62.578338] WARNING: CPU: 0 PID: 8 at arch/powerpc/kernel/iommu.c:407
__iommu_free+0
Greetings,
[linux-next] [6.6.0-rc3-next-20230929] [git bisect ->
2ad56efa80dba89162106c06ebc00b611325e584]WARNING: CPU: 0 PID: 8 at
arch/powerpc/kernel/iommu.c:407 __iommu_free+0x1e4/0x1f0
--- Traces ---
[ 62.578338] WARNING: CPU: 0 PID: 8 at arch/powerpc/kernel/iommu.c:407
__iommu_free+0
Greetings,
[linux-next] [6.6.0-rc3-next-20230929] [git bisect ->
2ad56efa80dba89162106c06ebc00b611325e584]WARNING: CPU: 0 PID: 8 at
arch/powerpc/kernel/iommu.c:407 __iommu_free+0x1e4/0x1f0
--- Traces ---
[ 62.578338] WARNING: CPU: 0 PID: 8 at arch/powerpc/kernel/iommu.c:407
__iommu_free+0
Greetings,
[linux-next] [6.6.0-rc3-next-20230929] [git bisect ->
2ad56efa80dba89162106c06ebc00b611325e584]WARNING: CPU: 0 PID: 8 at
arch/powerpc/kernel/iommu.c:407__iommu_free+0x1e4/0x1f0
--- Traces ---
[ 62.578338] WARNING: CPU: 0 PID: 8 at
arch/powerpc/kernel/iommu.c:407__iommu_free+0x1
On Wed, Oct 04, 2023 at 04:37:10PM +0530, Tasmiya Nalatwad wrote:
>Greetings,
>
>[linux-next] [6.6.0-rc3-next-20230929] [git bisect ->
>2ad56efa80dba89162106c06ebc00b611325e584]WARNING: CPU: 0 PID: 8 at
>arch/powerpc/kernel/[1]iommu.c:407 __iommu_free+0x1e4/0x1f0
>gitbisect i
Michael Ellerman writes:
> On October 4, 2023 3:05:48 AM GMT+11:00, Jonathan Corbet
> wrote:
>>Costa Shulyupin writes:
>>
>>> and fix all in-tree references.
>>>
>>> Architecture-specific documentation is being moved into Documentation/arch/
>>> as a way of cleaning up the top-level documentat
Thanks Jason. Yes the suggested changes works and Warnings are not seen.
On 10/4/23 17:08, Jason Gunthorpe wrote:
On Wed, Oct 04, 2023 at 04:37:10PM +0530, Tasmiya Nalatwad wrote:
Greetings,
[linux-next] [6.6.0-rc3-next-20230929] [git bisect ->
2ad56efa80dba89162106c06ebc00b611325e
On Fri, Sep 15, 2023 at 02:43:05PM -0400, Frank Li wrote:
> ls1021a add suspend/resume support.
>
> Signed-off-by: Frank Li
> ---
ping
Frank
> drivers/pci/controller/dwc/pci-layerscape.c | 88 -
> 1 file changed, 87 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/pc
On Tue, 2023-10-03 at 17:29 -0700, Rick Edgecombe wrote:
> It seems a bit weird to copy all of this. Is it trying to be faster
> or
> something?
>
> Couldn't it just check r->start in execmem_text/data_alloc() path and
> switch to EXECMEM_DEFAULT if needed then? The execmem_range_is_data()
> part
(trimmed the recipient list due to bounces on v1)
This is a series is part of ongoing clean-ups related to device
matching and DT related implicit includes. Essentially of_device.h has
a bunch of implicit includes and generally isn't needed any nore except
for of_match_device(). As we also gene
If probe is reached, we've already matched the device and in the case of
DT matching, the struct device_node pointer will be set. Therefore, there
is no need to call of_match_device() in probe.
Acked-by: Charles Keepax
Signed-off-by: Rob Herring
---
sound/soc/codecs/ak5386.c | 7 ++-
soun
'struct lpass_variant' is used for driver match data which is supposed to
be constant. It's not modified anywhere, so it's just a matter of adding
'const' everywhere.
Signed-off-by: Rob Herring
---
sound/soc/qcom/lpass-apq8016.c | 6 +++---
sound/soc/qcom/lpass-cdc-dma.c | 2 +-
sound/soc/qc
Use preferred device_get_match_data() instead of of_match_device() to
get the driver match data. With this, adjust the includes to explicitly
include the correct headers.
Signed-off-by: Rob Herring
---
sound/soc/intel/keembay/kmb_platform.c | 13 +
sound/soc/qcom/lpass-cpu.c
The DT of_device.h and of_platform.h date back to the separate
of_platform_bus_type before it was merged into the regular platform bus.
As part of that merge prepping Arm DT support 13 years ago, they
"temporarily" include each other. They also include platform_device.h
and of.h. As a result, there
Use preferred i2c_get_match_data() instead of of_match_device() and
i2c_match_id() to get the driver match data. With this, adjust the
includes to explicitly include the correct headers.
Avoid using 0 for enum da7218_dev_id so that no match data can be
distinguished.
Signed-off-by: Rob Herring
-
On Wed, Oct 04, 2023 at 10:58:05AM -0500, Rob Herring wrote:
> The DT of_device.h and of_platform.h date back to the separate
> of_platform_bus_type before it was merged into the regular platform bus.
> As part of that merge prepping Arm DT support 13 years ago, they
> "temporarily" include each ot
Convert to using the new inode timestamp accessor functions.
Signed-off-by: Jeff Layton
---
arch/powerpc/platforms/cell/spufs/inode.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/powerpc/platforms/cell/spufs/inode.c
b/arch/powerpc/platforms/cell/spufs/inode.c
index 3
From: Greg Joyce
Allow for permanent SED authentication keys by
reading/writing to the SED Opal non-volatile keystore.
Signed-off-by: Greg Joyce
Reviewed-by: Jonathan Derrick
---
block/sed-opal.c | 18 --
1 file changed, 16 insertions(+), 2 deletions(-)
diff --git a/block/sed
From: Greg Joyce
Define operations for SED Opal to read/write keys
from POWER LPAR Platform KeyStore(PLPKS). This allows
non-volatile storage of SED Opal keys.
Signed-off-by: Greg Joyce
Reviewed-by: Jonathan Derrick
---
arch/powerpc/platforms/pseries/Kconfig| 6 +
arch/powerpc/platf
From: Greg Joyce
Add read and write functions that allow SED Opal keys to stored
in a permanent keystore.
Signed-off-by: Greg Joyce
Reviewed-by: Jonathan Derrick
---
include/linux/sed-opal-key.h | 26 ++
1 file changed, 26 insertions(+)
create mode 100644 include/linu
From: Greg Joyce
This patchset has gone through numerous rounds of review and
all comments/suggetions have been addressed. The reviews have
covered all relevant areas including reviews by block and keyring
developers as well as the SED Opal maintainer.
TCG SED Opal is a specification from The Tr
On Wed, Oct 4, 2023 at 12:39 PM Mark Brown wrote:
>
> On Wed, Oct 04, 2023 at 10:58:05AM -0500, Rob Herring wrote:
> > The DT of_device.h and of_platform.h date back to the separate
> > of_platform_bus_type before it was merged into the regular platform bus.
> > As part of that merge prepping Arm
On 04.10.2023 18:58, Rob Herring wrote:
> The DT of_device.h and of_platform.h date back to the separate
> of_platform_bus_type before it was merged into the regular platform bus.
> As part of that merge prepping Arm DT support 13 years ago, they
> "temporarily" include each other. They also inc
v2:
- bugfix in mtime handling
- incorporate _sec and _nsec accessor functions (Chuck Lever)
- move i_generation to plug hole after changing timestamps (Amir Goldstein)
While working on the multigrain timestamp changes, Linus suggested
adding some similar wrappers for accessing the atime and mtime
Recently, we converted the ctime accesses in the kernel to use new
accessor functions. Linus recently pointed out though that if we add
accessors for the atime and mtime, then that would allow us to
seamlessly change how these timestamps are stored in the inode.
Add new accessor functions for the
Convert the core vfs code to use the new timestamp accessor functions.
Signed-off-by: Jeff Layton
---
fs/attr.c| 4 ++--
fs/bad_inode.c | 2 +-
fs/binfmt_misc.c | 2 +-
fs/inode.c | 35 +--
fs/nsfs.c| 2 +-
fs/pipe.c| 2 +-
fs/
Rename these two fields to discourage direct access (and to help ensure
that we mop up any leftover direct accesses).
Signed-off-by: Jeff Layton
---
include/linux/fs.h | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/include/linux/fs.h b/include/linux/fs
This shaves 8 bytes off struct inode with a garden-variety Fedora
Kconfig.
Signed-off-by: Jeff Layton
---
include/linux/fs.h | 53 ++
1 file changed, 30 insertions(+), 23 deletions(-)
diff --git a/include/linux/fs.h b/include/linux/fs.h
index 84fdaf39
The recent change to use discrete integers instead of struct timespec64
shaved 8 bytes off of struct inode, but it also moves the i_lock
into the previous cacheline, away from the fields that it protects.
Move i_generation above the i_lock, which moves the new 4 byte hole to
just after the i_fsnot
On Thu, Sep 28, 2023 at 9:11 PM Athira Rajeev
wrote:
>
> Running shellcheck on tests/shell/test_arm_coresight.sh
> throws below warnings:
>
> In tests/shell/test_arm_coresight.sh line 15:
> cs_etm_path=$(find /sys/bus/event_source/devices/cs_etm/ -name cpu*
> -print -quit)
>
On Thu, Sep 28, 2023 at 9:11 PM Athira Rajeev
wrote:
>
> Running shellcheck on record_sideband.sh throws below
> warning:
>
> In tests/shell/record_sideband.sh line 25:
> if ! perf record -o ${perfdata} -BN --no-bpf-event -C $1 true 2>&1
> >/dev/null
> ^--^ SC2069: T
On Wed, Oct 04, 2023 at 03:39:26PM +, Edgecombe, Rick P wrote:
> On Tue, 2023-10-03 at 17:29 -0700, Rick Edgecombe wrote:
> > It seems a bit weird to copy all of this. Is it trying to be faster
> > or
> > something?
> >
> > Couldn't it just check r->start in execmem_text/data_alloc() path and
On Wed, Oct 04, 2023 at 12:29:36AM +, Edgecombe, Rick P wrote:
> On Mon, 2023-09-18 at 10:29 +0300, Mike Rapoport wrote:
> > diff --git a/arch/x86/kernel/module.c b/arch/x86/kernel/module.c
> > index 5f71a0cf4399..9d37375e2f05 100644
> > --- a/arch/x86/kernel/module.c
> > +++ b/arch/x86/kernel/
39 matches
Mail list logo
