From: Peter Barada <peterb@logicpd.com>
To: linux-omap <linux-omap@vger.kernel.org>
Subject: Question regarding how to submit patches
Date: Mon, 16 Feb 2009 10:51:03 -0500 [thread overview]
Message-ID: <1234799464.3238.460.camel@blackhole> (raw)
Does anyone have a pointer on how to prepare patches for inclusion into
the linx-omap tree(s)? I'm looking for something that demonstrates it
as I'm quite unfamiliar with git...
I've got a bunch of patches to add support for Logic's OMAP 35x LV
SOM/SDK that I'd like to get integrated (and eventually carried on
upstream into mainline)...
--
Peter Barada <peterb@logicpd.com>
next reply other threads:[~2009-02-16 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 15:51 Peter Barada [this message]
2009-02-17 0:43 ` Question regarding how to submit patches Amit Kucheria
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=1234799464.3238.460.camel@blackhole \
--to=peterb@logicpd.com \
--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