From: Tim Bird <tim.bird@am.sony.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Peter Barada <peterb@logicpd.com>,
linux-omap <linux-omap@vger.kernel.org>
Subject: Re: Patch format for submission?
Date: Wed, 19 Aug 2009 09:31:34 -0700 [thread overview]
Message-ID: <4A8C28E6.7060209@am.sony.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0908190921130.5294@utopia.booyaka.com>
Paul Walmsley wrote:
> Hi Peter,
>
> On Wed, 19 Aug 2009, Peter Barada wrote:
>
>> 1) Does anyone have a URL of the format patches should be in that are
>> submitted to the linux-omap list?
>>
>> I've got some patches to add base support for the Logic OMAP 35x SOM and
>> Torpedo boards and I'd like to submit them in the right format for
>> inclusion and push into mainline.
>
> Documentation/SubmittingPatches and Documentation/CodingStyle are pretty
> good intros to this.
>
Also, Andrew Morton wrote a paper called "The Perfect Patch"
with a nice checklist of attributes.
http://userweb.kernel.org/~akpm/stuff/tpp.txt
-- Tim
=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Corporation of America
=============================
next prev parent reply other threads:[~2009-08-19 16:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 15:24 Patch format for submission? Peter Barada
2009-08-19 15:22 ` Paul Walmsley
2009-08-19 16:31 ` Tim Bird [this message]
2009-08-21 13:10 ` Kevin Hilman
2009-08-21 14:34 ` Peter Barada
2009-08-21 15:20 ` Jean Pihet
2009-08-24 15:55 ` Kalle Valo
2009-08-23 21:36 ` Felipe Balbi
2009-08-19 15:46 ` Amit Kucheria
2009-08-20 16:02 ` Stephan Linz
2010-04-29 17:18 ` OMAP 3530 LV-SOM support (was: Re: Patch format for submission?) Zygo Blaxell
2010-05-01 2:12 ` Ashwin Bihari
2010-05-03 14:13 ` Stephan Linz
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=4A8C28E6.7060209@am.sony.com \
--to=tim.bird@am.sony.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=peterb@logicpd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.