From: Ingo Molnar <mingo@kernel.org>
To: kernel-janitors@vger.kernel.org
Subject: Re: [patch] perf/x86/intel/pt: cleanup error handling in pt_pmu_hw_init()
Date: Sat, 11 Apr 2015 08:37:14 +0000 [thread overview]
Message-ID: <20150411083714.GB16060@gmail.com> (raw)
In-Reply-To: <20150409090805.GG17605@mwanda>
* Dan Carpenter <dan.carpenter@oracle.com> wrote:
> On Thu, Apr 09, 2015 at 04:54:40PM +0200, Ingo Molnar wrote:
> > > [...] If you unwind like:
> > >
> > > err_free_bar:
> > > kfree(foo->bar);
> > > err_free_foo:
> > > kfree(foo);
> > > return ret;
> > >
> > > That is less error prone.
> >
> > That's how I name and structure unwind labels as well, and my
> > suggestion is to use something similar here in this code too, in
> > arch/x86/kernel/cpu/perf_event_intel_pt.c.
> >
> > Agreed?
>
> I don't understand what you want me to do here. I think you are saying
> I should do this:
>
> err_attrs:
> kfree(attrs);
> err:
> return ret;
Yeah, that looks cleaner.
>
> That's not the style that the rest of this file uses. [...]
That might have slipped through review, but it's not a reason to
continue the bad practice.
Thanks,
Ingo
next prev parent reply other threads:[~2015-04-11 8:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 9:08 [patch] perf/x86/intel/pt: cleanup error handling in pt_pmu_hw_init() Dan Carpenter
2015-04-09 12:02 ` Ingo Molnar
2015-04-09 12:33 ` Dan Carpenter
2015-04-09 12:45 ` Peter Zijlstra
2015-04-09 12:47 ` Alexander Shishkin
2015-04-09 13:30 ` Dan Carpenter
2015-04-09 14:54 ` Ingo Molnar
2015-04-09 15:27 ` Dan Carpenter
2015-04-11 8:37 ` Ingo Molnar [this message]
2015-04-11 11:03 ` Dan Carpenter
2015-04-12 9:38 ` Ingo Molnar
2015-04-12 9:51 ` Julia Lawall
2015-04-12 10:18 ` Ingo Molnar
2015-04-15 10:10 ` Alexander Shishkin
2015-04-15 10:27 ` Dan Carpenter
2015-04-15 10:50 ` Alexander Shishkin
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=20150411083714.GB16060@gmail.com \
--to=mingo@kernel.org \
--cc=kernel-janitors@vger.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;
as well as URLs for NNTP newsgroup(s).