From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 16635C433E0 for ; Wed, 3 Jun 2020 01:46:18 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D7F58206E9 for ; Wed, 3 Jun 2020 01:46:17 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="U3MGenIC" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728234AbgFCBqR (ORCPT ); Tue, 2 Jun 2020 21:46:17 -0400 Received: from us-smtp-delivery-1.mimecast.com ([205.139.110.120]:47032 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726894AbgFCBqQ (ORCPT ); Tue, 2 Jun 2020 21:46:16 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1591148775; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=c2MAXgliaplJ68nQU8H/dBTpmxbn3DqQ8QfGl6JNyrU=; b=U3MGenICjdqf8t+hS3WB9Y5/3hjHVRU87LyLJegOggfkcuHxKTd9r6YTAlSACSyLqLLCbh fP3pOsHVFFM/tcxGs8qbanlvXq60Xa2IdHnSwGz4ffik+i1f6Ilf0BYCghQ4BmlppUvtUE 3NwdTk5ueRpCot2ZvwgAsaSTbq4pNaQ= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-42-mcGd2caDOxmIAJbXRh-kxw-1; Tue, 02 Jun 2020 21:46:13 -0400 X-MC-Unique: mcGd2caDOxmIAJbXRh-kxw-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id C3192800053; Wed, 3 Jun 2020 01:46:11 +0000 (UTC) Received: from localhost (unknown [10.10.110.14]) by smtp.corp.redhat.com (Postfix) with ESMTP id A6E2360BEC; Wed, 3 Jun 2020 01:46:09 +0000 (UTC) Date: Tue, 02 Jun 2020 18:46:08 -0700 (PDT) Message-Id: <20200602.184608.797176631158669285.davem@redhat.com> To: will@kernel.org Cc: linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org, peterz@infradead.org, linux@roeck-us.net, rppt@kernel.org, kernel-team@android.com Subject: Re: [PATCH 0/3] sparc32 SRMMU fixes for SMP From: David Miller In-Reply-To: <20200526173302.377-1-will@kernel.org> References: <20200526173302.377-1-will@kernel.org> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Will Deacon Date: Tue, 26 May 2020 18:32:59 +0100 > Hi folks, > > Enabling SMP for sparc32 uncovered some issues in the SRMMU page-table > allocation code. One of these was introduced by me, but the other two > seem to have been there a while and are probably just exposed more > easily by my recent changes. > > Tested on QEMU. I'm assuming these will go via David's tree. Series applied, thanks Will.