From: Sascha Hauer <s.hauer@pengutronix.de>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
barebox@lists.infradead.org
Subject: Re: [PATCH] of: add ranges address translation for default bus
Date: Thu, 13 Jun 2013 14:48:33 +0200 [thread overview]
Message-ID: <20130613124833.GD32299@pengutronix.de> (raw)
In-Reply-To: <51B9930B.8080609@gmail.com>
On Thu, Jun 13, 2013 at 11:38:19AM +0200, Sebastian Hesselbarth wrote:
> On 06/13/13 11:25, Sascha Hauer wrote:
> >On Tue, Jun 11, 2013 at 11:33:06AM +0200, Sebastian Hesselbarth wrote:
> >>I started merging already, and from what I can see we should just remove
> >>the spinlocks and OF_DYNAMIC stuff (but leave of_node_get/_put as stubs)
> >
> >Sounds like a plan. Functions existing both in barebox and Linux should
> >behave the same way. However, if Linux turns out to do something silly
> >or (for our usecase) too bloated, we shouldn't do the same just because
> >Linux does it.
> >
> >I want to keep the Linux list usage in the devicetree, so they won't be
> >really in sync.
>
> Ok, I started converting and doing it in a clean way is kind of tricky.
>
> First of all, allyesconfig doesn't build - so it is hard to find and
> re-build all users of current of_* functions.
>
> If you want to stick with list usage, it will end up with converting
> instead of just move current functions out of the way, import Linux
> OF, and switch users to that functions.
>
> I will have a look at it, find users/abusers of current API and see
> how much we can merge.
>
> You also want to stick with of_set_* and friends within base.c or
> move them out to some other source file where all set/modify functions
> will sit in?
I'm fine with moving the set/modify kernel to another file, no problem.
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
next prev parent reply other threads:[~2013-06-13 12:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-12 23:09 Sebastian Hesselbarth
2013-05-19 7:34 ` Sascha Hauer
2013-05-19 8:07 ` Sebastian Hesselbarth
2013-05-19 10:39 ` Sascha Hauer
2013-05-19 10:49 ` Sebastian Hesselbarth
2013-05-19 15:20 ` Thomas Petazzoni
2013-06-11 9:33 ` Sebastian Hesselbarth
2013-06-13 9:25 ` Sascha Hauer
2013-06-13 9:38 ` Sebastian Hesselbarth
2013-06-13 12:48 ` Sascha Hauer [this message]
2013-06-13 18:50 ` Sebastian Hesselbarth
2013-06-17 7:47 ` Sascha Hauer
2013-06-17 10:23 ` Sebastian Hesselbarth
2013-06-17 10:40 ` Sascha Hauer
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=20130613124833.GD32299@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=thomas.petazzoni@free-electrons.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