From: Doug Anderson <dianders@chromium.org>
To: Sui Jingfeng <sui.jingfeng@linux.dev>
Cc: 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>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Subject: Re: [PATCH v2] drm/debugfs: Drop conditionals around of_node pointers
Date: Wed, 1 May 2024 09:09:07 -0700 [thread overview]
Message-ID: <CAD=FV=XdQjEM05Jw7iVVcHbJ9oqy8qQeH66oxf2g304QKDaL=Q@mail.gmail.com> (raw)
In-Reply-To: <20240501051323.805076-1-sui.jingfeng@linux.dev>
Hi,
On Tue, Apr 30, 2024 at 10:13 PM Sui Jingfeng <sui.jingfeng@linux.dev> wrote:
>
> Having conditional around the of_node pointer of the drm_bridge structure
> is not necessary anymore, since drm_bridge structure always has the of_node
> member since the commit d8dfccde2709 ("drm/bridge: Drop conditionals around
> of_node pointers").
>
> So drop the conditional, please also note that this patch is following the
> convention used by driver core, see commit c9e358dfc4a8 ("driver-core:
> remove conditionals around devicetree pointers").
>
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> Signed-off-by: Sui Jingfeng <sui.jingfeng@linux.dev>
> ---
> v2: Update commit message
> ---
> drivers/gpu/drm/drm_debugfs.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Pushed to drm-misc-next:
235e60653f8d drm/debugfs: Drop conditionals around of_node pointers
-Doug
prev parent reply other threads:[~2024-05-01 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 5:13 [PATCH v2] drm/debugfs: Drop conditionals around of_node pointers Sui Jingfeng
2024-05-01 16:09 ` Doug Anderson [this message]
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='CAD=FV=XdQjEM05Jw7iVVcHbJ9oqy8qQeH66oxf2g304QKDaL=Q@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--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=sui.jingfeng@linux.dev \
--cc=tzimmermann@suse.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).