linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
To: Michal Simek <monstr@monstr.eu>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: Proposed prom parse fix + moving.
Date: Fri, 17 Apr 2009 16:02:03 +0300 (EEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0904171601020.10088@wrl-59.cs.helsinki.fi> (raw)
In-Reply-To: <49E87D25.8090001@monstr.eu>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1616 bytes --]

On Fri, 17 Apr 2009, Michal Simek wrote:

> Grant Likely wrote:
> > On Fri, Apr 17, 2009 at 12:08 AM, Michal Simek <monstr@monstr.eu> wrote:
> >> Hi All,
> >>
> >> I have got email from Ilpo about prom_parse file.
> >> I take this file from powerpc. Who did write prom_parse file and take care about?
> > 
> > Posting to the linuxppc-dev list is sufficient to start.  There are
> > several people who may be interested.
> > 
> >> BTW: What about to move prom_parse file to any generic location as we discussed in past?
> >> Any volunteer?
> > 
> > I'm kind of working on it.  More specifically, I'm looking at
> > factoring out fdt stuff into common code (drivers/of/of_fdt.c). But I
> > haven't made a whole lot of progress yet.
> > 
> >> -------- Original Message --------
> >> Subject: [RFC!] [PATCH] microblaze: fix bug in error handling
> >> Date: Thu, 16 Apr 2009 23:05:53 +0300 (EEST)
> >> From: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi>
> >> To: monstr@monstr.eu
> >> CC: microblaze-uclinux@itee.uq.edu.au
> >>
> >> While some version of the patches were on the lkml I read
> >> some part of the code briefly through but my feedback got
> >> stuck into postponed emails, so here's one correctness
> >> related issue I might have found (the rest were just
> >> cosmetic things).
> >>
> >> I'm not sure if the latter return needs the of_node_put or not
> >> but it seems more likely than not.
> > 
> > Yes, it does.  This change is applicable to
> > arch/powerpc/kernel/prom_parse.c too.
> 
> ok.
> Ilpo: Can you create patch for both architectures?

Sure, but tomorrow as today is a deadline day :-).

-- 
 i.

  reply	other threads:[~2009-04-17 13:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17  6:08 Proposed prom parse fix + moving Michal Simek
2009-04-17  6:44 ` Grant Likely
2009-04-17 12:59   ` Michal Simek
2009-04-17 13:02     ` Ilpo Järvinen [this message]
2009-04-17 22:07       ` Ilpo Järvinen
2009-04-18  5:35         ` Grant Likely
2009-04-20 21:15           ` Grant Likely
2009-04-17  7:43 ` Benjamin Herrenschmidt

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=Pine.LNX.4.64.0904171601020.10088@wrl-59.cs.helsinki.fi \
    --to=ilpo.jarvinen@helsinki.fi \
    --cc=arnd@arndb.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=monstr@monstr.eu \
    /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).