All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerry Van Baren <vanbargw@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [RFC libfdt update][PATCH 1/2] Removed some nonused fdt functions and moved fdt_find_and_setprop out of libfdt
Date: Wed, 24 Oct 2007 19:05:01 -0400	[thread overview]
Message-ID: <471FCF9D.70808@gmail.com> (raw)
In-Reply-To: <29786391-C862-4908-8FF8-A271B3BA6358@kernel.crashing.org>

Kumar Gala wrote:
> On Oct 24, 2007, at 12:00 PM, Jerry Van Baren wrote:
> 
>> Wolfgang Grandegger wrote:
>>> Kumar Gala wrote:
>>>> Removed:
>>>> 	fdt_node_is_compatible
>>>> 	fdt_find_node_by_type
>>>> 	fdt_find_compatible_node
>>>>
>>>> To ease merge of newer libfdt as we aren't using them anywhere at  
>>>> this time.
>>> I use them for development (new projects). When can we expect the  
>>> new libfdt to be available in U-Boot?
>>> Wolfgang.
>> Hi Kumar, Wolfgang,
>>
>> My current thought is that we need a place above libfdt where we  
>> can put our convenience (and difference-of-opinion ;-) utility  
>> routines.
>>
>> I'm thinking
>>   common/fdt_support.c
>> would be the place for this.  Then Wolfgang G can put his fdt_*  
>> kernel-parallel routines (above) in there as well as the utility  
>> routine that Grant created (find & set, I forgot the exact name).
> 
> Agreed, I moved Grant's fdt_find_and_setprop into common/fdt_support.c
> 
> Also, realize there are equivalent functions to  
> fdt_node_is_compatible, etc. in the new libfdt.
> 
> - k

Ahh, right, the brain was shorted, too much caffeine, too little 
caffeine, its hard to get it balanced.

My re-reading reminded me - question for Wolfgang Denk - are Doxygen 
tags in the source code acceptable?

Best regards,
gvb

  reply	other threads:[~2007-10-24 23:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24 16:06 [U-Boot-Users] [RFC libfdt update][PATCH 1/2] Removed some nonused fdt functions and moved fdt_find_and_setprop out of libfdt Kumar Gala
2007-10-24 16:21 ` Wolfgang Grandegger
2007-10-24 17:00   ` Jerry Van Baren
2007-10-24 18:04     ` Kumar Gala
2007-10-24 23:05       ` Jerry Van Baren [this message]
2007-10-25  7:03       ` Wolfgang Grandegger

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=471FCF9D.70808@gmail.com \
    --to=vanbargw@gmail.com \
    --cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.