From: Matt Sealey <matt@genesi-usa•com>
To: Kumar Gala <galak@kernel•crashing.org>
Cc: linuxppc-dev <linuxppc-dev@ozlabs•org>,
Paul Mackerras <paulus@samba•org>
Subject: Re: mpc52xx bestcomm patches.
Date: Mon, 15 Oct 2007 12:30:07 +0100 [thread overview]
Message-ID: <47134F3F.2020901@genesi-usa.com> (raw)
In-Reply-To: <DDF4941D-02CA-49FA-999D-8BD08740902C@kernel.crashing.org>
Kumar Gala wrote:
>> The problem is that bestcomm is completely stalled on Sylvain. He's
>> done good work, but he isn't able to put in the effort for the last
>> push to get it fixed and in. But until that happens, nobody else will
>> step in to add patches on top of it to fix it up.
>
> If Sylvain doesn't have the time can't someone else pick up what he's
> done and fixup the issues with it?
I second that motion!
There are a few minor quibbles I have with Sylvain's implementation (it
seems to have ditched some perfectly sound ideas of the original API plus
additions made by bplan for using the device tree to resolve tasks, in
favour of making the API entirely driver-dependant, and Linux-dependant
(it trashes any existing device table) also it has a few "5200-specific"
features like disabling task prefetch (errata not present in 5200B onwards).
It needs some looking at. But, this can be merged in my opinion, we can
just throw it to the list right now, and take the niggles to the list
and have a discussion about it..
In the absense of one guy hammering at the code let's just get 20 people
to review it, right here, with a new submission..
--
Matt Sealey <matt@genesi-usa•com>
Genesi, Manager, Developer Relations
prev parent reply other threads:[~2007-10-15 11:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 18:30 mpc52xx bestcomm patches Grant Likely
2007-10-12 18:40 ` Kumar Gala
2007-10-12 18:54 ` Grant Likely
2007-10-12 20:11 ` Kumar Gala
2007-10-12 20:30 ` Grant Likely
2007-10-15 11:30 ` Matt Sealey [this message]
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=47134F3F.2020901@genesi-usa.com \
--to=matt@genesi-usa$(echo .)com \
--cc=galak@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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