From: "Heiko Stübner" <heiko@sntech.de>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
hjc@rock-chips.com, kernel-team@android.com,
dri-devel@lists.freedesktop.org, geert+renesas@glider.be,
airlied@linux.ie, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
daniel@ffwll.ch
Subject: Re: [PATCH v2] drm/rockchip: cdn-dp-core: Fix cdn_dp_resume unused warning
Date: Tue, 21 Sep 2021 21:29:41 +0200 [thread overview]
Message-ID: <2662894.r5Zzv63rEP@diego> (raw)
In-Reply-To: <mhng-4c5264da-5502-4947-b32d-e9008a79ee90@palmerdabbelt-glaptop>
Hi,
Am Dienstag, 21. September 2021, 17:04:10 CEST schrieb Palmer Dabbelt:
> On Tue, 21 Sep 2021 02:12:17 PDT (-0700), heiko@sntech.de wrote:
> > On Fri, 10 Sep 2021 20:43:18 -0700, Palmer Dabbelt wrote:
> >> cdn_dp_resume is only used under PM_SLEEP, and now that it's static an
> >> unused function warning is triggered undner !PM_SLEEP. This marks the
> >> function as possibly unused, to avoid triggering compiler warnings.
> >
> > Applied, thanks!
> >
> > [1/1] drm/rockchip: cdn-dp-core: Fix cdn_dp_resume unused warning
> > commit: f7c57a4566115657c16fd6603b6ef8a21bae5194
>
> I'm not quite sure where that lives, but is it applied on top of
> something or is it merged from the tag? Like I said a bit below this in
> the original patch, this has started to break the build for me and I'd
> like to pull it in as soon as possible.
The patch now lives here:
https://cgit.freedesktop.org/drm/drm-misc/commit/?h=drm-misc-fixes&id=f7c57a4566115657c16fd6603b6ef8a21bae5194
This is the drm-misc tree, with the patch living in the drm-misc-fixes
branch, which targets the current rc-kernels.
drm-misc-* moves into the core drm tree and from there on to Linus.
Hope that helps
Heiko
prev parent reply other threads:[~2021-09-21 19:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-11 3:43 [PATCH v2] drm/rockchip: cdn-dp-core: Fix cdn_dp_resume unused warning Palmer Dabbelt
2021-09-21 9:12 ` Heiko Stuebner
2021-09-21 15:04 ` Palmer Dabbelt
2021-09-21 19:29 ` Heiko Stübner [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=2662894.r5Zzv63rEP@diego \
--to=heiko@sntech.de \
--cc=airlied@linux.ie \
--cc=arnd@arndb.de \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert+renesas@glider.be \
--cc=hjc@rock-chips.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=palmer@dabbelt.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