From: Dan Carpenter <dan.carpenter@oracle.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: devel@driverdev.osuosl.org, arve@android.com,
stable@vger.kernel.org, riandrews@android.com,
labbott@redhat.com, sumit.semwal@linaro.org
Subject: Re: [PATCH v3 1/1] staging: ion: Prevent incorrect reference counting behavour
Date: Fri, 26 Nov 2021 13:36:22 +0300 [thread overview]
Message-ID: <20211126103621.GP6514@kadam> (raw)
In-Reply-To: <20211126103335.880816-1-lee.jones@linaro.org>
On Fri, Nov 26, 2021 at 10:33:35AM +0000, Lee Jones wrote:
> Supply additional checks in order to prevent unexpected results.
>
> Fixes: b892bf75b2034 ("ion: Switch ion to use dma-buf")
> Suggested-by: Dan Carpenter <dan.carpenter@oracle.com>
> Signed-off-by: Lee Jones <lee.jones@linaro.org>
> ---
> Destined for v4.4.y and v4.9.y
Thanks!
regards,
dan carpenter
next prev parent reply other threads:[~2021-11-26 10:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 10:33 [PATCH v3 1/1] staging: ion: Prevent incorrect reference counting behavour Lee Jones
2021-11-26 10:36 ` Dan Carpenter [this message]
2021-11-27 11:57 ` Greg KH
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=20211126103621.GP6514@kadam \
--to=dan.carpenter@oracle.com \
--cc=arve@android.com \
--cc=devel@driverdev.osuosl.org \
--cc=labbott@redhat.com \
--cc=lee.jones@linaro.org \
--cc=riandrews@android.com \
--cc=stable@vger.kernel.org \
--cc=sumit.semwal@linaro.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