From: Paul Mundt <lethal@linux-sh.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: uclinux-dev@uclinux.org, linux-kernel@vger.kernel.org,
uclinux-dist-devel@blackfin.uclinux.org,
David McCullough <davidm@snapgear.com>,
Greg Ungerer <gerg@uclinux.org>, Jie Zhang <jie.zhang@analog.com>,
Bernd Schmidt <bernds_cb1@t-online.de>
Subject: Re: [PATCH/RFC] FDPIC: add hook for arches to customize program header parsing
Date: Sun, 14 Jun 2009 18:43:14 +0900 [thread overview]
Message-ID: <20090614094314.GF832@linux-sh.org> (raw)
In-Reply-To: <1244854869-2563-1-git-send-email-vapier@gentoo.org>
On Fri, Jun 12, 2009 at 09:01:09PM -0400, Mike Frysinger wrote:
> From: Jie Zhang <jie.zhang@analog.com>
>
> The Blackfin port has custom program header flags/addresses for
> automatically loading regions into the dedicated on-chip SRAM. So add a
> hook for ports to leverage.
>
> Signed-off-by: Jie Zhang <jie.zhang@analog.com>
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
> CC: Bernd Schmidt <bernds_cb1@t-online.de>
Acked-by: Paul Mundt <lethal@linux-sh.org>
next prev parent reply other threads:[~2009-06-14 9:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-13 1:01 [PATCH/RFC] FDPIC: add hook for arches to customize program header parsing Mike Frysinger
2009-06-13 12:23 ` [uClinux-dev] " David Howells
2009-06-13 16:13 ` Jamie Lokier
2009-06-13 16:40 ` Mike Frysinger
2009-06-13 18:25 ` Jamie Lokier
2009-06-13 18:26 ` Jamie Lokier
2009-06-14 0:32 ` Mike Frysinger
2009-06-14 0:42 ` Jie Zhang
2009-06-14 9:43 ` Paul Mundt [this message]
2009-06-15 1:43 ` Greg Ungerer
2009-06-16 8:24 ` [PATCH] " Mike Frysinger
2009-06-23 5:32 ` Andrew Morton
2009-06-23 11:04 ` Mike Frysinger
2009-12-04 17:44 ` [uClinux-dev] [PATCH/RFC] " David Howells
2009-12-05 0:28 ` Jie Zhang
2009-12-05 15:14 ` David Howells
2009-12-07 10:09 ` Mike Frysinger
2009-12-07 3:27 ` [Uclinux-dist-devel] " Zhang, Sonic
2009-12-07 10:10 ` Mike Frysinger
2009-12-07 10:17 ` Jie Zhang
2009-12-07 10:10 ` Mike Frysinger
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=20090614094314.GF832@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=bernds_cb1@t-online.de \
--cc=davidm@snapgear.com \
--cc=gerg@uclinux.org \
--cc=jie.zhang@analog.com \
--cc=linux-kernel@vger.kernel.org \
--cc=uclinux-dev@uclinux.org \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier@gentoo.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