From: Gautham R Shenoy <ego@in.ibm.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
torvalds <torvalds@linux-foundation.org>,
akpm <akpm@linux-foundation.org>,
mingo@elte.hu
Subject: Re: [PATCH] sched: fix errors in struct & function comments
Date: Thu, 2 Apr 2009 23:26:24 +0530 [thread overview]
Message-ID: <20090402175624.GB22030@in.ibm.com> (raw)
In-Reply-To: <20090328215247.daaad3f3.randy.dunlap@oracle.com>
On Sat, Mar 28, 2009 at 09:52:47PM -0700, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> Fix kernel-doc errors in sched.c: the structs don't have
> kernel-doc notation and the short function description needs to
> be one line only.
Sorry, that's my fault.
Didn't know about the kernel-doc notation for structs.
Thanks Randy for fixing this.
>
> Error(kernel/sched.c:3197): cannot understand prototype: 'struct sd_lb_stats '
> Error(kernel/sched.c:3228): cannot understand prototype: 'struct sg_lb_stats '
> Error(kernel/sched.c:3375): duplicate section name 'Description'
>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> cc: Ingo Molnar <mingo@elte.hu>
> ---
> kernel/sched.c | 15 ++++++++-------
> 1 file changed, 8 insertions(+), 7 deletions(-)
>
> --- linux-2.6.29-git4.orig/kernel/sched.c
> +++ linux-2.6.29-git4/kernel/sched.c
> @@ -3190,7 +3190,7 @@ static int move_one_task(struct rq *this
> return 0;
> }
> /********** Helpers for find_busiest_group ************************/
> -/**
> +/*
> * sd_lb_stats - Structure to store the statistics of a sched_domain
> * during load balancing.
> */
> @@ -3222,7 +3222,7 @@ struct sd_lb_stats {
> #endif
> };
>
> -/**
> +/*
> * sg_lb_stats - stats of a sched_group required for load_balancing
> */
> struct sg_lb_stats {
> @@ -3360,16 +3360,17 @@ static inline void update_sd_power_savin
> }
>
> /**
> - * check_power_save_busiest_group - Check if we have potential to perform
> - * some power-savings balance. If yes, set the busiest group to be
> - * the least loaded group in the sched_domain, so that it's CPUs can
> - * be put to idle.
> - *
> + * check_power_save_busiest_group - see if there is potential for some power-savings balance
> * @sds: Variable containing the statistics of the sched_domain
> * under consideration.
> * @this_cpu: Cpu at which we're currently performing load-balancing.
> * @imbalance: Variable to store the imbalance.
> *
> + * Description:
> + * Check if we have potential to perform some power-savings balance.
> + * If yes, set the busiest group to be the least loaded group in the
> + * sched_domain, so that it's CPUs can be put to idle.
> + *
> * Returns 1 if there is potential to perform power-savings balance.
> * Else returns 0.
> */
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
Thanks and Regards
gautham
prev parent reply other threads:[~2009-04-02 17:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-29 4:52 [PATCH] sched: fix errors in struct & function comments Randy Dunlap
2009-04-02 17:56 ` Gautham R Shenoy [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090402175624.GB22030@in.ibm.com \
--to=ego@in.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=randy.dunlap@oracle.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox