Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp3745087yba; Tue, 16 Apr 2019 19:00:58 -0700 (PDT) X-Google-Smtp-Source: APXvYqwQTcv+d9lAqkq48w1hN7+OuHDcsdhA4R9VAfR/2x9IrfkU8nbOASsBA5m4mDI4zhvw9ZDj X-Received: by 2002:a65:6545:: with SMTP id a5mr68649548pgw.264.1555466458349; Tue, 16 Apr 2019 19:00:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1555466458; cv=none; d=google.com; s=arc-20160816; b=YKWiou1GPvvzpoIqdsfA889i4Nr6OE1lLd1BfbZS1SCE+7GjmTq08cqApCZdpO2E7z iRwpIS84tCPc21quft6hjOYGIRgp9sE03qr40AVMV1OOPbC5HA7TyybhjUijpaoWibUn tcaoPK8hsbgWW79PfJQl9d9XgeJph0I+zEGah0ba/YcuXDSy8TpFI/G44Zx2/+tBGc5c vB92yMrvIfQRH/rXXOB0bzMfhKZa83DxsD0isKxXOxOnlXlu7mEv6JMa8dQs0ZrZEH0L E5JaSTPxsqp9XyJ8iyJhtcfI1K+LQohxIxWi8K66qYSI5jnAB3aExq3tu/0OtWtm/98P 3kiQ== 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 :dkim-signature; bh=S8RInvAC69V+yULWzOSPTpkgsKgagKqSc8vWonnjHdk=; b=q4ZJXfDfgBLPvEva04Qpbi2bJKI9Ou1jksptXyK9haZPVd3fBGpZGxW3TMKtVp1y7s 4Gslp17RiQGQttgtx1Kv8Hlcv1Bud4W8n0s2T4QY/dMrIeHiTl+oWqX3U/y8iW9Evwt8 9hHhqu5zK6QJFb10oOTs65dtou3b/yglwz1IcFvpvDH/TUdr452Xp//rCeGSie63jLyu kID4VW0kTfj1SL647i2svLh2Wh4GthiGIPDdElFSeF946F22onsqZ0kmQ09mAEJNgb+r qJm/ggR3vTgWMqFmgAbq5gD0wE/bCI7rF+HHHoamdrV6pjRiExopL+Kehdpd9VNRUdm4 gOJQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@infradead.org header.s=casper.20170209 header.b=TfIZ0rh1; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a3si50740456pfc.276.2019.04.16.19.00.42; Tue, 16 Apr 2019 19:00:58 -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; dkim=fail header.i=@infradead.org header.s=casper.20170209 header.b=TfIZ0rh1; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729901AbfDQB6y (ORCPT + 99 others); Tue, 16 Apr 2019 21:58:54 -0400 Received: from casper.infradead.org ([85.118.1.10]:35016 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728032AbfDQB6y (ORCPT ); Tue, 16 Apr 2019 21:58:54 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=S8RInvAC69V+yULWzOSPTpkgsKgagKqSc8vWonnjHdk=; b=TfIZ0rh1l4cXZFpNZv5pLWq/aa 00bwFyRhCo/rUaf0DQmBAzNWvSho3F5md0vYacEWBt9jTHMweaoFU3+zfwBVhAFObFu1aZfctthgq FIp+7WTw+GM2+UBqEVOyR//5QNPwwj43J63I2Lvp3G6rrqkLhhBlUiw5iwil2i67DtB7NR136hVjo QFNCr4u5cx5K0vt/69EVOUjss9vRm8mSdV+ahE+Fqi1pAcXIKKHiv0BIyV/8Um1ji++crImiONxSo D0Q1GFEVsF++Ntfe8WScX1q1pdHzRPtjewDKAheKk54iPVINNgGydp46Cjrh92ofgWp1mJnpQrH7L wda/oiCA==; Received: from 177.205.118.176.dynamic.adsl.gvt.net.br ([177.205.118.176] helo=coco.lan) by casper.infradead.org with esmtpsa (Exim 4.90_1 #2 (Red Hat Linux)) id 1hGZqV-0002ww-Uz; Wed, 17 Apr 2019 01:58:44 +0000 Date: Tue, 16 Apr 2019 22:58:36 -0300 From: Mauro Carvalho Chehab To: Guenter Roeck Cc: Jonathan Corbet , Linux Doc Mailing List , Mauro Carvalho Chehab , linux-kernel@vger.kernel.org, Andrew Jeffery , Benjamin Herrenschmidt , Jean Delvare , Joel Stanley , linux-arm-kernel@lists.infradead.org, linux-aspeed@lists.ozlabs.org, linux-hwmon@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, Liviu Dudau , Lorenzo Pieralisi , Michael Ellerman , Paul Mackerras , Sudeep Holla Subject: Re: [PATCH v2 00/21] Convert hwmon documentation to ReST Message-ID: <20190416225836.1d5953bc@coco.lan> In-Reply-To: <20190416203114.GB25517@roeck-us.net> References: <20190411124324.3ed62fad@lwn.net> <20190411174357.251904f5@coco.lan> <20190411210731.GA29378@roeck-us.net> <20190412100451.6fe49de7@lwn.net> <20190416141949.09b48789@lwn.net> <20190416203114.GB25517@roeck-us.net> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Em Tue, 16 Apr 2019 13:31:14 -0700 Guenter Roeck escreveu: > On Tue, Apr 16, 2019 at 02:19:49PM -0600, Jonathan Corbet wrote: > > On Fri, 12 Apr 2019 20:09:16 -0700 > > Guenter Roeck wrote: > > > > > The big real-world question is: Is the series good enough for you to accept, > > > or do you expect some level of user/kernel separation ? > > > > I guess it can go in; it's forward progress, even if it doesn't make the > > improvements I would like to see. > > > > The real question, I guess, is who should take it. I've been seeing a > > fair amount of activity on hwmon, so I suspect that the potential for > > conflicts is real. Perhaps things would go smoother if it went through > > your tree? > > > We'll see a number of conflicts, yes. In terms of timing, this is probably > the worst release in the last few years to make such a change. I currently > have 9 patches queued in hwmon-next which touch Documentation/hwmon. > Of course the changes made in those are all not ReST compatible, and I have > no idea what to look out for to make it compatible. So this is going to be > fun (in a negative sense) either way. > > I don't really have a recommendation at this point; I think the best I could > do to take the patches which don't generate conflicts and leave the rest > alone. But that would also be bad, since the new index file would not match > reality. No idea, really, what the best or even a useful approach would be. > > Maybe automated changes like this (assuming they are indeed automated) > can be generated and pushed right after a commit window closes. Would > that by any chance be possible ? No, those patches are hand-maid, but I can surely rebase it on the top of your tree. Is your tree already merged at linux-next, or should I use some other branch/tree for rebase? Thanks, Mauro