Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp930205ybp; Fri, 4 Oct 2019 07:11:07 -0700 (PDT) X-Google-Smtp-Source: APXvYqymQR4nBU80f1RiCIGNfNf2Ml5K/E7YCV8UBca+jPkDnS9if3rMg0ARrDui/Prw3OL8pNFZ X-Received: by 2002:a05:6402:13cd:: with SMTP id a13mr15192370edx.6.1570198267392; Fri, 04 Oct 2019 07:11:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570198267; cv=none; d=google.com; s=arc-20160816; b=Mf/CzP6LkljOSIlaqB2JJwwQt6OpwPaniu/q8mmAGPNGE7zPMRMkjVRSxWPcdrhudR MhVRjxJ1sd/Dx/WXmMqW59XUK7Rf07L29GfbTLw86TLi5oDT9cr7V1TAl4QoEkAKJ2zF MQwTk/tWVLeOX9EsHTKP1yBJbdxlD8NXAq9z3t6Q9vWf7zKsdfxxTn5r910/OYddz9/c AO62UTHFkPB1/2eIooeAaN9fmfnDz2A6DaE74vGg97kuXhvCLuVwqv/CD+LY+rzE4NRt vYdWa4VE/EdAEN1JGrap5PRZlerOE6+YobuR513JXHjt+rTANVBNavIx6DUeTUPTmKjt 9SJA== 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-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=L5pyMcfxBUycjbZ3zEJh0WWiIlUv3HQweo0qxjcJAGo=; b=zsme1WWZy0DvRNSdE8EHp7XfRb+f31gLFY0AgMlytXuLrhAAGu+ZCfyAqeImrQ73Au wa0wzoYr1HKeU0wwsZHrsClAZNQOT758NaMnOejhytKt7stD9rxmOUASzp6OS/K9PGTg DIIyiKCOMHXJQrrEhTHm5Os50LfrgPl7E3pwicVzs7C+eyYv4ah8SSjJqwAVyXrAU1TE Aw6PvBACmMYqiJHYA+weSfnFy1UV3c20yE8h09rwPwzsmQhFr91EegRFbZOH6Se7FPMQ ZWae8Np/qPkp5NsaiWv+JeXVwMa/2c1VDogB/+to85rIaR59UGwNGgnm5/G9fAqTUzSr v25Q== 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 y8si3812689edd.355.2019.10.04.07.10.43; Fri, 04 Oct 2019 07:11: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 S2389073AbfJDOJS (ORCPT + 99 others); Fri, 4 Oct 2019 10:09:18 -0400 Received: from metis.ext.pengutronix.de ([85.220.165.71]:38449 "EHLO metis.ext.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388971AbfJDOJS (ORCPT ); Fri, 4 Oct 2019 10:09:18 -0400 Received: from pty.hi.pengutronix.de ([2001:67c:670:100:1d::c5]) by metis.ext.pengutronix.de with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1iGOGg-0007DO-KU; Fri, 04 Oct 2019 16:09:14 +0200 Received: from ukl by pty.hi.pengutronix.de with local (Exim 4.89) (envelope-from ) id 1iGOGg-0004Ps-3s; Fri, 04 Oct 2019 16:09:14 +0200 Date: Fri, 4 Oct 2019 16:09:14 +0200 From: Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= To: Rasmus Villemoes Cc: Thierry Reding , devicetree@vger.kernel.org, Rob Herring , linux-pwm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 6/6] pwm: update comment on struct pwm_ops::apply Message-ID: <20191004140914.paljfpruoob5y54x@pengutronix.de> References: <20191004133207.6663-1-linux@rasmusvillemoes.dk> <20191004133207.6663-7-linux@rasmusvillemoes.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20191004133207.6663-7-linux@rasmusvillemoes.dk> User-Agent: NeoMutt/20170113 (1.7.2) X-SA-Exim-Connect-IP: 2001:67c:670:100:1d::c5 X-SA-Exim-Mail-From: ukl@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Oct 04, 2019 at 03:32:07PM +0200, Rasmus Villemoes wrote: > Commit 71523d1812ac (pwm: Ensure pwm_apply_state() doesn't modify the > state argument) updated the kernel-doc for pwm_apply_state(), but not > for the ->apply callback in the pwm_ops struct. > > Signed-off-by: Rasmus Villemoes > --- > include/linux/pwm.h | 5 +---- > 1 file changed, 1 insertion(+), 4 deletions(-) > > diff --git a/include/linux/pwm.h b/include/linux/pwm.h > index b2c9c460947d..0ef808d925bb 100644 > --- a/include/linux/pwm.h > +++ b/include/linux/pwm.h > @@ -243,10 +243,7 @@ pwm_set_relative_duty_cycle(struct pwm_state *state, unsigned int duty_cycle, > * @request: optional hook for requesting a PWM > * @free: optional hook for freeing a PWM > * @capture: capture and report PWM signal > - * @apply: atomically apply a new PWM config. The state argument > - * should be adjusted with the real hardware config (if the > - * approximate the period or duty_cycle value, state should > - * reflect it) > + * @apply: atomically apply a new PWM config Reviewed-by: Uwe Kleine-K?nig Thanks Uwe -- Pengutronix e.K. | Uwe Kleine-K?nig | Industrial Linux Solutions | http://www.pengutronix.de/ |