All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Linz <linz@li-pro.net>
To: Peter Barada <peterb@logicpd.com>
Cc: linux-omap <linux-omap@vger.kernel.org>
Subject: Re: Patch format for submission?
Date: Thu, 20 Aug 2009 18:02:06 +0200	[thread overview]
Message-ID: <200908201802.07169.linz@li-pro.net> (raw)
In-Reply-To: <1250695463.10817.4.camel@blitz>

Am Mittwoch, 19. August 2009 schrieb Peter Barada:
> 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.

Hi Peter,

nice to see your announcement here at linux-omap. Today I've finished my own 
port for the Logic OMAP 35x SOM based on 2.6.31-rc1. We should share our 
results befor submitting any patches to the list, or not?


-- 
Viele Grüße / Best Regards
Stephan Linz

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2009-08-20 16:02 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
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 [this message]
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=200908201802.07169.linz@li-pro.net \
    --to=linz@li-pro.net \
    --cc=linux-omap@vger.kernel.org \
    --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.