devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: rob.herring-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org
Subject: [RFC 0/3] of: Refactor device tree linked lists
Date: Thu,  5 Jun 2014 16:43:38 +0100	[thread overview]
Message-ID: <1401983021-13829-1-git-send-email-grant.likely@linaro.org> (raw)

I threw these patches together as part of getting the device_node
lifecycle issues sorted out so that the overlay patches can be merged.
It makes it possible to add and remove nodes without jumping through
crazy hoops.

I haven't yet decided if it is a good idea. It does increase the size of
deviec_node by 2 pointers which increases the footprint, but it
simplifies a lot of the code.  Although, if I was really concerned about
footprint I would be trying to get rid of the ->full_name string and
just use the path component instead. The primary user of full_name is
various printk format strings around the kernel and we could get the
same behaviour using a %p variant.

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2014-06-05 15:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-05 15:43 Grant Likely [this message]
     [not found] ` <1401983021-13829-1-git-send-email-grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-06-05 15:43   ` [RFC 1/3] of: Migrate of_find_node_by_name() users to for_each_node_by_name() Grant Likely
     [not found]     ` <1401983021-13829-2-git-send-email-grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-06-05 17:48       ` Rob Herring
     [not found]         ` <CABGGisx=fhp1P68M+9aQUTzi6Bp+PnXK7Xq_TQ+=87AkGCZvwQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-26 16:03           ` Grant Likely
     [not found]             ` <20140626160345.6613CC41060-WNowdnHR2B42iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
2014-06-26 18:22               ` Rob Herring
     [not found]                 ` <CAL_JsqKDsdqd3PJ0gwvESMER=Nxi1us55pKWDhTuZtwgjo_MGA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-26 18:56                   ` Grant Likely
     [not found]                     ` <CACxGe6tiiNvz9VCq=enTWMGDBUS_0gsDZh2DvzpVP5itQtiRpA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-26 19:00                       ` Rob Herring
     [not found]                         ` <CAL_JsqLUjcxHrHctfVe7M79=8MpUCYq1cBhfsoXVzrBoxECwvw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-26 19:02                           ` Grant Likely
2014-06-05 15:43   ` [RFC 2/3] of: Replace custom linked list with list_head Grant Likely
2014-06-05 15:43   ` [RFC 3/3] of: Refactor device_node child list to use list_head Grant Likely

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=1401983021-13829-1-git-send-email-grant.likely@linaro.org \
    --to=grant.likely-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=rob.herring-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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).