From: tony@atomide.com
To: Brian Swetland <swetland@google.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: fsample support patch (core omap only)
Date: Fri, 28 Apr 2006 01:15:46 -0700 [thread overview]
Message-ID: <20060428081545.GE31797@atomide.com> (raw)
In-Reply-To: <20060413170611.GA5510@localhost.localdomain>
* Brian Swetland <swetland@google.com> [060413 10:07]:
>
> Here's a revised version of my original patch, using cpu_is_*()
> and only including the core omap files.
Looks good & sorry for delay in replying. Just few more nitpicking
comments to make the patch usable for sending upstream as-is:
- Please repost with subject: [PATCH] ARM: OMAP: Add core fsample support
- Then body that says something like "This patch adds core fsample
support", and add Signed-off-by line
- Please separate arch/arm/tools/mach-types into yet another separate
patch as we don't need to send that chunk upstream
And just to recap, we want to have core omap support in sync with
mainline and want to produce patches that work against the mainline
tree without rewriting :)
> Device patches to follow.
Great!
Tony
prev parent reply other threads:[~2006-04-28 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 17:06 fsample support patch (core omap only) Brian Swetland
2006-04-28 8:15 ` tony [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=20060428081545.GE31797@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=swetland@google.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