linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Robin Holt <holt@sgi.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	U Bhaskar-B22300 <B22300@freescale.com>,
	"socketcan-core@lists.berlios.de"
	<socketcan-core@lists.berlios.de>,
	PPC list <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH v10 5/5] [powerpc] Fix up fsl-flexcan device tree binding.
Date: Wed, 10 Aug 2011 13:39:53 -0500	[thread overview]
Message-ID: <4E42D079.7070709@freescale.com> (raw)
In-Reply-To: <20110810183526.GZ4926@sgi.com>

On 08/10/2011 01:35 PM, Robin Holt wrote:
> On Wed, Aug 10, 2011 at 01:27:52PM -0500, Scott Wood wrote:
>> "...and then associate the label with an alias."
>>
>> The alias can then be used if you want "can0" versus "can1".
> 
> Does the alias get used by either the kernel or something else or is it
> just extra detail with no purpose?

It could be used by udev to produce a symlink.  Currently, the major
non-human consumer of the aliases is U-Boot.

-Scott

  reply	other threads:[~2011-08-10 18:40 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-10  3:05 [PATCH v10 0/5] [flexcan/powerpc] Add support for powerpc flexcan (freescale p1010) Robin Holt
2011-08-10  3:06 ` [PATCH v10 1/5] [flexcan] Remove #include <mach/clock.h> Robin Holt
2011-08-10  3:06 ` [PATCH v10 2/5] [flexcan] Abstract off read/write for big/little endian Robin Holt
2011-08-10  3:06 ` [PATCH v10 3/5] [flexcan] Add of_match to platform_device definition Robin Holt
2011-08-10 14:33   ` Robin Holt
2011-08-10  3:06 ` [PATCH v10 4/5] [powerpc] Add flexcan device support for p1010rdb Robin Holt
2011-08-10  9:56   ` Marc Kleine-Budde
2011-08-10 10:15     ` Robin Holt
2011-08-10  3:06 ` [PATCH v10 5/5] [powerpc] Fix up fsl-flexcan device tree binding Robin Holt
2011-08-10  8:15   ` Robert Schwebel
2011-08-10 10:09   ` Robin Holt
2011-08-10 13:47   ` Wolfgang Grandegger
2011-08-10 14:15     ` Robin Holt
2011-08-10 14:36       ` U Bhaskar-B22300
2011-08-10 16:00         ` Robin Holt
2011-08-10 16:53           ` Kumar Gala
2011-08-10 17:16             ` Robin Holt
2011-08-10 17:17               ` Kumar Gala
2011-08-10 17:20                 ` Robin Holt
2011-08-10 17:26                   ` Kumar Gala
2011-08-10 18:23           ` Wolfgang Grandegger
2011-08-10 18:27             ` Scott Wood
2011-08-10 18:35               ` Robin Holt
2011-08-10 18:39                 ` Scott Wood [this message]
2011-08-10 14:41       ` Wolfgang Grandegger
2011-08-10 14:46         ` Kumar Gala
2011-08-10 14:45       ` Kumar Gala
2011-08-10 15:35         ` Robin Holt
2011-08-10 10:01 ` [PATCH v10 0/5] [flexcan/powerpc] Add support for powerpc flexcan (freescale p1010) Marc Kleine-Budde
2011-08-10 10:11   ` Robin Holt
2011-08-10 10:24     ` Marc Kleine-Budde
2011-08-10 11:09 ` Marc Kleine-Budde

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=4E42D079.7070709@freescale.com \
    --to=scottwood@freescale.com \
    --cc=B07421@freescale.com \
    --cc=B22300@freescale.com \
    --cc=holt@sgi.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=netdev@vger.kernel.org \
    --cc=socketcan-core@lists.berlios.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 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).