Received: by 2002:a05:6a11:4021:0:0:0:0 with SMTP id ky33csp636523pxb; Thu, 23 Sep 2021 07:40:13 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyYhNQTNtSUxN57OFwi4Yn2DViqHWPnPf6a1rUAtHtz7E1vSfzKtGnsyD6ptGM64pQc6XMp X-Received: by 2002:a02:b704:: with SMTP id g4mr4250859jam.7.1632408012880; Thu, 23 Sep 2021 07:40:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1632408012; cv=none; d=google.com; s=arc-20160816; b=uqjGFlk8Wac69XYahgLS/Q0oknhVzjF096GeZkXFP3hDsj/V92oZ/MnOu61gaIktCA JQfuaoVWcbzBZLFkzqyjjHTV015PYFR3fkrb6V2pU1J0eG4/7lhvQJTUlTk2vUySkVA9 3u/J9CNrOwDqt+ApKB4k2Gm6qUbebup1z8gM3o0L060bzw/Vt1z0ks4kFKeA+rl4w87d ImiLvi6BgKR3Eu+1hJABsnHB3K2xDS+6uiEEiqHxWt1zijPPY0f3Y4nh9af1h1RhKn5x iJdnf6Jm8wIhnhKnNkVJp2BCPNxEZiszElaISPk/cleQ89fSsmBdACmTWu1L5Pp2IYmk SAuA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id; bh=FxuGml+YJ0UKdfn8N5mytxtvjYGvMVWgZpoOFOzfZv8=; b=Y1UYHMjvM2Ern/isevYxWquJoUaSukmSS5YTfI2gylXjyk9t2sNuNGVpDCQSFtjrk0 UOY+BuIdyT/SNNu2Lj99u9sMLuMfguHB+UgFUFD6yUmnMIqHHyhA3gLFpYYkVtpJFcQe oSivYA/tqo3iramzbc6IBXjyrdStJsA/Uop1bxWwb2XAC2RY1yZlMDspFalnSuxmyyDj a3a22XohSTc/Pj9ZT18RpHC6U1pT+V9K24mfJvi1LF9v7iMAauKT7b5K9UpgUNFVsWLt QeDMDivEloj7B6UkVyaPxLttipCfVlAjkolMt3T7POCzZv1sb5QHlYJlz1Klv14AFXLg Hnog== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id t21si1583778ioh.18.2021.09.23.07.40.00; Thu, 23 Sep 2021 07:40:12 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241710AbhIWOjK (ORCPT + 99 others); Thu, 23 Sep 2021 10:39:10 -0400 Received: from outpost1.zedat.fu-berlin.de ([130.133.4.66]:53103 "EHLO outpost1.zedat.fu-berlin.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241708AbhIWOjJ (ORCPT ); Thu, 23 Sep 2021 10:39:09 -0400 Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.94) with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (envelope-from ) id 1mTPqt-000K86-7O; Thu, 23 Sep 2021 16:37:31 +0200 Received: from p57bd97e9.dip0.t-ipconnect.de ([87.189.151.233] helo=[192.168.178.81]) by inpost2.zedat.fu-berlin.de (Exim 4.94) with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (envelope-from ) id 1mTPqs-001G6v-Gf; Thu, 23 Sep 2021 16:37:31 +0200 Message-ID: Date: Thu, 23 Sep 2021 16:37:29 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.1.0 Subject: Re: [PATCH 0/3 v2] sh: fixes for various build and kconfig warnings Content-Language: en-US To: Rich Felker Cc: Daniel Palmer , Randy Dunlap , Linux Kernel Mailing List , Yoshinori Sato , Linux-sh list , Geert Uytterhoeven , j-core@j-core.org References: <20210627220544.8757-1-rdunlap@infradead.org> <2bae95d0-0932-847c-c105-a333e9956dff@infradead.org> <20210912015740.GJ13220@brightrain.aerifal.cx> <5aa5301e-9b01-4e96-e185-13c2d4d7b675@physik.fu-berlin.de> <20210922024537.GA27465@brightrain.aerifal.cx> From: John Paul Adrian Glaubitz In-Reply-To: <20210922024537.GA27465@brightrain.aerifal.cx> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Original-Sender: glaubitz@physik.fu-berlin.de X-Originating-IP: 87.189.151.233 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Rich! On 9/22/21 04:45, Rich Felker wrote: > I didn't get through that yet, but I have rebased the patches that > were pending in for-next onto v5.15-rc1 (no conflicts) and > smoke-tested that a sh4 build runs in my qemu environment. linux-next > pulled them 27 hours ago and hasn't complained yet either. Sounds promising, thanks! > I started going through the list/patch backlog, but didn't make it > nearly as far as I'd like yet. If you have even a vague list of what's > important (warnings breaking the build, unapplied changes blocking > removal of cruft from other parts of the kernel and making people > unhappy with us, etc.) that would be really helpful. I will start testing kernel updates again from next week as I'm currently busy with other open source work I want to get off my table first. > I'll follow up again soon. Thanks, looking forward for more updates. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaubitz@debian.org `. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913