All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: Andy Yan <andy.yan@rock-chips.com>
Cc: kever.yang@rock-chips.com, robh+dt@kernel.org,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v2 1/4] dt-bindings: Add doc about rk3308 General Register Files
Date: Sun, 27 Oct 2019 18:45:16 +0100	[thread overview]
Message-ID: <5484541.170OI0MKF7@phil> (raw)
In-Reply-To: <20191021084555.28356-1-andy.yan@rock-chips.com>

Am Montag, 21. Oktober 2019, 10:45:55 CET schrieb Andy Yan:
> RK3308 GRF is divided into four sections: GRF, SGRF,
> DETECTGRF, COREGRF. This patch add documentation for
> it.
> 
> Signed-off-by: Andy Yan <andy.yan@rock-chips.com>

applied for 5.5

Thanks
Heiko



WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: Andy Yan <andy.yan@rock-chips.com>
Cc: devicetree@vger.kernel.org, kever.yang@rock-chips.com,
	linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
	robh+dt@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/4] dt-bindings: Add doc about rk3308 General Register Files
Date: Sun, 27 Oct 2019 18:45:16 +0100	[thread overview]
Message-ID: <5484541.170OI0MKF7@phil> (raw)
In-Reply-To: <20191021084555.28356-1-andy.yan@rock-chips.com>

Am Montag, 21. Oktober 2019, 10:45:55 CET schrieb Andy Yan:
> RK3308 GRF is divided into four sections: GRF, SGRF,
> DETECTGRF, COREGRF. This patch add documentation for
> it.
> 
> Signed-off-by: Andy Yan <andy.yan@rock-chips.com>

applied for 5.5

Thanks
Heiko



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2019-10-27 17:45 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21  8:44 [PATCH v2 0/4] Add basic dts support for RK3308 Andy Yan
2019-10-21  8:44 ` Andy Yan
2019-10-21  8:45 ` [PATCH v2 1/4] dt-bindings: Add doc about rk3308 General Register Files Andy Yan
2019-10-21  8:45   ` Andy Yan
2019-10-25 21:32   ` Rob Herring
2019-10-25 21:32     ` Rob Herring
2019-10-25 21:32     ` Rob Herring
2019-10-27 17:45   ` Heiko Stuebner [this message]
2019-10-27 17:45     ` Heiko Stuebner
2019-10-21  8:46 ` [PATCH v2 2/4] arm64: dts: rockchip: Add core dts for RK3308 SOC Andy Yan
2019-10-21  8:46   ` Andy Yan
2019-10-21  8:46   ` Andy Yan
2019-10-27 17:45   ` Heiko Stuebner
2019-10-27 17:45     ` Heiko Stuebner
2019-10-21  8:46 ` [PATCH v2 3/4] dt-bindings: Add doc for rk3308-evb Andy Yan
2019-10-21  8:46   ` Andy Yan
2019-10-25 21:33   ` Rob Herring
2019-10-25 21:33     ` Rob Herring
2019-10-25 21:33     ` Rob Herring
2019-10-27 17:44   ` Heiko Stuebner
2019-10-27 17:44     ` Heiko Stuebner
2019-10-21  8:46 ` [PATCH v2 4/4] arm64: dts: rockchip: Add basic dts for RK3308 EVB Andy Yan
2019-10-21  8:46   ` Andy Yan
2019-10-27 17:55   ` Heiko Stuebner
2019-10-27 17:55     ` 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=5484541.170OI0MKF7@phil \
    --to=heiko@sntech.de \
    --cc=andy.yan@rock-chips.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kever.yang@rock-chips.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh+dt@kernel.org \
    /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.