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=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,FROM_LOCAL_NOVOWEL, HEADER_FROM_DIFFERENT_DOMAINS,HK_RANDOM_FROM,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED 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 59A8EC3A5A0 for ; Mon, 19 Aug 2019 17:06:50 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 2E09C22CEA for ; Mon, 19 Aug 2019 17:06:50 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="BExNnfSw" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728050AbfHSRGp (ORCPT ); Mon, 19 Aug 2019 13:06:45 -0400 Received: from mail-yb1-f195.google.com ([209.85.219.195]:37379 "EHLO mail-yb1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727937AbfHSRGn (ORCPT ); Mon, 19 Aug 2019 13:06:43 -0400 Received: by mail-yb1-f195.google.com with SMTP id t5so669850ybt.4; Mon, 19 Aug 2019 10:06:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=csGSFDEdSWqw3dz2PgL0VnXwJ2fZOjcWs1UiwIbpOh8=; b=BExNnfSwIIIYOd2fPFOYG/vCFL2tOZqPG9oCAekHhn6/qBPnYcBCfFYgHijbOFgSIV 3DGpD6Gy4Yxe5tJ0y7ZDtPSbwdLfyXB8xV8HKV3QZokspTWK+H60PPr6tNBa71zjvjEq rDkPhzkM4GFacH7LMMWGfYsPXnbNLm8sYSaEGxEVpju8hAy7aMBTE3SSceq9PIT7WuWh sTzuvvnJCkLo1WwK+2CpqagEBM4t3E1OIt3MnqcTZn83/B1PR4Re9UMl/PdTgYf/ZlH4 UzWl4h+JNq8bi9ol4GaYY7DF3EHEeft6IC54G7JgHD9K3vmdEpTW1LySlpoqUoXgI+qN Gn9A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=csGSFDEdSWqw3dz2PgL0VnXwJ2fZOjcWs1UiwIbpOh8=; b=sHU7cJs4W01jLZ0Vqdu7E06NeiO0018UAP+x1maSxwZPnYo8v+j1bHsVnBueq63jyF gJpnW+v/hlFq4tdWPvkET6pmFWM8NzP0TbeUbY05BPP3ZLwKh3S7MmGMc7JvkmayQbBA rPj8oDYQrTU0q1ierW1KEeC2o9b2zU7qjdjuH0JRccE+vL+LAK258JlYgPneI1hXyKTF MuTolEkTkZJ8qRhKcRktGN0trtVzJfqvv2/KqTdbSGc2wnLAUpMZMF1vOpb0yInaQg1W w7CUjHlc3awr1pYo1JaA6jnno3/vVq1X/2r+deSDT1fTk59O0wmRLzoaWd4LoSArnnxS Zr8w== X-Gm-Message-State: APjAAAXXGecFJDHpXfeFkbu1HaljbJvRLiI7e1cS1PbO4RmaBp1FRATm D9+htx5EjTHSfczWdcKSgaRWeC/YFD+KLlPJMRQ= X-Google-Smtp-Source: APXvYqwQA66V3JZQ8sRo/iPqtTGs+feQWRX34c7uh9WJv+pUv2pSCy/Tkk/vsf3jr7t3twT4WPViCaVg1rYVma41ndA= X-Received: by 2002:a25:ed0e:: with SMTP id k14mr17889604ybh.286.1566234402617; Mon, 19 Aug 2019 10:06:42 -0700 (PDT) MIME-Version: 1.0 References: <20190806213749.20689-1-sashal@kernel.org> <35579e00d27344b853cafea0b29b13c5aaf9e1fc.camel@codethink.co.uk> In-Reply-To: <35579e00d27344b853cafea0b29b13c5aaf9e1fc.camel@codethink.co.uk> From: Max Filippov Date: Mon, 19 Aug 2019 10:06:32 -0700 Message-ID: Subject: Re: [PATCH AUTOSEL 4.4 01/14] xtensa: fix build for cores with coprocessors To: Ben Hutchings Cc: Sasha Levin , LKML , stable@vger.kernel.org, "open list:TENSILICA XTENSA PORT (xtensa)" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Aug 19, 2019 at 9:53 AM Ben Hutchings wrote: > > On Tue, 2019-08-06 at 17:37 -0400, Sasha Levin wrote: > > From: Max Filippov > > > > [ Upstream commit e3cacb73e626d885b8cf24103fed0ae26518e3c4 ] > > > > Assembly entry/return abstraction change didn't add asmmacro.h include > > statement to coprocessor.S, resulting in references to undefined macros > > abi_entry and abi_ret on cores that define XTENSA_HAVE_COPROCESSORS. > > Fix that by including asm/asmmacro.h from the coprocessor.S. > [...] > > This seems to be fixing commit d6d5f19e21d9 "xtensa: abstract 'entry' > and 'retw' in assembly code" so it wouldn't be needed for any stable > branches. That's correct. -- Thanks. -- Max