public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Zhenyu Wang <zhenyuw@linux.intel.com>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	stable@vger.kernel.org, Colin Ian King <colin.king@canonical.com>,
	Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: request for 4.14-stable: ffdf16edfbbe ("drm/i915/gvt: fix memory leak of a cmd_entry struct on error exit path")
Date: Thu, 1 Nov 2018 12:00:30 -0400	[thread overview]
Message-ID: <20181101160030.GB194472@sasha-vm> (raw)
In-Reply-To: <20181101023012.GO31661@zhen-hp.sh.intel.com>

On Thu, Nov 01, 2018 at 10:30:12AM +0800, Zhenyu Wang wrote:
>On 2018.10.31 10:38:19 -0400, Sasha Levin wrote:
>> On Tue, Oct 23, 2018 at 10:44:45AM +0100, Sudip Mukherjee wrote:
>> > Hi Greg,
>> >
>> > This was not marked for stable but seems it should be in stable.
>> > Please apply to your queue of 4.14-stable.
>>
>> Hi Sudip,
>>
>> The i915 maintainers want to explicitly tag patches for stable, and
>> avoid backporting non-tagged patches.
>>
>> I can queue it up if one of the maintainers will ack it.
>>
>
>It looks good to me for backport.
>
>Acked-by: Zhenyu Wang <zhenyuw@linux.intel.com>

Queued up, thanks!

--
Thanks,
Sasha

      reply	other threads:[~2018-11-02  1:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-23  9:44 request for 4.14-stable: ffdf16edfbbe ("drm/i915/gvt: fix memory leak of a cmd_entry struct on error exit path") Sudip Mukherjee
2018-10-31 14:38 ` Sasha Levin
2018-11-01  2:30   ` Zhenyu Wang
2018-11-01 16:00     ` 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=20181101160030.GB194472@sasha-vm \
    --to=sashal@kernel.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=colin.king@canonical.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=zhenyuw@linux.intel.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