From: "Rogério Brito" <rbrito@ime.usp.br>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linuxppc-dev@ozlabs.org, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: Regarding the linkstation defconfig
Date: Fri, 24 Apr 2009 18:23:12 -0300 [thread overview]
Message-ID: <20090424212311.GA7858@ime.usp.br> (raw)
In-Reply-To: <Pine.LNX.4.64.0904242158210.8309@axis700.grange>
Dear Guennadi, and Kumar.
On Apr 24 2009, Guennadi Liakhovetski wrote:
> On Fri, 24 Apr 2009, Rogério Brito wrote:
> > Guennadi, since you seem to be the one responsible for the
> > linkstation/kurobox in the kernel,
>
> That's not howI interpret my role in linkstation development /
> support.
Sorry. I thought that you were. I have, nonetheless, interest in helping
and understanding more about the platform.
> > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> > 01. why is anticipatory the default scheduler for linkstations when CFQ
> > is the default scheduler for the rest of the kernel?
(...)
> > 12. wouldn't it be a good thing to enable CONFIG_PRINTK_TIME?
> > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
> As I already replied to you earlier, I am not particularly interested in
> fine-tuning and optimisation of defconfigs. IMHO *_defconfigs are only
> examples of board configuration, that are known to build and work. The
> rest is up to the user / packager.
IMVHO, defconfigs should be examples of board configuration, known to
build and work (like you said) *and* be, in a way, exemplary to the
user/packager.
> > Again, please, forgive my ignorance here regarding the questions above.
> > I'm really looking for some clarification and to get things in shape
> > both on my systems and in the default kernel configuration, in general.
>
> Feel free to submit patches with reasoning to the powerpc ML and
> respective maintainer as per MAINTAINERS file.
I'm doing that as a reply to this message.
Thanks for your guiding, Rogério Brito.
--
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
next prev parent reply other threads:[~2009-04-24 21:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 6:58 Regarding the linkstation defconfig Rogério Brito
2009-04-24 20:05 ` Guennadi Liakhovetski
2009-04-24 21:23 ` Rogério Brito [this message]
2009-04-24 22:33 ` [PATCH] powerpc: minimizing the configuration of linkstation_defconfig Rogério Brito
2009-04-27 19:29 ` Kumar Gala
2009-04-28 2:27 ` Rogério Brito
2009-04-28 13:16 ` Kumar Gala
2009-04-28 14:48 ` Rogério Brito
2009-04-28 14:54 ` Kumar Gala
2009-04-28 13:03 ` [PATCH 1/2] powerpc: updating the linkstation_defconfig Rogério Brito
2009-04-28 13:32 ` [PATCH 2/2] powerpc: minimizing the configuration of linkstation_defconfig Rogério Brito
2009-05-16 16:04 ` [PATCH] " Rogério Brito
2009-06-11 2:46 ` Kumar Gala
2009-04-28 16:44 ` [PATCH 2/2] " Rogério Brito
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=20090424212311.GA7858@ime.usp.br \
--to=rbrito@ime.usp.br \
--cc=g.liakhovetski@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).