Re: [PATCH 1/1] futex: remove duplicated code and fix UB

2017-06-26 Thread Jiri Slaby
On 06/23/2017, 09:51 AM, Thomas Gleixner wrote: > On Wed, 21 Jun 2017, Jiri Slaby wrote: >> diff --git a/arch/arm64/include/asm/futex.h b/arch/arm64/include/asm/futex.h >> index f32b42e8725d..5bb2fd4674e7 100644 >> --- a/arch/arm64/include/asm/futex.h >> +++ b/arch/arm64/include/asm/futex.h >> @@

Re: [PATCH 1/1] futex: remove duplicated code and fix UB

2017-06-26 Thread Will Deacon
On Mon, Jun 26, 2017 at 02:02:31PM +0200, Jiri Slaby wrote: > On 06/23/2017, 09:51 AM, Thomas Gleixner wrote: > > On Wed, 21 Jun 2017, Jiri Slaby wrote: > >> diff --git a/arch/arm64/include/asm/futex.h > >> b/arch/arm64/include/asm/futex.h > >> index f32b42e8725d..5bb2fd4674e7 100644 > >> ---

Re: [PATCH 3/3 v6] ARC: hsdk: initial port for HSDK board

2017-06-26 Thread Rob Herring
On Mon, Jun 26, 2017 at 10:11 AM, Eugeniy Paltsev wrote: > From: Alexey Brodkin > > This initial port adds support of ARC HS Development Kit board with some > basic features such serial port, USB, SD/MMC and Ethernet. > > Essentially we run

[PATCH 1/3 v6] ARC: Set IO-coherency aperture base to LINUX_LINK_BASE

2017-06-26 Thread Eugeniy Paltsev
Most of the time we indeed use the one and only LINUX_LINK_BASE set to 0x8000_. But there might be good reasons to move the kernel to another location like 0x9z etc. And we want IOC aperture to cover entire area used by the kernel, so let's make its base matching link base and add required

[PATCH 0/3 v6] hsdk: initial port for HSDK board

2017-06-26 Thread Eugeniy Paltsev
This series introduces some required preparations and initial port of ARC HS Development Kit board with some basic features such as serial port, USB, SD/MMC and Ethernet. Essentially we run Linux kernel on all 4 cores (i.e. utilize SMP) and heavily use IO Coherency for speeding-up DMA-aware

[PATCH 2/3 v6] ARC: Decouple linux kernel memory address and link address

2017-06-26 Thread Eugeniy Paltsev
We faced with problem when we tried to utilize 1G DRAM by linux on HSDK. We can't use our usual kernel memory address (0x8000) like on AXS103 because of DCCM memory bank located at exactly same address (0x8000) But we can't simply move kernel memory address to another address (like

Re: [PATCH 3/3 v6] ARC: hsdk: initial port for HSDK board

2017-06-26 Thread Alexey Brodkin
Hi Rob, On Mon, 2017-06-26 at 10:51 -0500, Rob Herring wrote: > On Mon, Jun 26, 2017 at 10:11 AM, Eugeniy Paltsev > wrote: > > > > From: Alexey Brodkin > > [snip] > > + > > +   chosen { > > +   bootargs =

Re: [PATCH] pci: Add and use PCI_GENERIC_SETUP Kconfig entry

2017-06-26 Thread Palmer Dabbelt
rop us a note to >> help improve the system] >> >> url: >> https://github.com/0day-ci/linux/commits/Palmer-Dabbelt/pci-Add-and-use-PCI_GENERIC_SETUP-Kconfig-entry/20170626-043558 >> config: m68k-allnoconfig (attached as .config) >> compile

[PATCH] pci: Add and use PCI_GENERIC_SETUP Kconfig entry

2017-06-26 Thread Palmer Dabbelt
We wanted to add RISC-V to the list of architectures that used the generic PCI setup-irq.o inside the Makefile and it was suggested that instead we define a Kconfig entry and use that. I've done very minimal testing on this: I just checked to see that an aarch64 defconfig still build setup-irq.o

stdout-path (was Re: [PATCH 3/3 v6] ARC: hsdk: initial port for HSDK board)

2017-06-26 Thread Vineet Gupta
On 06/26/2017 07:25 PM, Alexey Brodkin wrote: + + chosen { + bootargs = "earlycon=uart8250,mmio32,0xf0005000,115200n8 console=ttyS0,115200n8 debug print-fatal-signals=1"; Use stdout-path for the console. Really, the bootargs should be blank and populated by the bootloader