dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Alex Deucher <alexdeucher@gmail.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: "Daniel Vetter" <daniel.vetter@ffwll.ch>,
	LKML <linux-kernel@vger.kernel.org>,
	"Maling list - DRI developers" <dri-devel@lists.freedesktop.org>,
	"Christian König" <christian.koenig@amd.com>,
	linux-media <linux-media@vger.kernel.org>
Subject: Re: [PATCH] dma-buf: Improve CONFIG_DMABUF_MOVE_NOTIFY help text
Date: Wed, 25 Mar 2020 14:43:07 -0400	[thread overview]
Message-ID: <CADnq5_M+2afonwdY2-8kdzx-_aidWPZ4OxwxRY31odPOJ8togg@mail.gmail.com> (raw)
In-Reply-To: <20200324125442.21983-1-geert+renesas@glider.be>

On Tue, Mar 24, 2020 at 8:54 AM Geert Uytterhoeven
<geert+renesas@glider.be> wrote:
>
> Improve the help text for the CONFIG_DMABUF_MOVE_NOTIFY symbol by:
>   1. Removing duplicated single quotes,
>   2. Adding a missing subject,
>   3. Fixing a misspelling of "yet",
>   4. Wrapping long lines.
>
> Fixes: bb42df4662a44765 ("dma-buf: add dynamic DMA-buf handling v15")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>

Applied.  Thanks!

Alex

> ---
>  drivers/dma-buf/Kconfig | 11 ++++++-----
>  1 file changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/dma-buf/Kconfig b/drivers/dma-buf/Kconfig
> index ef73b678419c6d86..9626673f1d83ae64 100644
> --- a/drivers/dma-buf/Kconfig
> +++ b/drivers/dma-buf/Kconfig
> @@ -43,11 +43,12 @@ config DMABUF_MOVE_NOTIFY
>         bool "Move notify between drivers (EXPERIMENTAL)"
>         default n
>         help
> -         Don''t pin buffers if the dynamic DMA-buf interface is available on both the
> -         exporter as well as the importer. This fixes a security problem where
> -         userspace is able to pin unrestricted amounts of memory through DMA-buf.
> -         But marked experimental because we don''t jet have a consistent execution
> -         context and memory management between drivers.
> +         Don't pin buffers if the dynamic DMA-buf interface is available on
> +         both the exporter as well as the importer. This fixes a security
> +         problem where userspace is able to pin unrestricted amounts of memory
> +         through DMA-buf.
> +         This is marked experimental because we don't yet have a consistent
> +         execution context and memory management between drivers.
>
>  config DMABUF_SELFTESTS
>         tristate "Selftests for the dma-buf interfaces"
> --
> 2.17.1
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2020-03-25 18:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-24 12:54 [PATCH] dma-buf: Improve CONFIG_DMABUF_MOVE_NOTIFY help text Geert Uytterhoeven
2020-03-25 18:43 ` Alex Deucher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-03-24 13:02 Koenig, Christian

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=CADnq5_M+2afonwdY2-8kdzx-_aidWPZ4OxwxRY31odPOJ8togg@mail.gmail.com \
    --to=alexdeucher@gmail.com \
    --cc=christian.koenig@amd.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=geert+renesas@glider.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@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).