* omap defconfigs in mainline tree
@ 2006-04-07 9:31 Komal Shah
2006-04-07 13:14 ` Tony Lindgren
0 siblings, 1 reply; 2+ messages in thread
From: Komal Shah @ 2006-04-07 9:31 UTC (permalink / raw)
To: linux-omap-open-source
Tony,
I want to understand why we don't push defconfigs (minus drivers
options, which are not yet in mainline) to mainline tree? If we do that
we can cover all variants as part of kautobuild, _or_ if someone gives
me idea on setting up such autobuilds (kautobuild source?) I can set it
up offline here.
---Komal Shah
http://komalshah.blogspot.com/
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: omap defconfigs in mainline tree
2006-04-07 9:31 omap defconfigs in mainline tree Komal Shah
@ 2006-04-07 13:14 ` Tony Lindgren
0 siblings, 0 replies; 2+ messages in thread
From: Tony Lindgren @ 2006-04-07 13:14 UTC (permalink / raw)
To: Komal Shah; +Cc: linux-omap-open-source
* Komal Shah <komal_shah802003@yahoo.com> [060407 02:31]:
> Tony,
>
> I want to understand why we don't push defconfigs (minus drivers
> options, which are not yet in mainline) to mainline tree? If we do that
> we can cover all variants as part of kautobuild, _or_ if someone gives
> me idea on setting up such autobuilds (kautobuild source?) I can set it
> up offline here.
We should send them, but let's get the omap i2c driver integrated first.
Then the mainline tree will be usable too.
Tony
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-04-07 13:14 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-04-07 9:31 omap defconfigs in mainline tree Komal Shah
2006-04-07 13:14 ` Tony Lindgren
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox