From: Greg KH <gregkh@linuxfoundation.org>
To: Amit Pundir <amit.pundir@linaro.org>
Cc: Stable <stable@vger.kernel.org>
Subject: Re: [PATCH for-4.9 0/7] Stable commits picked up from lede project
Date: Tue, 27 Jun 2017 13:08:16 +0200 [thread overview]
Message-ID: <20170627110816.GD10609@kroah.com> (raw)
In-Reply-To: <1498464091-26753-1-git-send-email-amit.pundir@linaro.org>
On Mon, Jun 26, 2017 at 01:31:24PM +0530, Amit Pundir wrote:
> Hi Greg,
>
> For your consideration, stable commits taken from lede source tree
> https://git.lede-project.org/?p=source.git for 4.9.y.
>
> Cherry-picked and build tested on Linux 4.9.34 for
> ARCH=arm/arm64/i386/x86_64/mips + allmodconfig.
All now queued up. Also, some of these had to go into 4.11-stable, and
older stable trees. You never want to apply a patch to an old stable
release and miss a newer one, that will just confuse users if they move
forward...
thanks,
greg k-h
next prev parent reply other threads:[~2017-06-27 11:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 8:01 [PATCH for-4.9 0/7] Stable commits picked up from lede project Amit Pundir
2017-06-26 8:01 ` [PATCH for-4.9 1/7] of: Add check to of_scan_flat_dt() before accessing initial_boot_params Amit Pundir
2017-06-26 8:01 ` [PATCH for-4.9 2/7] mtd: spi-nor: fix spansion quad enable Amit Pundir
2017-06-26 8:01 ` [PATCH for-4.9 3/7] rt2x00: avoid introducing a USB dependency in the rt2x00lib module Amit Pundir
2017-06-27 11:03 ` Greg KH
2017-06-26 8:01 ` [PATCH for-4.9 4/7] net: phy: Initialize mdio clock at probe function Amit Pundir
2017-06-26 8:01 ` [PATCH for-4.9 5/7] dmaengine: bcm2835: Fix cyclic DMA period splitting Amit Pundir
2017-06-26 8:01 ` [PATCH for-4.9 6/7] spi: double time out tolerance Amit Pundir
2017-06-26 11:54 ` Mark Brown
2017-06-26 8:01 ` [PATCH for-4.9 7/7] net: phy: fix marvell phy status reading Amit Pundir
2017-06-27 11:08 ` Greg KH [this message]
2017-06-27 11:12 ` [PATCH for-4.9 0/7] Stable commits picked up from lede project Amit Pundir
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=20170627110816.GD10609@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=amit.pundir@linaro.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 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.