Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp3145113yba; Mon, 8 Apr 2019 12:09:08 -0700 (PDT) X-Google-Smtp-Source: APXvYqye3Apq0csnFGbiP8UR3LtkoHMTn/W1XC5qGuGOWd/chaCbzh7vsajxWkqxkKjvkNF3ZCcE X-Received: by 2002:a65:5c8c:: with SMTP id a12mr30134457pgt.296.1554750547998; Mon, 08 Apr 2019 12:09:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554750547; cv=none; d=google.com; s=arc-20160816; b=ts/aS9+L5NQjlTY/stVKXS9OLuI9WIacDd1U8fkkXxFELV4LoGdPCZggpbgL+bA6aU DGPDK5AaKwlskgjJs/hlAv/G/B0lEtCxGU/n/EDKSz621kdAYgcs4+HCVscZtBS8+VAF BNNEO03gznuJqqa9L096QqrPWhPQ6OvqAlf3itsmCmWInJXA5gInQhjmsW22rojP02XW vhL8pprZUf9Fs2OrJeMIRWMeBNMCqaP6hL78+GQOzWTeQ9TYYazMgiJJtwsNzxROiEld fCTYTaXn8Pf3pQuw5g9lId5NYdjvlbdA9uOXyqmnD2r18Vvy+zLFw7bwQD1eSaq7I2M1 7KMQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=D7wKZ9d+JY2B+BpVfXF5AeDMoBc3Qs7UfcuT4MVrVtc=; b=VPQUeLRsl/T54f0KoiRkLY1TDWlsWmYnh/ltP+qBqnkQgF0sWlfq4Jp8fI79Dl7byD sx4DXdbjzF5pwyxTYPtBjy/BSgjPv1hl9ukHUjHtXGTGm/gOAhuZEJSEjlB6gV/nMTNt rfy41BreBUVzVCt4wackuTfwpKGVrIQwWkE3VtNGlwJyYVadXBnWdLazPMmnka+NMJUC xp+Yp5F3Y9yPp2FyNmnBIch7MHzliaYQB3Efqk4y1uYorH488aUB47QTavssbEJm3biV t9CzFrozqC72kfOoQtYxOktw/5QzPvGS8LbmLRCjklSWUlgGGqvtB0wXi152Q5WgHmub WiKA== 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 l98si27364263plb.165.2019.04.08.12.08.51; Mon, 08 Apr 2019 12:09:07 -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 S1729206AbfDHStE convert rfc822-to-8bit (ORCPT + 99 others); Mon, 8 Apr 2019 14:49:04 -0400 Received: from mx2.suse.de ([195.135.220.15]:49134 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726373AbfDHStE (ORCPT ); Mon, 8 Apr 2019 14:49:04 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 2564FADE2; Mon, 8 Apr 2019 18:49:02 +0000 (UTC) Date: Mon, 8 Apr 2019 20:48:47 +0200 From: Thomas Bogendoerfer To: David Miller Cc: ralf@linux-mips.org, paul.burton@mips.com, jhogan@kernel.org, dmitry.torokhov@gmail.com, lee.jones@linaro.org, a.zummo@towertech.it, alexandre.belloni@bootlin.com, gregkh@linuxfoundation.org, jslaby@suse.com, linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org, linux-input@vger.kernel.org, netdev@vger.kernel.org, linux-rtc@vger.kernel.org, linux-serial@vger.kernel.org Subject: Re: [PATCH 2/6] MIPS: SGI-IP27: remove setup of RTC platform device Message-Id: <20190408204847.d9f0c870a690aec8179f0615@suse.de> In-Reply-To: <20190408.100528.608078178525055072.davem@davemloft.net> References: <20190408142100.27618-1-tbogendoerfer@suse.de> <20190408142100.27618-3-tbogendoerfer@suse.de> <20190408.100528.608078178525055072.davem@davemloft.net> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; x86_64-suse-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 08 Apr 2019 10:05:28 -0700 (PDT) David Miller wrote: > From: Thomas Bogendoerfer > Date: Mon, 8 Apr 2019 16:20:54 +0200 > > > RTC platform device will be setup by new IOC3 MFD driver, therefore > > remove it from IP27 platform code. > > > > Signed-off-by: Thomas Bogendoerfer > > You cannot break the driver like this. > > Your patch series must be fully bisectable, which means that after > this patch is applied things still must continue working properly. I see your point and the ethernet driver itself will work properly, but of course IP27 will be working again after applying the whole series. One way I can see to solve this to also add the addition of the serial driver into it. Then we are on par with the current driver. Does this solve your concern ? Thomas. -- SUSE Linux GmbH GF: Felix Imend?rffer, Mary Higgins, Sri Rasiah HRB 21284 (AG N?rnberg)