On Thu, 2023-12-07 at 15:30 +0100, Jan Beulich wrote: > On 24.11.2023 11:30, Oleksii Kurochko wrote: > > Bobby Eshleman (1): > > xen/riscv: introduce asm/atomic.h > > > > Oleksii Kurochko (38): > > xen/riscv: disable unnecessary configs > > xen/riscv: use some asm-generic headers > > xen/riscv:introduce asm/byteorder.h > > xen/riscv: add public arch-riscv.h > > xen/riscv: introduce spinlock.h > > xen/riscv: introduce fence.h > > xen/riscv: introduce arch-riscv/hvm/save.h > > xen/riscv: introduce asm/cpufeature.h > > xen/riscv: introduce asm/guest_atomics.h > > xen/riscv: introduce asm/iommu.h > > xen/riscv: introduce asm/nospec.h > > xen/riscv: introduce asm/setup.h > > xen/riscv: introduce asm/system.h > > xen/riscv: introduce bitops.h > > xen/riscv: introduce flushtlb.h > > xen/riscv: introduce asm/smp.h > > xen/riscv: introduce cmpxchg.h > > xen/riscv: introduce asm/io.h > > xen/riscv: define bug frame tables in xen.lds.S > > xen/riscv: introduce bit operations > > xen/riscv: introduce asm/domain.h > > xen/riscv: introduce asm/guest_access.h > > xen/riscv: introduce asm/irq.h > > xen/riscv: introduce asm/p2m.h > > xen/riscv: introduce asm/regs.h > > xen/riscv: introduce asm/time.h > > xen/riscv: introduce asm/event.h > > Throughout here, would you please try to be consistent about (not) > using asm/ > prefixes? Sure. I'll skip asm, there is no any sense to use it as it is mentioned xen/riscv...
~ Oleksii
