linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tommy Huang <tommy_huang@aspeedtech.com>
To: Rob Herring <robh@kernel.org>
Cc: "dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
	"daniel@ffwll.ch" <daniel@ffwll.ch>,
	BMC-SW <BMC-SW@aspeedtech.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"joel@jms.id.au" <joel@jms.id.au>,
	"andrew@aj.id.au" <andrew@aj.id.au>,
	"airlied@linux.ie" <airlied@linux.ie>
Subject: RE: [PATCH 4/4] dt-bindings: gpu: Add ASPEED GFX bindings document
Date: Tue, 2 Nov 2021 00:20:38 +0000	[thread overview]
Message-ID: <HK2PR0601MB20338733A2D74609492388FAE18B9@HK2PR0601MB2033.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <YYBHsy3Ed3Ss9281@robh.at.kernel.org>

Hi Rob,

	Thanks for your comments.
	I got it.

	By Tommy

> -----Original Message-----
> From: Rob Herring <robh@kernel.org>
> Sent: Tuesday, November 2, 2021 4:02 AM
> To: Tommy Huang <tommy_huang@aspeedtech.com>
> Cc: dri-devel@lists.freedesktop.org; linux-arm-kernel@lists.infradead.org;
> linux-aspeed@lists.ozlabs.org; daniel@ffwll.ch; BMC-SW
> <BMC-SW@aspeedtech.com>; devicetree@vger.kernel.org;
> linux-kernel@vger.kernel.org; robh+dt@kernel.org; joel@jms.id.au;
> andrew@aj.id.au; airlied@linux.ie
> Subject: Re: [PATCH 4/4] dt-bindings: gpu: Add ASPEED GFX bindings document
> 
> On Mon, 01 Nov 2021 19:01:07 +0800, tommy-huang wrote:
> > Add ast2600-gfx description for gfx driver.
> >
> > Signed-off-by: tommy-huang <tommy_huang@aspeedtech.com>
> > ---
> >  Documentation/devicetree/bindings/gpu/aspeed-gfx.txt | 1 +
> >  1 file changed, 1 insertion(+)
> >
> 
> 
> Please add Acked-by/Reviewed-by tags when posting new versions. However,
> there's no need to repost patches *only* to add the tags. The upstream
> maintainer will do that for acks received on the version they apply.
> 
> If a tag was not added on purpose, please state why and what changed.


      reply	other threads:[~2021-11-02  0:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-01 11:01 [PATCH 0/4] Add Aspeed AST2600 soc display support tommy-huang
2021-11-01 11:01 ` [PATCH 1/4] ARM: dts: aspeed: Add GFX node to AST2600 tommy-huang
2021-11-01 11:01 ` [PATCH 2/4] ARM: dts: aspeed: ast2600-evb: Enable GFX device tommy-huang
2021-11-01 11:01 ` [PATCH 3/4] drm/aspeed: Update INTR_STS handling tommy-huang
2021-11-16  6:18   ` Joel Stanley
2021-11-16  7:18     ` Tommy Huang
2021-11-01 11:01 ` [PATCH 4/4] dt-bindings: gpu: Add ASPEED GFX bindings document tommy-huang
2021-11-01 20:01   ` Rob Herring
2021-11-02  0:20     ` Tommy Huang [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=HK2PR0601MB20338733A2D74609492388FAE18B9@HK2PR0601MB2033.apcprd06.prod.outlook.com \
    --to=tommy_huang@aspeedtech.com \
    --cc=BMC-SW@aspeedtech.com \
    --cc=airlied@linux.ie \
    --cc=andrew@aj.id.au \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=joel@jms.id.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=robh@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 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).