From: Bartlomiej Sieka <tur@semihalf.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: Please pull linux-2.6-mpc52xx.git
Date: Fri, 04 Apr 2008 13:13:33 +0200 [thread overview]
Message-ID: <47F60D5D.5090402@semihalf.com> (raw)
In-Reply-To: <47F22C9A.4050501@semihalf.com>
Bartlomiej Sieka wrote:
> Hi Grant,
>
> Grant Likely wrote:
>> On Tue, Mar 25, 2008 at 11:38 AM, Bartlomiej Sieka <tur@semihalf.com>
>> wrote:
>>> Grant Likely wrote:
>>> > The one part that I have a really strong opinion on is that there
>>> > should be a full featured mpc5200 defconfig for build testing.
>>> Beyond
>>> > that (and if ojn can also be appeased) I can probably be
>>> convinced. :-)
>>>
>>> Hi Grant,
>>>
>>> How to deal with a situation where I need a particular PHY driver from
>>> libphy compiled in the kernel for one of the MPC5200 boards? Adding it
>>> to mpc5200_defconfig doesn't seem like a right thing to do.
>>
>> Why not? mpc5200_defconfig is all about compile and runtime testing
>> on many platforms to make sure drivers play well together. I have no
>> problem adding more drivers to the mpc5200 defconfig. (In fact, I
>> encourage it).
>>
>>> How to
>>> convince you (and appease ojn) to accept a patch that adds a
>>> board-specific defconfig that only slightly differs from
>>> mpc5200_defconfig? :)
>>
>> I'm thinking 'optimized' defconfigs should go into a subdirectory.
>
> This requires a change to the top-level Makefile and shepherding this
> change upstream. Could we perhaps try to avoid this by having optimized
> defconfigs in the form of, for example:
>
> arch/powerpc/configs/tqm5200_opt_defconfig
> arch/powerpc/configs/motionpro_opt_defconfig
>
> Or, to signify what is the base defconfig:
>
> arch/powerpc/configs/mpc5200_tqm5200_defconfig
> arch/powerpc/configs/mpc5200_motionpro_defconfig
>
> or even:
>
> arch/powerpc/configs/mpc5200_opt_tqm5200_defconfig
> arch/powerpc/configs/mpc5200_opt_motionpro_defconfig
>
> Would patch adding an optimized _defconfig along these lines be accepted?
Grant,
Any thoughts on the above?
Regards,
Bartlomiej
next prev parent reply other threads:[~2008-04-04 11:14 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-24 7:35 Please pull linux-2.6-mpc52xx.git Grant Likely
[not found] ` <47DE94F4.90804@semihalf.com>
2008-03-17 19:19 ` Grant Likely
2008-03-17 20:59 ` Wolfgang Denk
2008-03-17 21:43 ` Grant Likely
2008-03-17 22:28 ` Wolfgang Denk
2008-03-17 23:43 ` Grant Likely
2008-03-18 0:26 ` Wolfgang Denk
2008-03-18 2:42 ` Grant Likely
2008-03-18 12:20 ` Josh Boyer
2008-03-18 8:29 ` Bartlomiej Sieka
2008-03-18 10:04 ` Richard Purdie
2008-03-25 15:29 ` Bartlomiej Sieka
2008-03-18 14:47 ` Grant Likely
2008-03-18 16:41 ` Richard Purdie
2008-03-18 16:53 ` Grant Likely
2008-03-25 16:50 ` Bartlomiej Sieka
2008-03-25 18:49 ` Grant Likely
2008-03-25 17:38 ` Bartlomiej Sieka
2008-03-25 18:51 ` Grant Likely
2008-04-01 12:37 ` Bartlomiej Sieka
2008-04-04 11:13 ` Bartlomiej Sieka [this message]
2008-04-04 16:11 ` Grant Likely
2008-04-04 16:14 ` Grant Likely
2008-04-04 16:38 ` Olof Johansson
2008-04-04 17:15 ` Josh Boyer
2008-04-04 17:25 ` Grant Likely
2008-04-15 10:34 ` Bartlomiej Sieka
2008-03-18 7:57 ` Bartlomiej Sieka
-- strict thread matches above, loose matches on Subject: below --
2009-01-09 23:09 Grant Likely
2008-11-14 19:20 Grant Likely
2008-11-24 3:38 ` Paul Mackerras
2008-11-24 14:41 ` Grant Likely
2008-05-01 18:04 Grant Likely
2008-04-29 13:34 Grant Likely
2007-10-16 23:22 Grant Likely
2007-10-17 10:27 ` Paul Mackerras
2007-10-17 13:13 ` Grant Likely
2007-10-10 16:30 Grant Likely
2007-10-11 17:35 ` tnt
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=47F60D5D.5090402@semihalf.com \
--to=tur@semihalf.com \
--cc=grant.likely@secretlab.ca \
--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 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.