From: Rob Herring <robh@kernel.org>
To: Artjom Vejsel <akawolf0@gmail.com>
Cc: devicetree@vger.kernel.org, thierry.reding@gmail.com,
paul@crapouillou.net, sam@ravnborg.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 1/3] dt-bindings: Add QiShenglong vendor prefix
Date: Mon, 26 Jul 2021 16:49:32 -0600 [thread overview]
Message-ID: <20210726224932.GA1020830@robh.at.kernel.org> (raw)
In-Reply-To: <20210725221527.1771892-2-akawolf0@gmail.com>
On Mon, 26 Jul 2021 01:15:25 +0300, Artjom Vejsel wrote:
> Add vendor prefix for Shenzhen QiShenglong Industrialist Co., Ltd.
> QiShenglong is a Chinese manufacturer of handheld gaming consoles, most of
> which run (very old) versions of Linux.
> QiShenglong is known as Hamy.
>
> Signed-off-by: Artjom Vejsel <akawolf0@gmail.com>
> ---
> Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Artjom Vejsel <akawolf0@gmail.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
robh+dt@kernel.org, paul@crapouillou.net,
thierry.reding@gmail.com, dri-devel@lists.freedesktop.org,
sam@ravnborg.org
Subject: Re: [PATCH v3 1/3] dt-bindings: Add QiShenglong vendor prefix
Date: Mon, 26 Jul 2021 16:49:32 -0600 [thread overview]
Message-ID: <20210726224932.GA1020830@robh.at.kernel.org> (raw)
In-Reply-To: <20210725221527.1771892-2-akawolf0@gmail.com>
On Mon, 26 Jul 2021 01:15:25 +0300, Artjom Vejsel wrote:
> Add vendor prefix for Shenzhen QiShenglong Industrialist Co., Ltd.
> QiShenglong is a Chinese manufacturer of handheld gaming consoles, most of
> which run (very old) versions of Linux.
> QiShenglong is known as Hamy.
>
> Signed-off-by: Artjom Vejsel <akawolf0@gmail.com>
> ---
> Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-07-26 22:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-25 22:15 [PATCH v3 0/3] add Gopher 2b LCD panel Artjom Vejsel
2021-07-25 22:15 ` Artjom Vejsel
2021-07-25 22:15 ` [PATCH v3 1/3] dt-bindings: Add QiShenglong vendor prefix Artjom Vejsel
2021-07-25 22:15 ` Artjom Vejsel
2021-07-25 23:06 ` Paul Cercueil
2021-07-25 23:06 ` Paul Cercueil
2021-07-26 22:49 ` Rob Herring [this message]
2021-07-26 22:49 ` Rob Herring
2021-07-25 22:15 ` [PATCH v3 2/3] dt-bindings: Add DT bindings for QiShenglong Gopher 2b panel Artjom Vejsel
2021-07-25 22:15 ` Artjom Vejsel
2021-07-25 23:06 ` Paul Cercueil
2021-07-25 23:06 ` Paul Cercueil
2021-07-26 22:51 ` Rob Herring
2021-07-26 22:51 ` Rob Herring
2021-07-25 22:15 ` [PATCH v3 3/3] drm/panel-simple: add Gopher 2b LCD panel Artjom Vejsel
2021-07-25 22:15 ` Artjom Vejsel
2021-07-25 23:07 ` Paul Cercueil
2021-07-25 23:07 ` Paul Cercueil
2021-07-26 9:02 ` Paul Cercueil
2021-07-26 9:02 ` Paul Cercueil
2021-07-26 11:11 ` Artjom Vejsel
2021-07-26 11:11 ` Artjom Vejsel
2021-07-26 20:00 ` Sam Ravnborg
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=20210726224932.GA1020830@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=akawolf0@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@crapouillou.net \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=thierry.reding@gmail.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.