From: Michael Jones <michael.jones@matrix-vision.de>
To: linux-omap@vger.kernel.org
Cc: Tony Lindgren <tony@atomide.com>
Subject: when to submit new board support
Date: Wed, 10 Aug 2011 12:19:54 +0200 [thread overview]
Message-ID: <4E425B4A.3050808@matrix-vision.de> (raw)
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
next reply other threads:[~2011-08-10 10:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 10:19 Michael Jones [this message]
2011-08-10 10:33 ` when to submit new board support Tony Lindgren
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=4E425B4A.3050808@matrix-vision.de \
--to=michael.jones@matrix-vision.de \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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