From: Tony Lindgren <tony@atomide.com>
To: Mike Rapoport <mike@compulab.co.il>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: adding new board
Date: Tue, 13 Oct 2009 08:39:34 -0700 [thread overview]
Message-ID: <20091013153934.GP12700@atomide.com> (raw)
In-Reply-To: <4AD491BC.5040405@compulab.co.il>
* Mike Rapoport <mike@compulab.co.il> [091013 07:42]:
>
>
> Tony Lindgren wrote:
> > Hi,
> >
> > * Mike Rapoport <mike@compulab.co.il> [091013 00:07]:
> >> Hi all,
> >>
> >> I'd like to send patches for OMAP3 based board. My question is what branch in
> >> linux-omap tree should I use as a base for my patches?
> >
> > Please do all the patches against the most recent mainline revision.
>
> Do you mean Linus' tree or linux-omap/master?
Linus' tree please. We are just queuing up things in linux-omap master
for merging to Linus' tree.
Regards,
Tony
prev parent reply other threads:[~2009-10-13 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 6:53 adding new board Mike Rapoport
2009-10-13 14:16 ` Tony Lindgren
2009-10-13 14:42 ` Mike Rapoport
2009-10-13 15:39 ` Tony Lindgren [this message]
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=20091013153934.GP12700@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=mike@compulab.co.il \
/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