From: "PaX Team" <pageexec@freemail.hu>
To: trivial@kernel.org, linux-kernel@vger.kernel.org,
"Jan-Simon Möller" <jsmoeller.linux@gmail.com>
Subject: Re: [PATCH] [TRIVIAL] FIX: unintended variable name reuse
Date: Fri, 05 Apr 2013 19:08:34 +0200 [thread overview]
Message-ID: <515F0512.4124.1F11126A@pageexec.freemail.hu> (raw)
In-Reply-To: <2178091.aRcfQYZIWb@aragorn.auenland.lan>
On 5 Apr 2013 at 18:17, Jan-Simon Möller wrote:
> Cleanup a variable name reuse.
>
>
> Fix suggested by PaX Team <pageexec@freemail.hu>
Reviewed-by: PaX Team <pageexec@freemail.hu>
> Signed-off-by: Jan-Simon Möller <dl9pf@gmx.de>
> ---
> arch/x86/kernel/cpu/perf_event_intel_uncore.c | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
next prev parent reply other threads:[~2013-04-05 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 16:17 [PATCH] [TRIVIAL] FIX: unintended variable name reuse Jan-Simon Möller
2013-04-05 17:08 ` PaX Team [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-04-30 10:02 dl9pf
2013-04-30 13:04 ` Steven Rostedt
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=515F0512.4124.1F11126A@pageexec.freemail.hu \
--to=pageexec@freemail.hu \
--cc=jsmoeller.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.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