All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: atull <atull@opensource.altera.com>
Cc: pantelis.antoniou@konsulko.com,
	Moritz Fischer <moritz.fischer@ettus.com>,
	gregkh@linuxfoundation.org, monstr@monstr.eu,
	michal.simek@xilinx.com, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-doc@vger.kernel.org, delicious.quinoa@gmail.com,
	dinguyen@opensource.altera.com,
	Matthew Gerlach <mgerlach@altera.com>
Subject: Re: [PATCH v17 2/6] ARM: socfpga: add bindings document for fpga bridge drivers
Date: Mon, 28 Mar 2016 17:09:23 -0500	[thread overview]
Message-ID: <20160328220923.GA12212@rob-hp-laptop> (raw)
In-Reply-To: <alpine.DEB.2.02.1603151657110.24255@linuxheads99>

On Tue, Mar 15, 2016 at 05:04:53PM -0500, atull wrote:
> On Sat, 5 Mar 2016, Rob Herring wrote:
> 
> > > +Example:
> > > +	hps_fpgabridge0: fpgabridge@ff400000 {
> > 
> > No underscores.
> > 
> > fpga-bridge@...
> 
> Hi Rob,
> 
> The dtc is not letting me compile if I use a hyphen in the label.
> I think we have to use hyphens in the node names and underscores
> in the labels.  So it will end up being:
> 
> +	fpga_bridge0: fpga-bridge@ff400000 {

Sorry, don't know what I was looking at. In labels, underscores are 
fine. This looks fine.

Rob

  parent reply	other threads:[~2016-03-28 22:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25 23:25 [PATCH v17 0/6] Device Tree support for FPGA Programming Alan Tull
2016-02-25 23:25 ` Alan Tull
2016-02-25 23:25 ` [PATCH v17 1/6] fpga: add bindings document for fpga region Alan Tull
2016-02-25 23:25   ` Alan Tull
2016-02-25 23:25 ` [PATCH v17 2/6] ARM: socfpga: add bindings document for fpga bridge drivers Alan Tull
2016-02-25 23:25   ` Alan Tull
2016-03-05  4:34   ` Rob Herring
2016-03-07 16:09     ` atull
2016-03-07 16:09       ` atull
2016-03-15 22:04     ` atull
2016-03-15 22:04       ` atull
2016-03-23 13:12       ` Rob Herring
2016-03-28 22:09       ` Rob Herring [this message]
2016-02-25 23:25 ` [PATCH v17 3/6] add sysfs document for fpga bridge class Alan Tull
2016-02-25 23:25   ` Alan Tull
2016-02-25 23:25 ` [PATCH v17 4/6] fpga: add fpga bridge framework Alan Tull
2016-02-25 23:25   ` Alan Tull
2016-02-25 23:25 ` [PATCH v17 5/6] fpga: fpga-region: device tree control for FPGA Alan Tull
2016-02-25 23:25   ` Alan Tull
2016-02-25 23:25 ` [PATCH v17 6/6] ARM: socfpga: fpga bridge driver support Alan Tull
2016-02-25 23:25   ` Alan Tull

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=20160328220923.GA12212@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=atull@opensource.altera.com \
    --cc=corbet@lwn.net \
    --cc=delicious.quinoa@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dinguyen@opensource.altera.com \
    --cc=galak@codeaurora.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mgerlach@altera.com \
    --cc=michal.simek@xilinx.com \
    --cc=monstr@monstr.eu \
    --cc=moritz.fischer@ettus.com \
    --cc=pantelis.antoniou@konsulko.com \
    --cc=pawel.moll@arm.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.