All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: Heiko Stuebner <heiko@sntech.de>
Cc: linux-rockchip@lists.infradead.org, sboyd@kernel.org,
	zhangqing@rock-chips.com, linux-clk@vger.kernel.org,
	mturquette@baylibre.com
Subject: Re: [PATCH 1/2] clk: rockchip: drop parenthesis from ARM || COMPILE_TEST depends
Date: Sun, 21 Mar 2021 21:14:30 +0100	[thread overview]
Message-ID: <161635763247.767241.6758144246841811873.b4-ty@sntech.de> (raw)
In-Reply-To: <20210315112502.343699-1-heiko@sntech.de>

On Mon, 15 Mar 2021 12:25:01 +0100, Heiko Stuebner wrote:
> As suggested by Stephen in the series adding the rk3568 clock controller
> the depends works just as well without the parenthesis around the depends.
> 
> So to make everything look the same, drop them from existing entries too.

Applied, thanks!

[1/2] clk: rockchip: drop parenthesis from ARM || COMPILE_TEST depends
      commit: e8c51b90f22031bf3f24d1f06d23bafac250bb62
[2/2] clk: rockchip: drop MODULE_ALIAS from rk3399 clock controller
      commit: 40f29839d8bef5aecaa772afa8e5f2ff8434b49f

Best regards,
-- 
Heiko Stuebner <heiko@sntech.de>

WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: Heiko Stuebner <heiko@sntech.de>
Cc: linux-rockchip@lists.infradead.org, sboyd@kernel.org,
	zhangqing@rock-chips.com, linux-clk@vger.kernel.org,
	mturquette@baylibre.com
Subject: Re: [PATCH 1/2] clk: rockchip: drop parenthesis from ARM || COMPILE_TEST depends
Date: Sun, 21 Mar 2021 21:14:30 +0100	[thread overview]
Message-ID: <161635763247.767241.6758144246841811873.b4-ty@sntech.de> (raw)
In-Reply-To: <20210315112502.343699-1-heiko@sntech.de>

On Mon, 15 Mar 2021 12:25:01 +0100, Heiko Stuebner wrote:
> As suggested by Stephen in the series adding the rk3568 clock controller
> the depends works just as well without the parenthesis around the depends.
> 
> So to make everything look the same, drop them from existing entries too.

Applied, thanks!

[1/2] clk: rockchip: drop parenthesis from ARM || COMPILE_TEST depends
      commit: e8c51b90f22031bf3f24d1f06d23bafac250bb62
[2/2] clk: rockchip: drop MODULE_ALIAS from rk3399 clock controller
      commit: 40f29839d8bef5aecaa772afa8e5f2ff8434b49f

Best regards,
-- 
Heiko Stuebner <heiko@sntech.de>

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

  parent reply	other threads:[~2021-03-21 20:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-15 11:25 [PATCH 1/2] clk: rockchip: drop parenthesis from ARM || COMPILE_TEST depends Heiko Stuebner
2021-03-15 11:25 ` Heiko Stuebner
2021-03-15 11:25 ` [PATCH 2/2] clk: rockchip: drop MODULE_ALIAS from rk3399 clock controller Heiko Stuebner
2021-03-15 11:25   ` Heiko Stuebner
2021-03-17  1:36   ` Stephen Boyd
2021-03-17  1:36     ` Stephen Boyd
2021-03-17  1:36 ` [PATCH 1/2] clk: rockchip: drop parenthesis from ARM || COMPILE_TEST depends Stephen Boyd
2021-03-17  1:36   ` Stephen Boyd
2021-03-21 20:14 ` Heiko Stuebner [this message]
2021-03-21 20:14   ` Heiko Stuebner

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=161635763247.767241.6758144246841811873.b4-ty@sntech.de \
    --to=heiko@sntech.de \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.org \
    --cc=zhangqing@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.