From: Heiko Stuebner <heiko@sntech.de>
To: linux-kernel@vger.kernel.org, Thomas Hebb <tommyhebb@gmail.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
stable@vger.kernel.org, linux-rockchip@lists.infradead.org,
Andrzej Hajda <a.hajda@samsung.com>,
dri-devel@lists.freedesktop.org, David Airlie <airlied@linux.ie>,
Sandy Huang <hjc@rock-chips.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RESEND PATCH] drm/rockchip: dsi: remove extra component_del() call
Date: Fri, 28 May 2021 20:09:45 +0200 [thread overview]
Message-ID: <162222530163.2887132.8458225826944784611.b4-ty@sntech.de> (raw)
In-Reply-To: <201385acb0eeb5dfb037afdc6a94bfbcdab97f99.1618797778.git.tommyhebb@gmail.com>
On Sun, 18 Apr 2021 19:03:04 -0700, Thomas Hebb wrote:
> commit cf6d100dd238 ("drm/rockchip: dsi: add dual mipi support") added
> this devcnt field and call to component_del(). However, these both
> appear to be erroneous changes left over from an earlier version of the
> patch. In the version merged, nothing ever modifies devcnt, meaning
> component_del() runs unconditionally and in addition to the
> component_del() calls in dw_mipi_dsi_rockchip_host_detach(). The second
> call fails to delete anything and produces a warning in dmesg.
>
> [...]
Applied, thanks!
[1/1] drm/rockchip: dsi: remove extra component_del() call
commit: b354498bbe65c917d521b3b56317ddc9ab217425
Best regards,
--
Heiko Stuebner <heiko@sntech.de>
next prev parent reply other threads:[~2021-05-28 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 2:03 [RESEND PATCH] drm/rockchip: dsi: remove extra component_del() call Thomas Hebb
2021-05-28 18:09 ` Heiko Stuebner [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-13 20:57 Thomas Hebb
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=162222530163.2887132.8458225826944784611.b4-ty@sntech.de \
--to=heiko@sntech.de \
--cc=a.hajda@samsung.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=hjc@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=stable@vger.kernel.org \
--cc=tommyhebb@gmail.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).