All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <swboyd@chromium.org>
To: Abhinav Kumar <quic_abhinavk@quicinc.com>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	 Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>
Cc: David Airlie <airlied@linux.ie>,
	linux-arm-msm@vger.kernel.org, freedreno@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/3] drm/msm: loop over encoders using drm_for_each_encoder()
Date: Tue, 5 Apr 2022 21:01:30 -0700	[thread overview]
Message-ID: <CAE-0n51ayjyfEdne_=R6FU-3+O91JiYz-GRg2C7jeXB_9HTiRA@mail.gmail.com> (raw)
In-Reply-To: <20220405235059.359738-3-dmitry.baryshkov@linaro.org>

Quoting Dmitry Baryshkov (2022-04-05 16:50:58)
> Rather than manually looping over encoders array, use standard
> drm_for_each_encoder() macro.
>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---

Reviewed-by: Stephen Boyd <swboyd@chromium.org>

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <swboyd@chromium.org>
To: Abhinav Kumar <quic_abhinavk@quicinc.com>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>
Cc: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
	linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
	freedreno@lists.freedesktop.org
Subject: Re: [PATCH 2/3] drm/msm: loop over encoders using drm_for_each_encoder()
Date: Tue, 5 Apr 2022 21:01:30 -0700	[thread overview]
Message-ID: <CAE-0n51ayjyfEdne_=R6FU-3+O91JiYz-GRg2C7jeXB_9HTiRA@mail.gmail.com> (raw)
In-Reply-To: <20220405235059.359738-3-dmitry.baryshkov@linaro.org>

Quoting Dmitry Baryshkov (2022-04-05 16:50:58)
> Rather than manually looping over encoders array, use standard
> drm_for_each_encoder() macro.
>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---

Reviewed-by: Stephen Boyd <swboyd@chromium.org>

  reply	other threads:[~2022-04-06  4:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-05 23:50 [PATCH 0/3] drm/msm: remove DRM mode setting object arrays Dmitry Baryshkov
2022-04-05 23:50 ` Dmitry Baryshkov
2022-04-05 23:50 ` [PATCH 1/3] drm/msm/dpu: remove manual destruction of DRM objects Dmitry Baryshkov
2022-04-05 23:50   ` Dmitry Baryshkov
2022-04-06  4:01   ` Stephen Boyd
2022-04-06  4:01     ` Stephen Boyd
2022-04-05 23:50 ` [PATCH 2/3] drm/msm: loop over encoders using drm_for_each_encoder() Dmitry Baryshkov
2022-04-05 23:50   ` Dmitry Baryshkov
2022-04-06  4:01   ` Stephen Boyd [this message]
2022-04-06  4:01     ` Stephen Boyd
2022-04-05 23:50 ` [PATCH 3/3] drm/msm: don't store created planes, connectors and encoders Dmitry Baryshkov
2022-04-05 23:50   ` Dmitry Baryshkov
2022-04-06  4:03   ` Stephen Boyd
2022-04-06  4:03     ` Stephen Boyd
2022-04-06 10:01     ` Dmitry Baryshkov
2022-04-06 10:01       ` Dmitry Baryshkov

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='CAE-0n51ayjyfEdne_=R6FU-3+O91JiYz-GRg2C7jeXB_9HTiRA@mail.gmail.com' \
    --to=swboyd@chromium.org \
    --cc=airlied@linux.ie \
    --cc=bjorn.andersson@linaro.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=quic_abhinavk@quicinc.com \
    --cc=robdclark@gmail.com \
    --cc=sean@poorly.run \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.