Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp3570755ybl; Mon, 12 Aug 2019 02:46:22 -0700 (PDT) X-Google-Smtp-Source: APXvYqwtNsbnqsCrDQFXdz7PLC/1c5p263ANcEOi98Y9j7DSG/2WS+/SKMRH6r0izOu/ebAgfv52 X-Received: by 2002:a17:902:8f93:: with SMTP id z19mr30960436plo.97.1565603182394; Mon, 12 Aug 2019 02:46:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565603182; cv=none; d=google.com; s=arc-20160816; b=OZd5Be7iY7L3KL6LRRrP9caDEuyHh3bwd17kg0CIQxxpZM4VteVDsoHLTY3W0WXLcl CludYZacMT7TAG0u28JBWvyRg0cAusoAk489I51EsNbJbdPqO3TvMvgkUXMiE4txn48N WzHXSkRW4MHIuW7U8IrCmJTDAD6zVufS5G1KacUI4hZnSKu9ZJpKt9iYwNg5lx8GTl3F tpdFMx/Gd1GyR4mcsv0R7m706XxliZVjfcEwd2BRoF21I4kddTqyW0XUBGnE2p69omh3 G6KlJTSg5rsGVOLFSzHHm6h5xXMfeOg2FqhSVT8v5y+Rwma4EQvIB5YeWpWROy4lSNLD QBgg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=L8z5/zYtZCj4domhVSh79xh9y2fMChz+E8Y0MPrvo3g=; b=L82MjxRpEwp+SBKoj7F3NQSOPqdDHBL9CiTte8fskfTqiQFptUEGPDPN1q5ogKvHL1 htUIf5AcyAyXVfve7EH1K4HHSlL07JoGhYtkyXjfVxlWMvMUhBNHbxTskKHGaeuWhS+A nd9Zkg5ouDqhVlsG1NpyVHENGXDXeyoLJk13BHoFF3VGDtVJP3Ou7NcuooWublh0/JtU 2XR5DUz80Y0FSitbF7vD7AMFqhvfT13wGXtiF6/plHscmS/lSWq6rhugqjH9lohn35LH S4QXgoEq5N7LSJuU9WtPKIYKSvuOKFzEsxiBcwWuR/dk11BMN/ogfD048N0pmU+0zn1Z 7+Dw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n5si6491388pjp.90.2019.08.12.02.46.07; Mon, 12 Aug 2019 02:46:22 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727724AbfHLJpE (ORCPT + 99 others); Mon, 12 Aug 2019 05:45:04 -0400 Received: from relay2-d.mail.gandi.net ([217.70.183.194]:51325 "EHLO relay2-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727430AbfHLJpC (ORCPT ); Mon, 12 Aug 2019 05:45:02 -0400 X-Originating-IP: 91.118.195.70 Received: from jirafa.cyrius.com (91-118-195-70.static.upcbusiness.at [91.118.195.70]) (Authenticated sender: tbm@cyrius.com) by relay2-d.mail.gandi.net (Postfix) with ESMTPSA id DA1BF40003; Mon, 12 Aug 2019 09:44:56 +0000 (UTC) Received: by jirafa.cyrius.com (Postfix, from userid 1000) id 58518A887E; Mon, 12 Aug 2019 11:44:56 +0200 (CEST) Date: Mon, 12 Aug 2019 11:44:56 +0200 From: Martin Michlmayr To: Dan Williams Cc: Arnd Bergmann , soc@kernel.org, Russell King , Vinod Koul , Linus Walleij , Bartosz Golaszewski , linux-arm-kernel@lists.infradead.org, Linux Kernel Mailing List , dmaengine@vger.kernel.org, linux-gpio@vger.kernel.org, linux-i2c@vger.kernel.org, Peter Teichmann Subject: Re: [PATCH 1/7] [RFC] ARM: remove Intel iop33x and iop13xx support Message-ID: <20190812094456.GI10598@jirafa.cyrius.com> References: <20190809162956.488941-1-arnd@arndb.de> <20190809163334.489360-1-arnd@arndb.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Dan Williams [2019-08-09 11:34]: > > Earlier versions of OpenWRT and Debian both had support for iop32x > > but not the others, and they both dropped iop32x as well in their 2015 > > releases. > > > > Signed-off-by: Arnd Bergmann > > --- > > I'm just guessing that iop32x is still needed, and the other two are > > not. If anyone disagrees with that assessment, let me know so we > > can come up with an alternative approach. > > I'm not sure who would scream if iop32x support went away as well, but > I have not followed this space in years hence copying Martin. I believe iop13xx were mostly Intel dev boards. I'm not aware of any major devices based on iop33x. As Arnd points out, Debian used to have support for various iop32x devices. While Debian hasn't supported iop32x in a number of years, these devices are still usable and in use (RMK being a prime example). So I think it's safe to drop iop33x/iop13xx while retaining support for iop32x. As I was looking at my email archives, I saw an email from Peter Teichmann who was working on an iop33x based platform (around 2009) so I've copied him as well. > In any event: > > Acked-by: Dan Williams Acked-by: Martin Michlmayr -- Martin Michlmayr https://www.cyrius.com/