From: Sid Boyce <sboyce@blueyonder.co.uk>
To: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Alternative for defconfig
Date: Fri, 11 Jun 2010 16:35:19 +0100 [thread overview]
Message-ID: <4C1257B7.9050100@blueyonder.co.uk> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB03233C036E@dbde02.ent.ti.com>
On 11/06/10 16:14, Gadiyar, Anand wrote:
> Laurent Pinchart wrote:
>> On Friday 11 June 2010 16:55:07 Aguirre, Sergio wrote:
>>>> On Fri, Jun 11, 2010 at 3:19 PM, Nagarajan, Rajkumar wrote:
>>>>> 1. What is the alternative way of submitting defconfig changes/files to
>>>>
>>>> LO?
>>>
>>> I don't think defconfig changes are prohibited now. If I understand
>>> correctly, Linus just hates the fact that there is a big percentage of
>>> patches for defconfigs. Maybe he wants us to hold these, and better
>>> provide higher percentage of actual code changes.
>>>
>>> What about holding defconfig changes in a separate branch, and just send
>>> them for upstream once in a while, specially if there's a big quantity of
>>> them in the queue?
>>>
>>> IMHO, defconfigs are just meant to make us life easier, but changes to them
>>> should _never_ be a fix/solution to any problem, and therefore I understand
>>> that those aren't a priority over regressions.
>>
>> My understanding is that Linus will remove all ARM defconfigs in 2.6.36,
>> unless someone can convince him not to. Board-specific defconfigs won't be
>> allowed anymore, the number of defconfigs needs to be reduced drastically
>> (ideally to one or two only).
>>
>
> There is some good work going on on the linux-arm-kernel mailing list to
> cut down heavily the ARM defconfigs. Would be good to join that discussion.
>
> For OMAP, I suppose maintaining omap1_defconfig and omap3_defconfig would
> suffice to cover all OMAPs?
>
> - Anand
If I use omap3_beagle_defconfig instead of omap3_defconfig HID is
missing from the .config and doesn't show up for selection in "make
config".
Is this an oversight or is omap3_defconfig the proper one to use.
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
next prev parent reply other threads:[~2010-06-11 15:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201006091227.29175.laurent.pinchart@ideasonboard.com>
2010-06-11 12:19 ` Alternative for defconfig Nagarajan, Rajkumar
2010-06-11 13:43 ` Felipe Contreras
2010-06-11 14:55 ` Aguirre, Sergio
2010-06-11 15:07 ` Laurent Pinchart
2010-06-11 15:12 ` Aguirre, Sergio
2010-06-11 15:14 ` Gadiyar, Anand
2010-06-11 15:26 ` Laurent Pinchart
2010-06-11 15:28 ` Aguirre, Sergio
2010-06-11 15:35 ` Sid Boyce [this message]
2010-06-11 16:09 ` Felipe Contreras
2010-06-16 7:56 ` Tony Lindgren
2010-06-17 14:23 ` Tony Lindgren
2010-06-18 13:00 ` Felipe Contreras
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=4C1257B7.9050100@blueyonder.co.uk \
--to=sboyce@blueyonder.co.uk \
--cc=linux-omap@vger.kernel.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).