From: "Heiko Stübner" <heiko@sntech.de>
To: Douglas Anderson <dianders@chromium.org>
Cc: Elaine Zhang <zhangqing@rock-chips.com>,
dbasehore@chromium.org, amstan@chromium.org,
linux-rockchip@lists.infradead.org, briannorris@chromium.org,
mka@chromium.org, ryandcase@chromium.org,
Chris Zhong <zyw@rock-chips.com>,
linux-arm-kernel@lists.infradead.org,
Russell King <linux@armlinux.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] ARM: rockchip: pm: Mark init functions __init
Date: Fri, 12 Apr 2019 13:16:34 +0200 [thread overview]
Message-ID: <4763542.DKDFWeTMbT@diego> (raw)
In-Reply-To: <20190411232157.55125-2-dianders@chromium.org>
Am Freitag, 12. April 2019, 01:21:54 CEST schrieb Douglas Anderson:
> The functions rk3288_config_bootdata() and rk3288_suspend_init() are
> only called in the context of rockchip_suspend_init() which is already
> marked __init. We can mark them __init too.
>
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
applied for 5.2
Thanks
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: Douglas Anderson <dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Cc: Elaine Zhang <zhangqing-TNX95d0MmH7DzftRWevZcw@public.gmane.org>,
amstan-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org,
briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org,
dbasehore-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org,
Russell King <linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
mka-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org,
ryandcase-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org,
Chris Zhong <zyw-TNX95d0MmH7DzftRWevZcw@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 2/5] ARM: rockchip: pm: Mark init functions __init
Date: Fri, 12 Apr 2019 13:16:34 +0200 [thread overview]
Message-ID: <4763542.DKDFWeTMbT@diego> (raw)
In-Reply-To: <20190411232157.55125-2-dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Am Freitag, 12. April 2019, 01:21:54 CEST schrieb Douglas Anderson:
> The functions rk3288_config_bootdata() and rk3288_suspend_init() are
> only called in the context of rockchip_suspend_init() which is already
> marked __init. We can mark them __init too.
>
> Signed-off-by: Douglas Anderson <dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
applied for 5.2
Thanks
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Douglas Anderson <dianders@chromium.org>
Cc: Elaine Zhang <zhangqing@rock-chips.com>,
amstan@chromium.org, briannorris@chromium.org,
dbasehore@chromium.org, Russell King <linux@armlinux.org.uk>,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
mka@chromium.org, ryandcase@chromium.org,
Chris Zhong <zyw@rock-chips.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/5] ARM: rockchip: pm: Mark init functions __init
Date: Fri, 12 Apr 2019 13:16:34 +0200 [thread overview]
Message-ID: <4763542.DKDFWeTMbT@diego> (raw)
In-Reply-To: <20190411232157.55125-2-dianders@chromium.org>
Am Freitag, 12. April 2019, 01:21:54 CEST schrieb Douglas Anderson:
> The functions rk3288_config_bootdata() and rk3288_suspend_init() are
> only called in the context of rockchip_suspend_init() which is already
> marked __init. We can mark them __init too.
>
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
applied for 5.2
Thanks
Heiko
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-04-12 11:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 23:21 [PATCH 1/5] clk: rockchip: Turn on "aclk_dmac1" for suspend Douglas Anderson
2019-04-11 23:21 ` Douglas Anderson
2019-04-11 23:21 ` [PATCH 2/5] ARM: rockchip: pm: Mark init functions __init Douglas Anderson
2019-04-11 23:21 ` Douglas Anderson
2019-04-12 11:16 ` Heiko Stübner [this message]
2019-04-12 11:16 ` Heiko Stübner
2019-04-12 11:16 ` Heiko Stübner
2019-04-11 23:21 ` [PATCH 3/5] ARM: dts: rockchip: Add DDR retention/poweroff to rk3288-veyron hogs Douglas Anderson
2019-04-11 23:21 ` Douglas Anderson
2019-04-12 11:16 ` Heiko Stübner
2019-04-12 11:16 ` Heiko Stübner
2019-04-11 23:21 ` [PATCH 4/5] ARM: dts: rockchip: vcc33_ccd off in suspend for rk3288-veyron-chromebook Douglas Anderson
2019-04-11 23:21 ` Douglas Anderson
2019-04-12 1:53 ` elaine.zhang
2019-04-12 1:53 ` elaine.zhang
2019-04-12 11:16 ` Heiko Stübner
2019-04-12 11:16 ` Heiko Stübner
2019-04-11 23:21 ` [PATCH 5/5] ARM: dts: rockchip: vdd_gpu off in suspend for rk3288-veyron Douglas Anderson
2019-04-11 23:21 ` Douglas Anderson
2019-04-12 1:55 ` elaine.zhang
2019-04-12 1:55 ` elaine.zhang
2019-04-12 11:17 ` Heiko Stübner
2019-04-12 11:17 ` Heiko Stübner
2019-04-12 1:56 ` [PATCH 1/5] clk: rockchip: Turn on "aclk_dmac1" for suspend elaine.zhang
2019-04-12 1:56 ` elaine.zhang
2019-04-12 10:06 ` Heiko Stübner
2019-04-12 10:06 ` Heiko Stübner
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=4763542.DKDFWeTMbT@diego \
--to=heiko@sntech.de \
--cc=amstan@chromium.org \
--cc=briannorris@chromium.org \
--cc=dbasehore@chromium.org \
--cc=dianders@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mka@chromium.org \
--cc=ryandcase@chromium.org \
--cc=zhangqing@rock-chips.com \
--cc=zyw@rock-chips.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 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.