From: Johan Hovold <johan@kernel.org>
To: gregkh@linuxfoundation.org
Cc: johan@kernel.org, linus.walleij@linaro.org,
stable@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: Patch "gpio: sysfs: fix memory leaks and device hotplug" has been added to the 3.14-stable tree
Date: Fri, 15 May 2015 12:07:54 +0200 [thread overview]
Message-ID: <20150515100754.GA13976@localhost> (raw)
In-Reply-To: <1431655051129115@kroah.com>
On Thu, May 14, 2015 at 06:57:31PM -0700, Greg Kroah-Hartman wrote:
>
> This is a note to let you know that I've just added the patch titled
>
> gpio: sysfs: fix memory leaks and device hotplug
>
> to the 3.14-stable tree which can be found at:
> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
> The filename of the patch is:
> gpio-sysfs-fix-memory-leaks-and-device-hotplug.patch
> and it can be found in the queue-3.14 subdirectory.
>
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@vger.kernel.org> know about it.
Your backport looks good, but this one depends on commit 01cca93a9491
("gpio: unregister gpiochip device before removing it") which needs to
be backported as well. I tried to convey this in the stable tag:
Cc: stable <stable@vger.kernel.org> # v2.6.27: 01cca93a9491
I'll respond to this message with a tested backport of both patches.
Thanks,
Johan
next prev parent reply other threads:[~2015-05-15 10:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 1:57 Patch "gpio: sysfs: fix memory leaks and device hotplug" has been added to the 3.14-stable tree gregkh
2015-05-15 10:07 ` Johan Hovold [this message]
2015-05-15 10:10 ` [PATCH-3.14 1/2] gpio: unregister gpiochip device before removing it Johan Hovold
2015-05-15 10:10 ` [PATCH-3.14 2/2] gpio: sysfs: fix memory leaks and device hotplug Johan Hovold
2015-05-15 15:44 ` Patch "gpio: sysfs: fix memory leaks and device hotplug" has been added to the 3.14-stable tree Greg KH
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=20150515100754.GA13976@localhost \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.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