From: Borislav Petkov <bp@alien8.de>
To: Junjie Mao <junjie.mao@hotmail.com>
Cc: Doug Thompson <dougthompson@xmission.com>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] edac: fix the leak of mci->bus->name when bus_register fails
Date: Fri, 30 Jan 2015 15:03:04 +0100 [thread overview]
Message-ID: <20150130140304.GE1451@pd.tnic> (raw)
In-Reply-To: <BLU436-SMTP25291B6B612942A212AEBFE95300@phx.gbl>
On Thu, Jan 29, 2015 at 09:13:55AM +0800, Junjie Mao wrote:
> Also use goto labels for all failure paths in edac_create_sysfs_mci_device and
> update meaningless labels.
>
> Signed-off-by: Junjie Mao <junjie.mao@hotmail.com>
Applied, thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
prev parent reply other threads:[~2015-01-30 14:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 1:13 [PATCH v2] edac: fix the leak of mci->bus->name when bus_register fails Junjie Mao
2015-01-30 14:03 ` Borislav Petkov [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=20150130140304.GE1451@pd.tnic \
--to=bp@alien8.de \
--cc=dougthompson@xmission.com \
--cc=junjie.mao@hotmail.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@osg.samsung.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