public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Michael Jones <michael.jones@matrix-vision.de>
Cc: linux-omap@vger.kernel.org
Subject: Re: when to submit new board support
Date: Wed, 10 Aug 2011 03:33:36 -0700	[thread overview]
Message-ID: <20110810103336.GE1939@atomide.com> (raw)
In-Reply-To: <4E425B4A.3050808@matrix-vision.de>

* 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

  reply	other threads:[~2011-08-10 10:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-10 10:19 when to submit new board support Michael Jones
2011-08-10 10:33 ` Tony Lindgren [this message]
2011-08-22  8:59   ` Michael Jones

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=20110810103336.GE1939@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=michael.jones@matrix-vision.de \
    /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