Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: mirq-linux@rere.qmqm.pl, adrian.hunter@intel.com,
	ludovic.desroches@microchip.com, stable@vger.kernel.org,
	ulf.hansson@linaro.org
Subject: Re: FAILED: patch "[PATCH] mmc: sdhci-of-at91: fix memleak on clk_get failure" failed to apply to 5.5-stable tree
Date: Thu, 6 Feb 2020 20:09:50 -0500	[thread overview]
Message-ID: <20200207010950.GQ31482@sasha-vm> (raw)
In-Reply-To: <1581016127158142@kroah.com>

On Thu, Feb 06, 2020 at 08:08:47PM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 5.5-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From a04184ce777b46e92c2b3c93c6dcb2754cb005e1 Mon Sep 17 00:00:00 2001
>From: =?UTF-8?q?Micha=C5=82=20Miros=C5=82aw?= <mirq-linux@rere.qmqm.pl>
>Date: Thu, 2 Jan 2020 11:42:16 +0100
>Subject: [PATCH] mmc: sdhci-of-at91: fix memleak on clk_get failure
>MIME-Version: 1.0
>Content-Type: text/plain; charset=UTF-8
>Content-Transfer-Encoding: 8bit
>
>sdhci_alloc_host() does its work not using managed infrastructure, so
>needs explicit free on error path. Add it where needed.
>
>Cc: <stable@vger.kernel.org>
>Fixes: bb5f8ea4d514 ("mmc: sdhci-of-at91: introduce driver for the Atmel SDMMC")
>Signed-off-by: Michał Mirosław <mirq-linux@rere.qmqm.pl>
>Acked-by: Ludovic Desroches <ludovic.desroches@microchip.com>
>Acked-by: Adrian Hunter <adrian.hunter@intel.com>
>Link: https://lore.kernel.org/r/b2a44d5be2e06ff075f32477e466598bb0f07b36.1577961679.git.mirq-linux@rere.qmqm.pl
>Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>

We're missing 3976656d67c1 ("mmc: sdhci-of-at91: rework clocks
management to support SAM9x60 device") on older kernels. I've fixed it
up and queued for 5.5-4.14. I don't think it applies to older kernels,
but happy to be proven otherwise.

-- 
Thanks,
Sasha

  reply	other threads:[~2020-02-07  1:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06 19:08 FAILED: patch "[PATCH] mmc: sdhci-of-at91: fix memleak on clk_get failure" failed to apply to 5.5-stable tree gregkh
2020-02-07  1:09 ` Sasha Levin [this message]
2020-02-11  6:21   ` Ludovic Desroches

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=20200207010950.GQ31482@sasha-vm \
    --to=sashal@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=ludovic.desroches@microchip.com \
    --cc=mirq-linux@rere.qmqm.pl \
    --cc=stable@vger.kernel.org \
    --cc=ulf.hansson@linaro.org \
    /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