linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/2] dt-bindings: simplefb: Drop the advice about using a specific path for nodes
Date: Tue, 18 Nov 2014 11:10:49 +0000	[thread overview]
Message-ID: <1416309051-26784-1-git-send-email-hdegoede@redhat.com> (raw)

Hi Tomi,

So it turns out we needed a v3, as I mistakenly went with "sunxi," as vendor
prefix for the allwinner specific properties, but the registered vendor prefix
for allwinner is "allwinnner,", this version fixes this.

Changes in v3: Use proper "allwinnner," for the compatible string and vendor
specific properties.

Changes in v2: Changed the simplefb-sunxi bindings to use a single
sunxi,pipeline string property instead of a sunxi,pipeline int and a
sunxi,output string property.

This patch set is all acked up, and a fix to the binding changes you've
already queued for 3.19, so please queue these 2 patches for 3.19.

Thanks & Regards,

Hans

             reply	other threads:[~2014-11-18 11:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-18 11:10 Hans de Goede [this message]
2014-11-18 11:10 ` [PATCH v3 1/2] dt-bindings: simplefb: Drop the advice about using a specific path for nodes Hans de Goede
2014-11-18 11:10 ` [PATCH v3 2/2] dt-bindings: simplefb-sunxi: Add sunxi simplefb extensions Hans de Goede
2014-11-25 12:32   ` Tomi Valkeinen
2014-11-25 12:52     ` Hans de Goede
2014-11-25 13:02       ` Tomi Valkeinen
2014-11-25 13:21         ` Hans de Goede
2014-11-25 13:38           ` Tomi Valkeinen
2014-11-25 13:45             ` Hans de Goede
2014-11-26  8:13               ` Tomi Valkeinen
2014-11-25 12:34 ` [PATCH v3 0/2] dt-bindings: simplefb: Drop the advice about using a specific path for nodes Tomi Valkeinen

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=1416309051-26784-1-git-send-email-hdegoede@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.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).