From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Michael Wang <wangyun@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, dipankar@in.ibm.com,
fengguang.wu@intel.com
Subject: Re: [PATCH] rcu: Fix the code style issue in rcutree_trace_init()
Date: Mon, 29 Oct 2012 02:49:03 -0700 [thread overview]
Message-ID: <20121029094903.GB3027@linux.vnet.ibm.com> (raw)
In-Reply-To: <1351479733-6978-1-git-send-email-wangyun@linux.vnet.ibm.com>
On Mon, Oct 29, 2012 at 11:02:13AM +0800, Michael Wang wrote:
> This patch fix the code style issue caused by:
>
> commit 622afdb3bd6288837a37bac137dfeff4e771798d
> "rcu: Optimize the 'rcudata' for RCU trace"
Queued, thank you Michael.
Thanx, Paul
> Signed-off-by: Michael Wang <wangyun@linux.vnet.ibm.com>
> Reported-by: Fengguang Wu <fengguang.wu@intel.com>
> ---
> kernel/rcutree_trace.c | 60 ++++++++++++++++++++++++------------------------
> 1 files changed, 30 insertions(+), 30 deletions(-)
>
> diff --git a/kernel/rcutree_trace.c b/kernel/rcutree_trace.c
> index 73abfb0..e84679c 100644
> --- a/kernel/rcutree_trace.c
> +++ b/kernel/rcutree_trace.c
> @@ -436,44 +436,44 @@ static int __init rcutree_trace_init(void)
> if (!rspdir)
> goto free_out;
>
> - retval = debugfs_create_file("rcudata", 0444,
> - rspdir, rsp, &rcudata_fops);
> - if (!retval)
> - goto free_out;
> + retval = debugfs_create_file("rcudata", 0444,
> + rspdir, rsp, &rcudata_fops);
> + if (!retval)
> + goto free_out;
>
> - retval = debugfs_create_file("rcuexp", 0444,
> - rspdir, rsp, &rcuexp_fops);
> - if (!retval)
> - goto free_out;
> + retval = debugfs_create_file("rcuexp", 0444,
> + rspdir, rsp, &rcuexp_fops);
> + if (!retval)
> + goto free_out;
>
> - retval = debugfs_create_file("rcu_pending", 0444,
> - rspdir, rsp, &rcu_pending_fops);
> - if (!retval)
> - goto free_out;
> + retval = debugfs_create_file("rcu_pending", 0444,
> + rspdir, rsp, &rcu_pending_fops);
> + if (!retval)
> + goto free_out;
>
> - retval = debugfs_create_file("rcubarrier", 0444,
> - rspdir, rsp, &rcubarrier_fops);
> - if (!retval)
> - goto free_out;
> + retval = debugfs_create_file("rcubarrier", 0444,
> + rspdir, rsp, &rcubarrier_fops);
> + if (!retval)
> + goto free_out;
>
> #ifdef CONFIG_RCU_BOOST
> - if (rsp == &rcu_preempt_state) {
> - retval = debugfs_create_file("rcuboost", 0444,
> - rspdir, NULL, &rcu_node_boost_fops);
> - if (!retval)
> - goto free_out;
> - }
> -#endif
> -
> - retval = debugfs_create_file("rcugp", 0444,
> - rspdir, rsp, &rcugp_fops);
> + if (rsp == &rcu_preempt_state) {
> + retval = debugfs_create_file("rcuboost", 0444,
> + rspdir, NULL, &rcu_node_boost_fops);
> if (!retval)
> goto free_out;
> + }
> +#endif
>
> - retval = debugfs_create_file("rcuhier", 0444,
> - rspdir, rsp, &rcuhier_fops);
> - if (!retval)
> - goto free_out;
> + retval = debugfs_create_file("rcugp", 0444,
> + rspdir, rsp, &rcugp_fops);
> + if (!retval)
> + goto free_out;
> +
> + retval = debugfs_create_file("rcuhier", 0444,
> + rspdir, rsp, &rcuhier_fops);
> + if (!retval)
> + goto free_out;
> }
>
> retval = debugfs_create_file("rcutorture", 0444, rcudir,
> --
> 1.7.4.1
>
parent reply other threads:[~2012-10-29 9:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1351479733-6978-1-git-send-email-wangyun@linux.vnet.ibm.com>]
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=20121029094903.GB3027@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=dipankar@in.ibm.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wangyun@linux.vnet.ibm.com \
/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
Powered by JetHome