From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Tony Luck <tony.luck@intel.com>,
Zhang Yanmin <yanmin.zhang@intel.com>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-ia64@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/2] ia64: topology: Fix an error handling path in cache_add_dev()
Date: Mon, 28 Mar 2022 19:16:21 +0000 [thread overview]
Message-ID: <facd6471-4c4f-ff5a-e81f-38acd855eb8d@physik.fu-berlin.de> (raw)
In-Reply-To: <452b20c160a20754022407acefd2abb170f43d14.1648494330.git.christophe.jaillet@wanadoo.fr>
Hi Christophe!
On 3/28/22 21:07, Christophe JAILLET wrote:
> If kobject_init_and_add()fails, kobject_put() needs to be called.
> Add the missing call which is already there a few lines below in another
> error handling path.
>
> Fixes: f19180056ea0 ("[IA64] Export cpu cache info by sysfs")
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Thanks for your patches. There is currently no maintainer for ia64, so the patches
would have to go through Andrew Morton's tree.
However, I can test the patches and verify they don't break anything.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2022-03-28 19:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 19:07 [PATCH 1/2] ia64: topology: Fix an error handling path in cache_add_dev() Christophe JAILLET
2022-03-28 19:07 ` [PATCH 2/2] ia64: topology: Slightly simplify code Christophe JAILLET
2022-03-28 19:16 ` John Paul Adrian Glaubitz [this message]
2022-03-28 19:45 ` [PATCH 1/2] ia64: topology: Fix an error handling path in cache_add_dev() Christophe JAILLET
2022-03-28 20:07 ` John Paul Adrian Glaubitz
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=facd6471-4c4f-ff5a-e81f-38acd855eb8d@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=akpm@linux-foundation.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=yanmin.zhang@intel.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