[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <mhng-768a8522-6d57-4b78-81ff-fea1ecceca5f@palmer-si-x1c4>
Date: Tue, 14 Nov 2017 11:27:36 -0800 (PST)
From: Palmer Dabbelt <palmer@...belt.com>
To: will.deacon@....com
CC: Linus Torvalds <torvalds@...ux-foundation.org>,
linux-kernel@...r.kernel.org, patches@...ups.riscv.org,
Arnd Bergmann <arnd@...db.de>, Olof Johansson <olof@...om.net>,
peterz@...radead.org
Subject: Re: [GIT PULL] RISC-V Port for Linux 4.15 v9
On Tue, 14 Nov 2017 11:23:08 PST (-0800), will.deacon@....com wrote:
> Hi Palmer,
>
> On Mon, Nov 13, 2017 at 01:56:22PM -0800, Palmer Dabbelt wrote:
>> The following changes since commit bebc6082da0a9f5d47a1ea2edc099bf671058bd4:
>>
>> Linux 4.14 (2017-11-12 10:46:13 -0800)
>>
>> are available in the git repository at:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/palmer/linux.git tags/riscv-for-linus-4.15-arch-v9
>>
>> for you to fetch changes up to 512d88db5ef3de56f392f761657c2ab2cadc0498:
>>
>> Merge tag 'v4.14' into for-linus (2017-11-13 13:17:51 -0800)
>
> [...]
>
>> RISC-V: Atomic and Locking Code
>
> I had some open comments on this patch:
>
> http://lkml.kernel.org/r/20171024141032.GD13445@arm.com
>
> Amongst other things, you're adding a spin_unlock_wait and I think your
> test bitops are missing barriers.
>
> I'm not suggesting this holds up the merge, but a reply would've been
> nice :/
Sorry about that, it must have gotten buried in my inbox somewhere. We have a
patch already to remove spin_unlock_wait, it's just not in this because it
didn't get any comments.
I'll look through the rest of your comments.
> Will
Powered by blists - more mailing lists