From: "Andreas Färber" <afaerber@suse.de>
To: Stafford Horne <shorne@gmail.com>, LKML <linux-kernel@vger.kernel.org>
Cc: Openrisc <openrisc@lists.librecores.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Kevin Hilman <khilman@baylibre.com>,
Jonathan Cameron <jic23@kernel.org>,
Thierry Reding <treding@nvidia.com>,
Marek Vasut <marek.vasut@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 05/14] dt-bindings: add openrisc to vendor prefixes list
Date: Sun, 10 Sep 2017 13:13:55 +0200 [thread overview]
Message-ID: <8692ec38-798e-9766-56f6-56bf7b022718@suse.de> (raw)
In-Reply-To: <20170910064926.5874-6-shorne@gmail.com>
Am 10.09.2017 um 08:49 schrieb Stafford Horne:
> Add OpenRISC.io to vendor prefixes. This is reserved for softcores
> developed by the OpenRISC community. The OpenRISC community has
> separated from OpenCores.org requiring a new prefix.
>
> Signed-off-by: Stafford Horne <shorne@gmail.com>
Reviewed-by: Andreas Färber <afaerber@suse.de>
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2017-09-10 11:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-10 6:49 [PATCH v2 00/14] OpenRISC SMP Support Stafford Horne
2017-09-10 6:49 ` [PATCH v2 01/14] openrisc: use shadow registers to save regs on exception Stafford Horne
2017-09-10 6:49 ` [PATCH v2 02/14] openrisc: define CPU_BIG_ENDIAN as true Stafford Horne
2017-09-10 6:49 ` [PATCH v2 03/14] openrisc: add 1 and 2 byte cmpxchg support Stafford Horne
2017-09-10 6:49 ` [PATCH v2 04/14] openrisc: use qspinlocks and qrwlocks Stafford Horne
2017-09-10 6:49 ` [PATCH v2 05/14] dt-bindings: add openrisc to vendor prefixes list Stafford Horne
2017-09-10 11:13 ` Andreas Färber [this message]
2017-09-18 20:39 ` Rob Herring
2017-09-10 6:49 ` [PATCH v2 06/14] irqchip: add initial support for ompic Stafford Horne
2017-09-13 17:21 ` Marc Zyngier
2017-09-14 6:54 ` Stafford Horne
2017-09-14 18:31 ` Marc Zyngier
2017-09-18 20:29 ` Rob Herring
2017-09-19 12:14 ` Stafford Horne
2017-09-18 20:43 ` Rob Herring
2017-09-19 12:10 ` Stafford Horne
2017-09-10 6:49 ` [PATCH v2 07/14] openrisc: initial SMP support Stafford Horne
2017-09-10 6:49 ` [PATCH v2 08/14] openrisc: fix initial preempt state for secondary cpu tasks Stafford Horne
2017-09-10 6:49 ` [PATCH v2 09/14] openrisc: sleep instead of spin on secondary wait Stafford Horne
2017-09-10 6:49 ` [PATCH v2 10/14] openrisc: add cacheflush support to fix icache aliasing Stafford Horne
2017-09-10 6:49 ` [PATCH v2 11/14] openrisc: add simple_smp dts and defconfig for simulators Stafford Horne
2017-09-10 6:49 ` [PATCH v2 12/14] openrisc: support framepointers and STACKTRACE_SUPPORT Stafford Horne
2017-09-10 6:49 ` [PATCH v2 13/14] openrisc: enable LOCKDEP_SUPPORT and irqflags tracing Stafford Horne
2017-09-10 6:49 ` [PATCH v2 14/14] openrisc: add tick timer multicore sync logic Stafford Horne
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=8692ec38-798e-9766-56f6-56bf7b022718@suse.de \
--to=afaerber@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marek.vasut@gmail.com \
--cc=mark.rutland@arm.com \
--cc=openrisc@lists.librecores.org \
--cc=robh+dt@kernel.org \
--cc=shorne@gmail.com \
--cc=treding@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®