mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Trent Piepho <tpiepho@kymetacorp.com>
Cc: barebox <barebox@lists.infradead.org>
Subject: Re: [PATCH] cdev: When creating a new cdev, initialize device_node
Date: Mon, 14 Dec 2015 11:25:58 +0100	[thread overview]
Message-ID: <20151214102558.GG11966@pengutronix.de> (raw)
In-Reply-To: <1449793397.26955.94.camel@rtred1test09.kymeta.local>

On Fri, Dec 11, 2015 at 12:23:11AM +0000, Trent Piepho wrote:
> If a new cdev doesn't have a device_node defined when passed to
> devfs_create(), set it to the device_node of the parent device, if one
> exists.
> 
> For non-partitions, like ocotp or eeprom devices, this is the correct
> thing to do.  Partitions need to use, and do use, a different node.
> 
> The code from commit 274e0b8dc48956babeaa2faf70bf8066e656b621 to set
> device_node in ocotp can be removed.
> 
> Signed-off-by: Trent Piepho <tpiepho@kymetacorp.com>
> ---
> Tested this to work for loading the env from an at24 eeprom.  Should work
> for any other non-partitioned device too.

Applied, thanks

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2015-12-14 10:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-11  0:23 Trent Piepho
2015-12-14 10:25 ` Sascha Hauer [this message]

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=20151214102558.GG11966@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=tpiepho@kymetacorp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox