All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org,
	Sean Paul <seanpaul@chromium.org>,
	stable@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Free write_buf that we allocated with kzalloc.
Date: Thu, 23 Aug 2018 15:48:56 -0700	[thread overview]
Message-ID: <20180823224856.GL2190@intel.com> (raw)
In-Reply-To: <153506314244.20928.14372256445570563760@skylake-alporthouse-com>

On Thu, Aug 23, 2018 at 11:25:42PM +0100, Chris Wilson wrote:
> Quoting Rodrigo Vivi (2018-08-23 21:51:36)
> > We use kzalloc to allocate the write_buf that we use for
> > i2c transfer on hdcp write. But it seems that we are forgetting
> > to free the memory that is not needed after i2c transfer is
> > completed.
> > 
> > Reported-by: Brian J Wood <brian.j.wood@intel.com>
> > Fixes: 2320175feb74 ("drm/i915: Implement HDCP for HDMI")
> > Cc: Ramalingam C <ramalingam.c@intel.com>
> > Cc: Sean Paul <seanpaul@chromium.org>
> > Cc: Jani Nikula <jani.nikula@linux.intel.com>
> > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > Cc: <stable@vger.kernel.org> # v4.17+
> > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>

thanks. pushed to dinq.

> -Chris
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2018-08-23 22:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-23 20:51 [PATCH] drm/i915: Free write_buf that we allocated with kzalloc Rodrigo Vivi
2018-08-23 20:51 ` Rodrigo Vivi
2018-08-23 21:16 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-08-23 22:03 ` ✓ Fi.CI.IGT: " Patchwork
2018-08-23 22:25 ` [Intel-gfx] [PATCH] " Chris Wilson
2018-08-23 22:25   ` Chris Wilson
2018-08-23 22:48   ` Rodrigo Vivi [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=20180823224856.GL2190@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=seanpaul@chromium.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.