From: Greg KH <gregkh@linuxfoundation.org>
To: Amit Pundir <amit.pundir@linaro.org>
Cc: Stable <stable@vger.kernel.org>
Subject: Re: [PATCH for-4.14.y 0/5] Stable commits picked up from lede project
Date: Tue, 17 Jul 2018 10:13:02 +0200 [thread overview]
Message-ID: <20180717081302.GA16462@kroah.com> (raw)
In-Reply-To: <1531814914-19191-1-git-send-email-amit.pundir@linaro.org>
On Tue, Jul 17, 2018 at 01:38:29PM +0530, Amit Pundir wrote:
> Hi Greg,
Welcome back! :)
> For your consideration, stable commits picked up from lede source
> tree https://git.lede-project.org/?p=source.git for 4.14.y.
>
> Cherry-picked and build tested on Linux v4.14.55.
Why only 4.14? These aren't needed further back? Just checking...
thanks,
greg k-h
next prev parent reply other threads:[~2018-07-17 8:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 8:08 [PATCH for-4.14.y 0/5] Stable commits picked up from lede project Amit Pundir
2018-07-17 8:08 ` [PATCH for-4.14.y 1/5] PCI: exynos: Fix a potential init_clk_resources NULL pointer dereference Amit Pundir
2018-07-17 8:08 ` [PATCH for-4.14.y 2/5] crypto: crypto4xx - remove bad list_del Amit Pundir
2018-07-17 8:08 ` [PATCH for-4.14.y 3/5] crypto: crypto4xx - fix crypto4xx_build_pdr, crypto4xx_build_sdr leak Amit Pundir
2018-07-17 8:08 ` [PATCH for-4.14.y 4/5] bcm63xx_enet: correct clock usage Amit Pundir
2018-07-17 8:08 ` [PATCH for-4.14.y 5/5] bcm63xx_enet: do not write to random DMA channel on BCM6345 Amit Pundir
2018-07-17 8:13 ` Greg KH [this message]
2018-07-17 8:24 ` [PATCH for-4.14.y 0/5] Stable commits picked up from lede project Amit Pundir
2018-07-18 10:13 ` Greg Kroah-Hartman
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=20180717081302.GA16462@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.