stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <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: Wed, 18 Jul 2018 12:13:56 +0200	[thread overview]
Message-ID: <20180718101356.GA31667@kroah.com> (raw)
In-Reply-To: <CAMi1Hd2_MLShPpNEfzzh5H--hVO+v6-weVqn4t=6OdXBDiDhGQ@mail.gmail.com>

On Tue, Jul 17, 2018 at 01:54:49PM +0530, Amit Pundir wrote:
> On Tue, 17 Jul 2018 at 13:43, Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Tue, Jul 17, 2018 at 01:38:29PM +0530, Amit Pundir wrote:
> > > Hi Greg,
> >
> > Welcome back!  :)
> 
> Sorry I've been sitting on few of these for a long time. Got stuck in
> some other work items.
> 
> >
> > > 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...
> 
> Sent few for 4.9 as well. Couple of these 4.14 ones are cleanly
> applied on 4.9.y as well but they are not present on Lede's 4.9 tree,
> so I don't know if they are useful for 4.9.y as such, so I skipped
> them over.

Well, it looks like they are relevant there, as well as for 4.4.y, so
I've applied them all over the place.  Please be more "complete" if at
all possible next time.

thanks,

greg k-h

      reply	other threads:[~2018-07-18 10:51 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 ` [PATCH for-4.14.y 0/5] Stable commits picked up from lede project Greg KH
2018-07-17  8:24   ` Amit Pundir
2018-07-18 10:13     ` Greg Kroah-Hartman [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=20180718101356.GA31667@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).