Received: by 10.223.185.116 with SMTP id b49csp450241wrg; Fri, 16 Feb 2018 01:35:27 -0800 (PST) X-Google-Smtp-Source: AH8x22664k988P85UO3ycW9pI2KziTgceuvBPxSbqX3qUVR9oV5MpHyQAEXDPlsnxnl4AwJ4DFcx X-Received: by 10.99.96.206 with SMTP id u197mr4503823pgb.261.1518773727273; Fri, 16 Feb 2018 01:35:27 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518773727; cv=none; d=google.com; s=arc-20160816; b=VdO23LmazPZmM935SYBreiCfDhR4Q06tmmgXJ1oxO5lGepqz7ckUWEMwD1IfQj2kxT a5bUEe1XqjpKiUjsucgDSi1pSaddR2qRd/TZB4FFFw8BiRWAiqLBVHSIdYRl2KNCSYxx wSkGXLeupbCPxy4Y4PpC57MR9/J2cl0UDeKmetyG9t63Dk+DzAoU/BWZPzrNPluy5UjJ vs33QTcXvhY8ihX5eu2dXHIEtt+q5ma3ScEsoOh1RZoozb03m5fqvnonuFp6dz3713Dv i+Dqlcg4tp/2bsknoFOjONZHP5hCS0/lFWXpGtXAZQ6SkxX3CtvRAlE26h0Vys2G8fxr ULEQ== 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:arc-authentication-results; bh=RpsBzCLybllUk0sWpHGjvA3j8rZKjK2NPQLlDHFDRgI=; b=SqyKo51yN8J/aLbYJWJwZkaDKvU3dS4iAujPL3NxvQoff6ubLH7IAN+i6eIWZkza4W 5yhFesaW9C/McCbsTlZkyNfi2PBrNZpIaUMr6H3KGGbs0k4D7fdZ9k4GM8+NhHqP/fRB vYtUJtybjczotJ2Wdpj7KcUU2JzOm584/ygGmy/PiDprh+n6BXM0Ndo1AGYyQO3iYtu3 CUW64k1BGFOmRUKkYPObV/qEJPMpIBvXbjy5d4WKqTuZFTQOxxzWBbuPkgokeWE1OtfV hWvgUS50iQ20f9cIUvX3nwLWwkKPQEaj4cUvGtMqrDe2pvdSHJfI1dZjTc6Sp5IWwKZ9 BfpQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@infradead.org header.s=merlin.20170209 header.b=HCYJ9Ht3; 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 f74si1222800pfa.365.2018.02.16.01.35.12; Fri, 16 Feb 2018 01:35:27 -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=fail header.i=@infradead.org header.s=merlin.20170209 header.b=HCYJ9Ht3; 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 S1426590AbeBOQwV (ORCPT + 99 others); Thu, 15 Feb 2018 11:52:21 -0500 Received: from merlin.infradead.org ([205.233.59.134]:49778 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1423757AbeBOQwR (ORCPT ); Thu, 15 Feb 2018 11:52:17 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=merlin.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding: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=RpsBzCLybllUk0sWpHGjvA3j8rZKjK2NPQLlDHFDRgI=; b=HCYJ9Ht3dQ0qwu1Q9MqGdluQa helDGkryoMbUZdVkP/1tqLBlWgjYcIpnhzDXwG9i4u1Fpe2hbLcRShUstz3248DW/omjpkbBWVuMj q5s25eTIdj34P6YeQcR8oeBagikCYhjZfXxCP5sSwwVHDgNgLPLZyf/bhgczCCE3Qs8Bor0hKXR0m ICME1iIXAmwV3YnXznIZYl0spGsMa4VVgcTeMX1jnoJZHKWzXtQQJhs+4F/uYXzKwPKVjMNMf8Der c5z9D4quHVQThXp9PvJCbJj2tJQhnzbCBikdSDtYEyzbSTDrnxU7x+nfeJEYzdloVdZITJDOjun7O hk3wuN/oA==; Received: from j217100.upc-j.chello.nl ([24.132.217.100] helo=hirez.programming.kicks-ass.net) by merlin.infradead.org with esmtpsa (Exim 4.89 #1 (Red Hat Linux)) id 1emMlZ-0005I0-6u; Thu, 15 Feb 2018 16:52:13 +0000 Received: by hirez.programming.kicks-ass.net (Postfix, from userid 1000) id 0DCF8201FB4E9; Thu, 15 Feb 2018 17:52:12 +0100 (CET) Date: Thu, 15 Feb 2018 17:52:12 +0100 From: Peter Zijlstra To: Christopher Diaz Riveros Cc: mingo@redhat.com, linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org Subject: Re: [PATCH-next] sched/headers: Clean up Message-ID: <20180215165212.GB25181@hirez.programming.kicks-ass.net> References: <20180215154318.15894-1-chrisadr@gentoo.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180215154318.15894-1-chrisadr@gentoo.org> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 15, 2018 at 10:43:18AM -0500, Christopher Diaz Riveros wrote: > @@ -183,7 +183,7 @@ extern void io_schedule_finish(int token); > extern long io_schedule_timeout(long timeout); > extern void io_schedule(void); > > -/** > +/* > * struct prev_cputime - snapshot of system and user cputime > * @utime: time spent in user mode > * @stime: time spent in system mode > @@ -200,7 +200,7 @@ struct prev_cputime { > #endif > }; > > -/** > +/* > * struct task_cputime - collected CPU time counts > * @utime: time spent in user mode, in nanoseconds > * @stime: time spent in kernel mode, in nanoseconds Why, are those not valid kerneldoc comments? > @@ -437,20 +437,28 @@ struct sched_dl_entity { > * during sched_setattr(), they will remain the same until > * the next sched_setattr(). > */ > - u64 dl_runtime; /* Maximum runtime for each instance */ > - u64 dl_deadline; /* Relative deadline of each instance */ > - u64 dl_period; /* Separation of two instances (period) */ > - u64 dl_bw; /* dl_runtime / dl_period */ > - u64 dl_density; /* dl_runtime / dl_deadline */ > + /* Maximum runtime for each instance */ > + u64 dl_runtime; > + /* Relative deadline of each instance */ > + u64 dl_deadline; > + /* Separation of two instances (period) */ > + u64 dl_period; > + /* dl_runtime / dl_period */ > + u64 dl_bw; > + /* dl_runtime / dl_deadline */ > + u64 dl_density; That's a whole lot less readable :/