From: Qian Cai <cai@lca.pw>
To: Maxime Ripard <maxime.ripard@anandra.org>
Cc: airlied@linux.ie, daniel@ffwll.ch,
dri-devel@lists.freedesktop.org, emil.l.velikov@gmail.com,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
maarten.lankhorst@linux.intel.com, michal.lkml@markovi.net,
mripard@kernel.org, sean@poorly.run,
yamada.masahiro@socionext.com
Subject: Re: [RFC PATCH] gpu: no need to compile drm/ if CONFIG_DRM=n
Date: Wed, 11 Sep 2019 13:41:33 -0400 [thread overview]
Message-ID: <08E1DEDD-D82F-41C1-966B-ECCE445C8FA1@lca.pw> (raw)
In-Reply-To: <CAO4ZVTMUMKMOqef5yV=5bwHLXLMsNtTegGGMkw0GbFaDHvrV6g@mail.gmail.com>
> On Sep 11, 2019, at 1:37 PM, Maxime Ripard <maxime.ripard@anandra.org> wrote:
>
> Hi,
>
> Le mer. 11 sept. 2019 à 19:35, Qian Cai <cai@lca.pw> a écrit :
> The commit c0e09200dc08 ("drm: reorganise drm tree to be more future
> proof.") changed the behavior from only compiling drm/ if CONFIG_DRM=y
> to always compiling drm/. This restores the behavior, so people don't
> need to waste time compiling stuff they don't need.
>
> Fixes: c0e09200dc08 ("drm: reorganise drm tree to be more future proof.")
>
> You are missing your signed-off-by
That is intentional because this is a RFC patch to gather the feedback as I am no
expert in DRM and may miss something important.
Once people are happy with it, I plan to send a formal patch with Signed-off-by.
next prev parent reply other threads:[~2019-09-11 17:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 17:34 Qian Cai
[not found] ` <CAO4ZVTMUMKMOqef5yV=5bwHLXLMsNtTegGGMkw0GbFaDHvrV6g@mail.gmail.com>
2019-09-11 17:41 ` Qian Cai [this message]
2019-09-12 0:52 ` Masahiro Yamada
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=08E1DEDD-D82F-41C1-966B-ECCE445C8FA1@lca.pw \
--to=cai@lca.pw \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=maxime.ripard@anandra.org \
--cc=michal.lkml@markovi.net \
--cc=mripard@kernel.org \
--cc=sean@poorly.run \
--cc=yamada.masahiro@socionext.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
all inboxes | Powered by JetHome®