From: Hans de Goede <hdegoede@redhat.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Vadim Pasternak <vadimp@nvidia.com>,
christophe.jaillet@wanadoo.fr,
platform-driver-x86@vger.kernel.org
Subject: Re: [GIT PULL] Fixes in the mellanox init branch due for v6.6.
Date: Wed, 11 Oct 2023 11:17:58 +0200 [thread overview]
Message-ID: <0ca2c331-651a-d548-0822-7b7cf015de96@redhat.com> (raw)
In-Reply-To: <c51fd7a6-a843-1c83-fa3b-f5dd104cf3ad@linux.intel.com>
Hi Ilpo,
On 10/9/23 14:09, Ilpo Järvinen wrote:
> The following changes since commit 0bb80ecc33a8fb5a682236443c1e740d5c917d1d:
>
> Linux 6.6-rc1 (2023-09-10 16:28:41 -0700)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git tags/platform-drivers-x86-mellanox-init-v6.6
>
> for you to fetch changes up to 7ec4cd3c1a12dc08c60d5e376c2c05aae23f1e41:
>
> platform: mellanox: Fix a resource leak in an error handling path in probing flow (2023-10-06 16:40:35 +0300)
Thank you I've merged the platform-drivers-x86-mellanox-init-v6.6 tag into pdx86/fixes now.
Regards,
Hans
> ----------------------------------------------------------------
> Fixes in the mellanox init branch due for v6.6.
>
> platform-drivers-x86-mellanox-init-v6.6: v6.6-rc1 + fixes in
> the platform-drivers-x86-mellanox-init branch to avoid a feature
> conflict during the v6.7 merge window.
>
> ----------------------------------------------------------------
> Vadim Pasternak (1):
> platform: mellanox: Fix a resource leak in an error handling path in probing flow
>
> drivers/platform/x86/mlx-platform.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
prev parent reply other threads:[~2023-10-11 9:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 12:09 [GIT PULL] Fixes in the mellanox init branch due for v6.6 Ilpo Järvinen
2023-10-11 9:17 ` Hans de Goede [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=0ca2c331-651a-d548-0822-7b7cf015de96@redhat.com \
--to=hdegoede@redhat.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=ilpo.jarvinen@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox