From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id ACCC5C10F14 for ; Wed, 17 Apr 2019 02:01:06 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id E5A7220872 for ; Wed, 17 Apr 2019 02:01:05 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="TfIZ0rh1" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org E5A7220872 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Received: from lists.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 44kQSb61nGzDqCH for ; Wed, 17 Apr 2019 12:01:03 +1000 (AEST) Authentication-Results: lists.ozlabs.org; spf=permerror (mailfrom) smtp.mailfrom=kernel.org (client-ip=2001:8b0:10b:1236::1; helo=casper.infradead.org; envelope-from=mchehab+samsung@kernel.org; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=infradead.org header.i=@infradead.org header.b="TfIZ0rh1"; dkim-atps=neutral Received: from casper.infradead.org (casper.infradead.org [IPv6:2001:8b0:10b:1236::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 44kQQd5F27zDqJT; Wed, 17 Apr 2019 11:59:20 +1000 (AEST) 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 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 X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-hwmon@vger.kernel.org, Jean Delvare , linux-aspeed@lists.ozlabs.org, Linux Doc Mailing List , Andrew Jeffery , Jonathan Corbet , Liviu Dudau , linux-kernel@vger.kernel.org, Mauro Carvalho Chehab , Lorenzo Pieralisi , Paul Mackerras , Joel Stanley , linuxppc-dev@lists.ozlabs.org, Sudeep Holla , linux-arm-kernel@lists.infradead.org Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" 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