mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oleksandr Tymoshenko <ovt@google.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	linux-kernel@vger.kernel.org
Cc: Oleksandr Tymoshenko <ovt@google.com>
Subject: [PATCH] dma-buf: add option text so it can be enabled by users
Date: Thu,  5 May 2022 04:50:01 +0000	[thread overview]
Message-ID: <20220505045001.363548-1-ovt@google.com> (raw)

This reverts commit 3b32a592ea6e4 ("dma-buf: drop option text so users
don't select it.") to allow users select DMA_SHARED_BUFFER option
explicitly. This is required for out-of-tree modules that depend on
dma-buf functionality, for instance drivers that rely on Google's Gasket
framework.

On general-purpose Linux systems the option is usually implicitely
enabled in the default kernel config by subsystems that use it but
systems with smaller kernel footprint have to rely on side-effects
from enabling unrelated options to get dma-buf functionality built.

Signed-off-by: Oleksandr Tymoshenko <ovt@google.com>
---
 drivers/base/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/base/Kconfig b/drivers/base/Kconfig
index 6f04b831a5c0..108bf9b38ce6 100644
--- a/drivers/base/Kconfig
+++ b/drivers/base/Kconfig
@@ -198,7 +198,7 @@ config SOC_BUS
 source "drivers/base/regmap/Kconfig"
 
 config DMA_SHARED_BUFFER
-	bool
+	bool "Buffer framework to be shared between drivers"
 	default n
 	select IRQ_WORK
 	help
-- 
2.36.0.464.gb9c8b46e94-goog


             reply	other threads:[~2022-05-05  4:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05  4:50 Oleksandr Tymoshenko [this message]
2022-05-05 12:03 ` Greg Kroah-Hartman
2022-05-09  6:39 ` Christoph Hellwig

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=20220505045001.363548-1-ovt@google.com \
    --to=ovt@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@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

all inboxes | Powered by JetHome®