From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Rob Herring <robh+dt@kernel.org>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Kumar Gala <galak@codeaurora.org>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>
Subject: Re: [PATCH 1/2] drm: bridge: sil902x
Date: Wed, 6 Jan 2016 14:53:30 +0100 [thread overview]
Message-ID: <20160106145330.03479703@bbrezillon> (raw)
In-Reply-To: <20160106134736.GR13058@pengutronix.de>
Hi Sascha,
On Wed, 6 Jan 2016 14:47:36 +0100
Sascha Hauer <s.hauer@pengutronix.de> wrote:
> Hi Boris,
>
> On Wed, Jan 06, 2016 at 12:25:50PM +0100, Boris Brezillon wrote:
> > Add basic support for the sil902x RGB -> HDMI bridge.
> > This driver does not support audio output yet.
> >
> > Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> > ---
> > Hello,
> >
> > This patch is only adding basic support for the sil9022 chip.
>
> This thing is a SiI9022 for camel case "Silicon Image" with a capital 'I',
> not a small 'l'.
Oh, my bad, I'll fix that, but the vendor prefix defined in
Documentation/devicetree/bindings/vendor-prefixes.txt is not helping in
getting this right.
Should I also change the driver name?
Best Regards,
Boris
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Kumar Gala <galak@codeaurora.org>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>
Subject: Re: [PATCH 1/2] drm: bridge: sil902x
Date: Wed, 6 Jan 2016 14:53:30 +0100 [thread overview]
Message-ID: <20160106145330.03479703@bbrezillon> (raw)
In-Reply-To: <20160106134736.GR13058@pengutronix.de>
Hi Sascha,
On Wed, 6 Jan 2016 14:47:36 +0100
Sascha Hauer <s.hauer@pengutronix.de> wrote:
> Hi Boris,
>
> On Wed, Jan 06, 2016 at 12:25:50PM +0100, Boris Brezillon wrote:
> > Add basic support for the sil902x RGB -> HDMI bridge.
> > This driver does not support audio output yet.
> >
> > Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> > ---
> > Hello,
> >
> > This patch is only adding basic support for the sil9022 chip.
>
> This thing is a SiI9022 for camel case "Silicon Image" with a capital 'I',
> not a small 'l'.
Oh, my bad, I'll fix that, but the vendor prefix defined in
Documentation/devicetree/bindings/vendor-prefixes.txt is not helping in
getting this right.
Should I also change the driver name?
Best Regards,
Boris
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-01-06 13:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 11:25 [PATCH 1/2] drm: bridge: sil902x Boris Brezillon
2016-01-06 11:25 ` Boris Brezillon
2016-01-06 11:25 ` [PATCH 2/2] drm: bridge: add sil902x DT bindings doc Boris Brezillon
[not found] ` <1452079551-30914-2-git-send-email-boris.brezillon-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2016-01-06 13:19 ` Rob Herring
2016-01-06 13:19 ` Rob Herring
2016-01-06 13:24 ` Boris Brezillon
2016-01-06 13:24 ` Boris Brezillon
2016-01-06 12:13 ` [PATCH 1/2] drm: bridge: sil902x kbuild test robot
2016-01-06 12:13 ` kbuild test robot
2016-01-06 12:25 ` [PATCH v2 " Boris Brezillon
2016-01-06 12:25 ` Boris Brezillon
2016-01-07 5:42 ` Archit Taneja
2016-01-07 5:42 ` Archit Taneja
2016-01-07 9:35 ` Boris Brezillon
[not found] ` <1452083126-18211-1-git-send-email-boris.brezillon-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2016-03-16 13:14 ` Nicolas Ferre
2016-03-16 13:14 ` Nicolas Ferre
2016-01-06 12:36 ` [PATCH " kbuild test robot
2016-01-06 12:36 ` kbuild test robot
2016-01-06 13:47 ` Sascha Hauer
2016-01-06 13:53 ` Boris Brezillon [this message]
2016-01-06 13:53 ` Boris Brezillon
2016-01-06 15:26 ` Sascha Hauer
2016-01-06 15:26 ` Sascha Hauer
[not found] ` <20160106152638.GS13058-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2016-01-06 15:35 ` Ilia Mirkin
2016-01-06 15:35 ` Ilia Mirkin
[not found] ` <CAKb7UvghNhGZLUX_3LchZoiYAtywN99tEpDy+k8ApPnPF-ce+Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-01-07 7:01 ` Sascha Hauer
2016-01-07 7:01 ` Sascha Hauer
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=20160106145330.03479703@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nicolas.ferre@atmel.com \
--cc=pawel.moll@arm.com \
--cc=plagnioj@jcrosoft.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
/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.