From: Greg KH <gregkh@linuxfoundation.org>
To: Jiri Slaby <jslaby@suse.cz>
Cc: stable@vger.kernel.org, haibo.chen@freescale.com, ulf.hansson@linaro.org
Subject: Re: [PATCH 4.1] mmc: sdhci: fix dma memory leak in sdhci_pre_req()
Date: Sat, 17 Oct 2015 16:50:05 -0700 [thread overview]
Message-ID: <20151017235005.GF9038@kroah.com> (raw)
In-Reply-To: <56138DF6.1050108@suse.cz>
On Tue, Oct 06, 2015 at 11:01:42AM +0200, Jiri Slaby wrote:
> On 10/06/2015, 10:59 AM, Jiri Slaby wrote:
> > [js] add sg_count to mmc_data as happenned in 208489032bdd8d (mmc:
> > mediatek: Add Mediatek MMC driver).
>
> I don't know if this is justifiable or how otherwise to solve this...
> The prereq 208489032bdd8d is way too big for stable, I suppose.
Yeah, that doesn't make sense to add, I'll just take your backport, it's
better.
thanks,
greg k-h
prev parent reply other threads:[~2015-10-17 23:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-26 17:24 FAILED: patch "[PATCH] mmc: sdhci: fix dma memory leak in sdhci_pre_req()" failed to apply to 4.1-stable tree gregkh
2015-10-06 8:59 ` [PATCH 4.1] mmc: sdhci: fix dma memory leak in sdhci_pre_req() Jiri Slaby
2015-10-06 9:01 ` Jiri Slaby
2015-10-17 23:50 ` Greg KH [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=20151017235005.GF9038@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=haibo.chen@freescale.com \
--cc=jslaby@suse.cz \
--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 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.