dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Sun, Jing A" <jing.a.sun@intel.com>,
	"airlied@linux.ie" <airlied@linux.ie>,
	"Vetter, Daniel" <daniel.vetter@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	dri-devel@lists.freedesktop.org, Takashi Iwai <tiwai@suse.de>,
	a.hajda@samsung.com, Thierry Reding <treding@nvidia.com>
Subject: Re: [PATCH]"drm: change DRM_MIPI_DSI module type from "bool" to "tristate".
Date: Mon, 10 Oct 2016 11:28:31 +0300	[thread overview]
Message-ID: <87h98ktxow.fsf@intel.com> (raw)
In-Reply-To: <C5AB7166D8288A4698415C150FD56DBA22E373B0@SHSMSX103.ccr.corp.intel.com>

On Mon, 10 Oct 2016, "Sun, Jing A" <jing.a.sun@intel.com> wrote:
> Dear Maintainers,
>
> Please kindly review my patch as below. It's based on the mainline branch.
>
> From b401009f79883ac5e9d41525c9d54b800ece2e22 Mon Sep 17 00:00:00 2001
> From: Jing SUN <jing.a.sun@intel.com>
> Date: Mon, 10 Oct 2016 14:06:54 +0800
> Subject: [PATCH 1/1] drm: change DRM_MIPI_DSI module type from "bool" to
>  "tristate".
>
> A lot of drm driver modules, which are designed
> to be loadable, select DRM_MIPI_DSI, while that
> being "bool" prevents those from getting reloaded.

You're missing some lists and people from distribution, added now.

See the discussion starting at [1]. I don't know if anything has
happened since then. Takashi?

BR,
Jani.


[1] http://lkml.kernel.org/r/s5hh9bhvj7j.wl-tiwai@suse.de


>
> Signed-off-by: Jing SUN <jing.a.sun@intel.com>
> ---
>  drivers/gpu/drm/Kconfig | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/Kconfig b/drivers/gpu/drm/Kconfig
> index fc35731..67668a0 100644
> --- a/drivers/gpu/drm/Kconfig
> +++ b/drivers/gpu/drm/Kconfig
> @@ -22,7 +22,7 @@ menuconfig DRM
>  	  (/dev/agpgart) support if it is available for your platform.
>  
>  config DRM_MIPI_DSI
> -	bool
> +	tristate
>  	depends on DRM
>  
>  config DRM_DP_AUX_CHARDEV

-- 
Jani Nikula, Intel Open Source Technology Center

       reply	other threads:[~2016-10-10  8:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <C5AB7166D8288A4698415C150FD56DBA22E373B0@SHSMSX103.ccr.corp.intel.com>
2016-10-10  8:28 ` Jani Nikula [this message]
2016-10-10  9:57   ` [PATCH]"drm: change DRM_MIPI_DSI module type from "bool" to "tristate" Takashi Iwai
2016-10-11  8:40     ` Sun, Jing A
2016-10-11  9:17       ` Andrzej Hajda
2016-10-11  9:33       ` Jani Nikula
2016-10-11  9:53         ` Andrzej Hajda
2016-10-12  3:08           ` Sun, Jing A
2016-10-12  6:51             ` Daniel Vetter
2016-10-12  9:04               ` Sun, Jing A
2016-10-12 10:52                 ` Jani Nikula
2016-10-12 11:28         ` Emil Velikov
2016-10-12 14:28           ` Jani Nikula
2016-10-20 13:20             ` Andrzej Hajda
2016-10-20 13:44               ` Jani Nikula
2016-10-21 12:19                 ` Daniel Vetter

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=87h98ktxow.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=a.hajda@samsung.com \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jing.a.sun@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tiwai@suse.de \
    --cc=treding@nvidia.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;
as well as URLs for NNTP newsgroup(s).