From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Hunter, Jon" <jon-hunter@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: ARM: CONFIG_FRAME_POINTER
Date: Wed, 13 May 2009 11:09:07 -0700 [thread overview]
Message-ID: <87d4ac6fjw.fsf@deeprootsystems.com> (raw)
In-Reply-To: <7B4574D56E4ADF438756313E9A172A87396A2052@dlee01.ent.ti.com> (Jon Hunter's message of "Wed\, 13 May 2009 13\:05\:22 -0500")
"Hunter, Jon" <jon-hunter@ti.com> writes:
> Hi Kevin,
>
>> Yes. Do you mind sending a patch to linux-arm-kernel?
>
> Sure. Does Russell King maintain a git tree for linux-arm or do you
> have any advice which tree I should use to base a patch on for the
> linux-arm folks?
Just base it at Linus' master branch or the latest -rc tag.
Kevin
next prev parent reply other threads:[~2009-05-13 18:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 21:46 ARM: CONFIG_FRAME_POINTER Hunter, Jon
2009-05-12 23:33 ` Kevin Hilman
2009-05-13 3:09 ` Woodruff, Richard
2009-05-13 15:48 ` Hunter, Jon
2009-05-13 15:55 ` Woodruff, Richard
2009-05-13 16:06 ` Hunter, Jon
2009-05-13 16:10 ` Woodruff, Richard
2009-05-13 15:42 ` Hunter, Jon
2009-05-13 16:37 ` Kevin Hilman
2009-05-13 18:05 ` Hunter, Jon
2009-05-13 18:09 ` Kevin Hilman [this message]
2009-05-13 19:16 ` Hunter, Jon
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=87d4ac6fjw.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=jon-hunter@ti.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