From: Borislav Petkov <bp@suse.de>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Justin Ernst <justin.ernst@hpe.com>,
Hans de Goede <hdegoede@redhat.com>,
Mark Gross <mgross@linux.intel.com>,
Steve Wahl <steve.wahl@hpe.com>,
platform-driver-x86@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] x86/platform/uv: Fix an error code in uv_hubs_init()
Date: Wed, 2 Dec 2020 20:51:31 +0100 [thread overview]
Message-ID: <20201202195131.GD25881@zn.tnic> (raw)
In-Reply-To: <X8eoN/jMAJb3H3iv@mwanda>
On Wed, Dec 02, 2020 at 05:44:07PM +0300, Dan Carpenter wrote:
> Return -ENOMEM on allocation failure instead of returning success.
s/success/random stack memory contents/
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
next prev parent reply other threads:[~2020-12-02 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 14:44 [PATCH] x86/platform/uv: Fix an error code in uv_hubs_init() Dan Carpenter
2020-12-02 19:51 ` Borislav Petkov [this message]
2020-12-02 20:50 ` Ernst, Justin
2020-12-07 10:43 ` Hans de Goede
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=20201202195131.GD25881@zn.tnic \
--to=bp@suse.de \
--cc=dan.carpenter@oracle.com \
--cc=hdegoede@redhat.com \
--cc=justin.ernst@hpe.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=mgross@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=steve.wahl@hpe.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