public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
* when to submit new board support
@ 2011-08-10 10:19 Michael Jones
  2011-08-10 10:33 ` Tony Lindgren
  0 siblings, 1 reply; 3+ messages in thread
From: Michael Jones @ 2011-08-10 10:19 UTC (permalink / raw)
  To: linux-omap; +Cc: Tony Lindgren

I would like to submit some patches to add support for a new OMAP board...

Is there a right or wrong time to post such patches to this list? How
does the kernel merge window effect what kind of patches are expected
here on the OMAP list?

What should I use as the base for my patches? At
http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git,
at the moment 'master' hasn't been updated for 4 weeks. Should I base it
on v3.1-rc1 instead (as an example, since I won't manage to submit it
while v3.1-rc1 is the most recent tag)?

thanks,
Michael

MATRIX VISION GmbH, Talstrasse 16, DE-71570 Oppenweiler
Registergericht: Amtsgericht Stuttgart, HRB 271090
Geschaeftsfuehrer: Gerhard Thullner, Werner Armingeon, Uwe Furtner, Erhard Meier

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: when to submit new board support
  2011-08-10 10:19 when to submit new board support Michael Jones
@ 2011-08-10 10:33 ` Tony Lindgren
  2011-08-22  8:59   ` Michael Jones
  0 siblings, 1 reply; 3+ messages in thread
From: Tony Lindgren @ 2011-08-10 10:33 UTC (permalink / raw)
  To: Michael Jones; +Cc: linux-omap

* Michael Jones <michael.jones@matrix-vision.de> [110810 03:14]:
> I would like to submit some patches to add support for a new OMAP board...
> 
> Is there a right or wrong time to post such patches to this list? How
> does the kernel merge window effect what kind of patches are expected
> here on the OMAP list?

Well this is the right time, however we're moving things to device tree
and coalescing code. So you may need to be prepared to update the patches
a few times before we get them to mainline.
 
> What should I use as the base for my patches? At
> http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git,
> at the moment 'master' hasn't been updated for 4 weeks. Should I base it
> on v3.1-rc1 instead (as an example, since I won't manage to submit it
> while v3.1-rc1 is the most recent tag)?

Yes v3.1-rc1 should be used as the base. I've been on vacation and
have not updated the omap tree for a while, will updated it soonish,
but will be just v3.1-rc1 + bug fixes.

Tony

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: when to submit new board support
  2011-08-10 10:33 ` Tony Lindgren
@ 2011-08-22  8:59   ` Michael Jones
  0 siblings, 0 replies; 3+ messages in thread
From: Michael Jones @ 2011-08-22  8:59 UTC (permalink / raw)
  To: Tony Lindgren; +Cc: linux-omap

Hi Tony,

Thanks for the reply.

On 08/10/2011 12:33 PM, Tony Lindgren wrote:
> 
> * Michael Jones <michael.jones@matrix-vision.de> [110810 03:14]:
>> I would like to submit some patches to add support for a new OMAP board...
>>
>> Is there a right or wrong time to post such patches to this list? How
>> does the kernel merge window effect what kind of patches are expected
>> here on the OMAP list?
> 
> Well this is the right time, however we're moving things to device tree
> and coalescing code. So you may need to be prepared to update the patches
> a few times before we get them to mainline.

Unfortunately I am not ready to pull the trigger on submitting my code
right _now_, so I was hoping to get a better understanding of the
system- when the right time would be AND when the wrong time would be.
I.e. what makes "this" the right time?

Also, I'm uncertain whether my submission will generally be welcome. Are
there criteria for which boards are desirable to merge upstream? In
April [1] you said in response to the inquiry about submitting support
for the Nook Color that usually supporting a new machine adds "a few
tens of lines". My machine is not even on the market yet, and its board
file is currently 384 lines long, which is more than a few tens. I don't
want to submit unwanted bloat.

I'm not familiar yet with Device Tree, so I don't understand what the
implications are for existing supported boards and their board files,
but I would of course be prepared to make necessary changes after review.

-Michael

[1] http://www.mail-archive.com/linux-omap%40vger.kernel.org/msg48348.html

>  
>> What should I use as the base for my patches? At
>> http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git,
>> at the moment 'master' hasn't been updated for 4 weeks. Should I base it
>> on v3.1-rc1 instead (as an example, since I won't manage to submit it
>> while v3.1-rc1 is the most recent tag)?
> 
> Yes v3.1-rc1 should be used as the base. I've been on vacation and
> have not updated the omap tree for a while, will updated it soonish,
> but will be just v3.1-rc1 + bug fixes.
> 
> Tony


MATRIX VISION GmbH, Talstrasse 16, DE-71570 Oppenweiler
Registergericht: Amtsgericht Stuttgart, HRB 271090
Geschaeftsfuehrer: Gerhard Thullner, Werner Armingeon, Uwe Furtner, Erhard Meier

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2011-08-22  8:59 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-08-10 10:19 when to submit new board support Michael Jones
2011-08-10 10:33 ` Tony Lindgren
2011-08-22  8:59   ` Michael Jones

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox