From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Vadim Pasternak <vadimp@nvidia.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
christophe.jaillet@wanadoo.fr,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH platform 0/3] platform/x86: Add fixes and amendments for init()/exit() flows
Date: Fri, 6 Oct 2023 17:55:28 +0300 (EEST) [thread overview]
Message-ID: <c2aa7fdd-fa8a-9fac-7b4e-a09fe821aabc@linux.intel.com> (raw)
In-Reply-To: <20231005075616.42777-1-vadimp@nvidia.com>
On Thu, 5 Oct 2023, Vadim Pasternak wrote:
> The patchset:
> - Fixes memory leak in error handling flow.
> - Add cosmetic changes - misspelling fix, better naming/
>
> Patches #1: Fixes memory leak issue.
> Patch #2: Fix misspelling.
> Patches #3: Renames few routines for better naming convention.
>
> Vadim Pasternak (3):
> platform: mellanox: Fix a resource leak in an error handling path in
> probing flow
> platform: mellanox: Fix misspelling error in routine name
> platform: mellanox: Rename some init()/exit() functions for consistent
> naming
Thanks for the patches. I've applied these into
platform-drivers-x86-mellanox-init branch and merged that into
review-ilpo. (I decided to reorder the patches 2 and 3 though as it felt
more logical ordering.)
--
i.
prev parent reply other threads:[~2023-10-06 14:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 7:56 [PATCH platform 0/3] platform/x86: Add fixes and amendments for init()/exit() flows Vadim Pasternak
2023-10-05 7:56 ` [PATCH platform 1/3] platform: mellanox: Fix a resource leak in an error handling path in probing flow Vadim Pasternak
2023-10-06 13:30 ` Ilpo Järvinen
2023-10-05 7:56 ` [PATCH platform 2/3] platform: mellanox: Fix misspelling error in routine name Vadim Pasternak
2023-10-05 7:56 ` [PATCH platform 3/3] platform: mellanox: Rename some init()/exit() functions for consistent naming Vadim Pasternak
2023-10-06 14:55 ` Ilpo Järvinen [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=c2aa7fdd-fa8a-9fac-7b4e-a09fe821aabc@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=hdegoede@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=vadimp@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.