[Mainline/linux-next-netdev/net-next/scsi]Dlpar remove, drmgr phb and pci remove operations are failing

2024-01-02 Thread Tasmiya Nalatwad
Greetings,  [Mainline/linux-next-netdev/net-next/scsi]Dlpar remove, drmgr phb and pci remove operations are failing command ---> chhwres -r io --rsubtype slot -m "managed system name" -o r --id 6 -l 21030014 output ---> HSCL2929 The dynamic removal of I/O resources failed: The I/O slot dy

Re: [PATCHv3 RESEND 10/10] ASoC: dt-bindings: fsl-asoc-card: add compatible for generic codec

2024-01-02 Thread Elinor Montmasson
Hello, On Wednesday, 20 December, 2023 23:25:50, Rob Herring wrote: > On Mon, Dec 18, 2023 at 01:40:58PM +0100, Elinor Montmasson wrote: > > +Optional, relevant only with the "fsl,imx-audio-generic" compatible: > > + > > + - cpu-slot-width : Indicates a specific TDM slot width in bits. > > + -

Re: [Mainline/linux-next-netdev/net-next/scsi]Dlpar remove, drmgr phb and pci remove operations are failing

2024-01-02 Thread Nathan Lynch
Hi, Tasmiya Nalatwad writes: >  [Mainline/linux-next-netdev/net-next/scsi] What does this mean? Are you reporting this issue against four separate trees? > Dlpar remove, drmgr phb and > pci remove operations are failing > > command ---> chhwres -r io --rsubtype slot -m "managed system name" -

Re: [PATCH v4] powerpc/pseries/vas: Use usleep_range() to support HCALL delay

2024-01-02 Thread Nathan Lynch
"Aneesh Kumar K.V" writes: > Haren Myneni writes: > >> diff --git a/arch/powerpc/platforms/pseries/vas.c >> b/arch/powerpc/platforms/pseries/vas.c >> index 71d52a670d95..5cf81c564d4b 100644 >> --- a/arch/powerpc/platforms/pseries/vas.c >> +++ b/arch/powerpc/platforms/pseries/vas.c >> @@ -38,7 +3

Re: [PATCH 2/3] PCI/AER: Decode Requester ID when no error info found

2024-01-02 Thread Kuppuswamy Sathyanarayanan
On 12/6/2023 2:42 PM, Bjorn Helgaas wrote: > From: Bjorn Helgaas > > When a device with AER detects an error, it logs error information in its > own AER Error Status registers. It may send an Error Message to the Root > Port (RCEC in the case of an RCiEP), which logs the fact that an Error >

Re: [PATCH 1/3] PCI/AER: Use 'Correctable' and 'Uncorrectable' spec terms for errors

2024-01-02 Thread Kuppuswamy Sathyanarayanan
On 12/6/2023 2:42 PM, Bjorn Helgaas wrote: > From: Bjorn Helgaas > > The PCIe spec classifies errors as either "Correctable" or "Uncorrectable". > Previously we printed these as "Corrected" or "Uncorrected". To avoid > confusion, use the same terms as the spec. > > One confusing situation is

[PATCH] crypto:vmx: Move ppc vmx diirectory to arch/powerpc/crypto.

2024-01-02 Thread Danny Tsen
Relocate all crypto files in vmx driver to arch/powerpc/crypto directory and remove vmx directory. drivers/crypto/vmx/aes.c rename to arch/powerpc/crypto/aes.c drivers/crypto/vmx/aes_cbc.c rename to arch/powerpc/crypto/aes_cbc.c drivers/crypto/vmx/aes_ctr.c rename to arch/powerpc/crypto/aes_ctr.c

Re: [PATCH 2/3] PCI/AER: Decode Requester ID when no error info found

2024-01-02 Thread Bjorn Helgaas
On Tue, Jan 02, 2024 at 11:22:53AM -0800, Kuppuswamy Sathyanarayanan wrote: > On 12/6/2023 2:42 PM, Bjorn Helgaas wrote: > > From: Bjorn Helgaas > > > > When a device with AER detects an error, it logs error information in its > > own AER Error Status registers. It may send an Error Message to t