From: "John W. Linville" <linville@tuxdriver.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Neil Brown <neilb@suse.de>,
"ksummit-2010-discuss@lists.linux-foundation.org"
<ksummit-2010-discuss@lists.linux-foundation.org>
Subject: Re: [PATCH][GIT PULL] ring-buffer: Place duplicate expression into a single function
Date: Wed, 1 Sep 2010 13:16:22 -0400 [thread overview]
Message-ID: <20100901171622.GE2486@tuxdriver.com> (raw)
In-Reply-To: <1283359792.2356.39.camel@gandalf.stny.rr.com>
On Wed, Sep 01, 2010 at 12:49:52PM -0400, Steven Rostedt wrote:
>
> Ingo,
>
> Please pull the latest tip/perf/core tree, which can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> tip/perf/core
>
>
> Steven Rostedt (1):
> ring-buffer: Place duplicate expression into a single function
>
> ----
> kernel/trace/ring_buffer.c | 21 +++++++++++++++------
> 1 files changed, 15 insertions(+), 6 deletions(-)
> ---------------------------
> commit f6195aa09e618d712f52bf4fa33b5293820eb93d
> Author: Steven Rostedt <srostedt@redhat.com>
> Date: Wed Sep 1 12:23:12 2010 -0400
>
> ring-buffer: Place duplicate expression into a single function
>
> While discussing the strictness of the 80 character limit on the
> Kernel Summit Discussion mailing list, I showed examples that I
> broke that limit slightly with some algorithms. In discussing with
> John Linville, what looked better, I realized that two of the
> 80 char breaking culprits were an identical expression.
>
> As a clean up, this patch moves the identical expression into its
> own helper function and that is used instead. As a side effect,
> the offending code is now under the 80 character limit. :-)
>
> This clean up code also changes the expression from
>
> (A - B) - C to A - (B + C)
>
> This makes the code look a little nicer too.
>
> Cc: John W. Linville <linville@tuxdriver.com>
> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
ACK :-)
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2010-09-01 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100825052123.GA5237@linux.vnet.ibm.com>
[not found] ` <AANLkTinCaKNXadoTtOvBhO3K5mOyzHi=ZJw4guWWB1W6@mail.gmail.com>
[not found] ` <20100826210328.4ccd5aaf@notabene>
[not found] ` <1283220647.1377.69.camel@gandalf.stny.rr.com>
[not found] ` <20100831132708.GA2484@tuxdriver.com>
[not found] ` <1283263428.2945.83.camel@powerslave>
[not found] ` <20100901080715.5834450d@notabene>
[not found] ` <1283295699.1377.732.camel@gandalf.stny.rr.com>
[not found] ` <20100901133653.GB2486@tuxdriver.com>
[not found] ` <1283351527.2356.22.camel@gandalf.stny.rr.com>
2010-09-01 16:49 ` Steven Rostedt
2010-09-01 17:16 ` John W. Linville [this message]
2010-09-01 17:30 ` Ingo Molnar
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=20100901171622.GE2486@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=ksummit-2010-discuss@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=neilb@suse.de \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®