From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: "M. Warner Losh" <imp-uzTCJ5RojNnQT0dZR+AlfA@public.gmane.org>
Cc: devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org,
gvb.uboot-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: [RFC] add alias support to fdt_path_offset
Date: Tue, 5 Aug 2008 14:13:06 +1000 [thread overview]
Message-ID: <20080805041306.GC16526@yookeroo.seuss> (raw)
In-Reply-To: <20080804.220226.-1219852411.imp-uzTCJ5RojNnQT0dZR+AlfA@public.gmane.org>
On Mon, Aug 04, 2008 at 10:02:26PM -0600, M. Warner Losh wrote:
> In message: <20080805035844.GB16526-787xzQ0H9iRg7VrjXcPTGA@public.gmane.org>
> David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org> writes:
> : On Mon, Aug 04, 2008 at 05:25:17PM -0500, Kumar Gala wrote:
> : > Here's my attempt at adding alias support to fdt_path_offset()
> : >
> : > I don't care for the path_buf[256], but not sure how else to do
> : > that.
> :
> : That's because you haven't thought hard enough, we can do better than
> : this. Patches coming..
>
> Hmmm, PATH_MAX...
No. We can do better than that, too. Though admittedly it will be
slightly more work than I first thought.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2008-08-05 4:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 22:25 [RFC] add alias support to fdt_path_offset Kumar Gala
[not found] ` <Pine.LNX.4.64.0808041722001.328-S0ohy4nlquecPGwCZ8RIISaugJOa9f/+@public.gmane.org>
2008-08-05 3:58 ` David Gibson
[not found] ` <20080805035844.GB16526-787xzQ0H9iRg7VrjXcPTGA@public.gmane.org>
2008-08-05 4:02 ` M. Warner Losh
[not found] ` <20080804.220226.-1219852411.imp-uzTCJ5RojNnQT0dZR+AlfA@public.gmane.org>
2008-08-05 4:13 ` David Gibson [this message]
[not found] ` <20080805041306.GC16526-787xzQ0H9iRg7VrjXcPTGA@public.gmane.org>
2008-08-05 6:26 ` Kumar Gala
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=20080805041306.GC16526@yookeroo.seuss \
--to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
--cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
--cc=gvb.uboot-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=imp-uzTCJ5RojNnQT0dZR+AlfA@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