Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3270510imu; Sun, 11 Nov 2018 11:11:03 -0800 (PST) X-Google-Smtp-Source: AJdET5eEHpwG6FC1dNIGQWnjxmHuu/l1cOR+T6mjIegaMpxC1JhwEbgzPQ/LgWNYq5rD7bbTdsDA X-Received: by 2002:a17:902:9a04:: with SMTP id v4-v6mr16797408plp.247.1541963463562; Sun, 11 Nov 2018 11:11:03 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541963463; cv=none; d=google.com; s=arc-20160816; b=kTAJwHUITO+R/EbApGerTumXs9w/DuSxlTMc/XRmj96cMf0QSeeercTED2NBGvQA45 E36HpxlVvLdxFa3mt1OUDcbpIC3PxThIKu6csiHbncDWMvpitql8c8PkNMf7n/3au9ry jumM320HZe7pN4bAmvpNvb56Efd4CzaPGf3prjPozsfnR4GyBowcQcWnx19iqw2oHuCc 6vquiatosAYe7tfS7kTdXfOCcA73olLV+53ASnlAmVqyM5BQGVidwRWoVl8R3odPiHRA DivfC/yhc3GV/m9M092hOWSndl1NywbriatSNUmPDiw9G8mgcn6VPFkv/buQOaqBBHw5 qnYw== 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:dkim-signature; bh=s+9qhgCFq35/vYhsCwa2F0kzcMUkKt7lR4yctbpTcEU=; b=MQj+Kvi9ljdIwdam36nP4xz3kyNkqadXY8bjfaPTfEYHxnWPx3Fx1c6EAWh+/f6Sfx xUtUJwWk3rytuWaYr4IbvJQirJ1JPqYWYMC3ViPZb31s4N1Pi4RMmrzSP5HOlJHXrqpN G47nro/epgFWF6ZyIkj7ooXH/ZDFkjwImAA7V1S/4VxxTAsq1e+YQwJfxBsMtA+Hx2FM VSUnVGWhwBBmyDgZYCtTIxs77bHiZ2mZU9yc4Kjllo1/LtW0i00tah40Ip9N+ZXp3Nvc B7MNKqoPcRg7JahKRwM5GPNzI67x7gfWqfPQoCpyn7ioNIuMuvSO0wYg2+kCh60ZVS/p d5tw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=x6TeAeK5; 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 w11-v6si15450147pfk.208.2018.11.11.11.10.45; Sun, 11 Nov 2018 11:11:03 -0800 (PST) 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; dkim=pass header.i=@kernel.org header.s=default header.b=x6TeAeK5; 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 S1729487AbeKLE7n (ORCPT + 99 others); Sun, 11 Nov 2018 23:59:43 -0500 Received: from mail.kernel.org ([198.145.29.99]:42852 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729426AbeKLE7m (ORCPT ); Sun, 11 Nov 2018 23:59:42 -0500 Received: from localhost (unknown [206.108.79.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 5A9A820871; Sun, 11 Nov 2018 19:10:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1541963421; bh=SwDuDn02uSZBfKW/4peMSUJV4aPW8r7+hgyovSsrCng=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=x6TeAeK5CxGIthfq8GbobFcjQcyPKEWyn1Lj30co582o4cXv7T80r4GQwbwuwmCdu U2+tLujYDvHiqbtwO8xY77FIvIzJYKBCSsp8hiVa2G8saYbreBJFhozO+S+gqri/1A +CFFdDwW+dmy06ANRa+w8DIs7O4NYDo6PQLuqDt4= Date: Sun, 11 Nov 2018 11:10:20 -0800 From: Greg Kroah-Hartman To: Boris Brezillon Cc: Wolfram Sang , linux-i2c@vger.kernel.org, Jonathan Corbet , linux-doc@vger.kernel.org, Arnd Bergmann , Przemyslaw Sroka , Arkadiusz Golec , Alan Douglas , Bartosz Folta , Damian Kos , Alicja Jurasik-Urbaniak , Cyprian Wronka , Suresh Punnoose , Rafal Ciepiela , Thomas Petazzoni , Nishanth Menon , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Vitor Soares , Geert Uytterhoeven , Linus Walleij , Xiang Lin , linux-gpio@vger.kernel.org, Sekhar Nori , Przemyslaw Gaj , Peter Rosin , Mike Shettel , Stephen Boyd , Stephen Rothwell Subject: Re: [PATCH v10 0/9] Add the I3C subsystem Message-ID: <20181111191020.GA21003@kroah.com> References: <20181026144333.12276-1-boris.brezillon@bootlin.com> <20181111173932.GA12254@kroah.com> <20181111191017.7b2efdf1@bbrezillon> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181111191017.7b2efdf1@bbrezillon> 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 On Sun, Nov 11, 2018 at 07:10:17PM +0100, Boris Brezillon wrote: > Hi Greg, > > On Sun, 11 Nov 2018 09:39:32 -0800 > Greg Kroah-Hartman wrote: > > > On Fri, Oct 26, 2018 at 04:43:24PM +0200, Boris Brezillon wrote: > > > Hi Greg, > > > > > > I think we've reached a point where we can eventually consider the I3C > > > framework for inclusion in 4.20 (5.0?). A few more issues were reported > > > on v9 and fixed in v10. I can't guarantee that the implementation is > > > free of bugs but I still think it's worth merging it in v4.20: it's a > > > new subsystem, so we don't risk regressions, and the only way we can > > > detect other issues is by having other people experiment with this > > > implementation. > > > > > > The only remaining concern raised by Arnd is the fact that both hosts > > > and slaves share the same bus type and are differentiated thanks to > > > their device_type, which IMHO is fine since this is what other > > > subsystems do (plus I don't see other solutions to have both I3C > > > devices and I3C buses represented under /sys/bus/i3c/). > > > > Yeah, it's not the nicest, but it will work, we did it also for USB and > > greybus and it solves the issue. > > > > This all looks good to me, so I've queued it up. Let's see if > > linux-next has any problems with it. > > I recently asked Stephen to add the linux-i3c tree to linux-next, so > I'm expecting conflicts :-/. Sorry, I didn't know you were planning to > take these patches through your tree. > > BTW, I also fixed a couple of things when rebasing on top of 4.20-rc1: > > - KernelVersion in the sysfs ABI doc has been updated to 5.0 There is no 5.0 yet :) > - Fixed i3c_master_getmxds_locked() (bug reported/fixed by Colin here > https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1799850.html) > - Removed a blank line at the end of master-driver-api.rst > > For the record, the i3c/next branch pulled by Stephen is available here > [1]. > > > Thanks for sticking with it, nice work! > > Thanks for reviewing it! Greg, Stephen, let me know if you want me to > reset i3c/next to v4.20-rc1 to avoid conflicts in linux-next. So do you want me to just drop these patches from my tree? If so, I can, but i have no problem sending these to Linus for the next -rc1 merge window through my tree if that is easier. It's up to you. greg k-h