linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lars@metafoo.de (Lars-Peter Clausen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] iio: adc: xilinx-xadc: Add xlnx,extend-name as an optional argument for aux channels
Date: Tue, 19 May 2015 19:53:39 +0200	[thread overview]
Message-ID: <555B78A3.2030202@metafoo.de> (raw)
In-Reply-To: <1431038644-41600-2-git-send-email-xander.huff@ni.com>

On 05/08/2015 12:44 AM, Xander Huff wrote:
> To better facilitate user-mode access to optional aux channels, allow
> device trees to specify a custom extended name for defined channels.

Hi,

'extend-name' is kind of a IIO specific term. I think a better name in the 
devicetree context would be 'label'. That's used everywhere else when giving 
a short description string to a node.

- Lars

  reply	other threads:[~2015-05-19 17:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07 22:44 [PATCH 1/2] devicetree: xilinx-xadc: Add optional xlnx, extend-name property Xander Huff
2015-05-07 22:44 ` [PATCH 2/2] iio: adc: xilinx-xadc: Add xlnx, extend-name as an optional argument for aux channels Xander Huff
2015-05-19 17:53   ` Lars-Peter Clausen [this message]
2015-05-20 15:22     ` [PATCH v2 1/2] devicetree: xilinx-xadc: Add optional label property Xander Huff
2015-05-20 15:22       ` [PATCH v2 2/2] iio: adc: xilinx-xadc: Add label as an optional argument for aux channels Xander Huff
2015-06-07 16:49         ` Jonathan Cameron
2015-06-08 13:49           ` Josh Cartwright
2015-06-14 11:20             ` Jonathan Cameron
2015-05-23 11:23     ` [PATCH 2/2] iio: adc: xilinx-xadc: Add xlnx,extend-name " Jonathan Cameron
2015-05-26  9:38       ` Lars-Peter Clausen
2015-05-26 19:05         ` Xander Huff
2015-05-08 18:43 ` [PATCH 1/2] devicetree: xilinx-xadc: Add optional xlnx, extend-name property Jonathan Cameron

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=555B78A3.2030202@metafoo.de \
    --to=lars@metafoo.de \
    --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).