From: Jean Delvare <jdelvare@suse.de>
To: Doug Anderson <dianders@chromium.org>
Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
dri-devel@lists.freedesktop.org,
LKML <linux-kernel@vger.kernel.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Andrew Morton <akpm@linux-foundation.org>,
YueHaibing <yuehaibing@huawei.com>
Subject: Re: [PATCH RESEND] drm/display: Drop obsolete dependency on COMPILE_TEST
Date: Tue, 18 Jun 2024 09:20:48 +0200 [thread overview]
Message-ID: <20240618092048.510215ff@endymion.delvare> (raw)
In-Reply-To: <CAD=FV=X4qVDTOdMFQeEiJi2DD=tuEj66vP35XQKrSj5-r_YADQ@mail.gmail.com>
Hi Doug,
On Mon, 17 Jun 2024 19:12:05 -0700, Doug Anderson wrote:
> On Mon, Jun 17, 2024 at 3:26 PM Dmitry Baryshkov
> <dmitry.baryshkov@linaro.org> wrote:
> >
> > On Mon, Jun 17, 2024 at 08:18:14PM GMT, Jean Delvare wrote:
> > > The major difference is that one can't possibly enable ARCH_QCOM if
> > > building on X86 for example. Therefore COMPILE_TEST is the only way to
> > > let everyone (including randconfig/allmodconfig build farms) test-build
> > > your code.
> > >
> > > On the other hand, if you want to test-build drm_dp_aux_bus, you can
> > > simply enable OF, because it is available on all architectures and
> > > doesn't depend on anything. No need for COMPILE_TEST.
> >
> > I'd probably let Doug respond, what was his intention.
>
> Is this me? This looks like a straight revert of commit 876271118aa4
> ("drm/display: Fix build error without CONFIG_OF")
>
> I don't personally have anything against removing COMPILE_TEST for
> this given that I wasn't the one who added it, but make sure it's not
> going to cause randconfig issues.
Thanks for pointing this commit to my attention, I wasn't aware. This
means that my proposed patch is incomplete and would indeed break
randconfig. I'll send a v2.
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2024-06-18 7:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 8:30 Jean Delvare
2024-06-17 9:57 ` Dmitry Baryshkov
2024-06-17 11:23 ` Jean Delvare
2024-06-17 11:55 ` Dmitry Baryshkov
2024-06-17 18:18 ` Jean Delvare
2024-06-17 22:26 ` Dmitry Baryshkov
2024-06-18 2:12 ` Doug Anderson
2024-06-18 7:20 ` Jean Delvare [this message]
2024-06-18 8:53 ` Dmitry Baryshkov
-- strict thread matches above, loose matches on Subject: below --
2023-12-02 20:32 Jean Delvare
2023-12-04 9:17 ` Javier Martinez Canillas
2023-01-27 10:59 Jean Delvare
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=20240618092048.510215ff@endymion.delvare \
--to=jdelvare@suse.de \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=daniel@ffwll.ch \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.de \
--cc=yuehaibing@huawei.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®