Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Gilad Ben-Yossef <gilad@benyossef.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Stable <stable@vger.kernel.org>
Subject: Re: request for 4.14-stable: 293edc27f8bc ("stating: ccree: revert "staging: ccree: fix leak of import() after init()"")
Date: Thu, 11 Apr 2019 10:36:19 -0400	[thread overview]
Message-ID: <20190411143619.GJ11568@sasha-vm> (raw)
In-Reply-To: <CADVatmOGQQmLQs7_3KkBpM8vOgVUREN+5qCgEFGvr4H56_x1kQ@mail.gmail.com>

On Thu, Apr 11, 2019 at 12:57:38PM +0100, Sudip Mukherjee wrote:
>On Thu, Apr 11, 2019 at 12:40 PM Gilad Ben-Yossef <gilad@benyossef.com> wrote:
>>
>> Hi,
>>
>> On Mon, Apr 8, 2019 at 5:09 PM Sasha Levin <sashal@kernel.org> wrote:
>> >
>> > On Sun, Apr 07, 2019 at 04:40:08PM +0100, Sudip Mukherjee wrote:
>> > >Hi Greg,
>> > >
>> > >This was missing in 4.14-stable. Please apply to your queue.
>> >
>> > Gilad, could you ack the backport?
>> >
>>
>> There is nothing wrong in the backport itself but It does not seem
>> useful since there were many changes on top if this one since the
>> driver matured out of the staging area, so I wonder if it is useful to
>> take it...
>
>It matured out of staging from v4.17 and if I consider v4.14-stable,
>it is still in staging. :)

I've queued it up, thank you.

--
Thanks,
Sasha

      reply	other threads:[~2019-04-11 14:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-07 15:40 request for 4.14-stable: 293edc27f8bc ("stating: ccree: revert "staging: ccree: fix leak of import() after init()"") Sudip Mukherjee
2019-04-08 14:09 ` Sasha Levin
2019-04-11 11:40   ` Gilad Ben-Yossef
2019-04-11 11:57     ` Sudip Mukherjee
2019-04-11 14:36       ` Sasha Levin [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=20190411143619.GJ11568@sasha-vm \
    --to=sashal@kernel.org \
    --cc=gilad@benyossef.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    /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