From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] linkage.h: move from blackfin to common includes
Date: Tue, 10 Jan 2012 20:27:20 -0500 [thread overview]
Message-ID: <201201102027.20776.vapier@gentoo.org> (raw)
In-Reply-To: <201112011305.44388.vapier@gentoo.org>
On Thursday 01 December 2011 13:05:42 Mike Frysinger wrote:
> On Wednesday 30 November 2011 23:32:10 Macpaul Lin wrote:
> > 1. Add linkage.h support from blackfin to common include,
> >
> > which is a reduced version from Linux.
> >
> > 2. Add architecture part support of linkage.h into blackfin
> > 3. Fix include path of in blackfin related to linkage.h
> >
> > due to header file movement.
>
> i'll test it out and run it through my Blackfin tree. let's see if any one
> else has any feedback ...
FYI, i'll be including it as part of my Blackfin merge when the window closes
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20120110/a6d90a7c/attachment.pgp>
next prev parent reply other threads:[~2012-01-11 1:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 7:23 [U-Boot] [PATCH 1/3] linkage.h: move from blackfin to common includes Macpaul Lin
2011-11-30 7:23 ` [U-Boot] [PATCH 2/3] blackfin: add architecture part support of linkage.h Macpaul Lin
2011-11-30 7:23 ` [U-Boot] [PATCH 3/3] blackfin: fix linkage support due to header movement Macpaul Lin
2011-11-30 16:25 ` [U-Boot] [PATCH 1/3] linkage.h: move from blackfin to common includes Mike Frysinger
2011-12-01 4:32 ` [U-Boot] [PATCH v2] " Macpaul Lin
2011-12-01 18:05 ` Mike Frysinger
2012-01-11 1:27 ` Mike Frysinger [this message]
2012-01-11 1:57 ` Macpaul Lin
2012-01-11 2:05 ` [U-Boot] [PATCH 1/3] " Fabio Estevam
2012-01-11 2:21 ` 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=201201102027.20776.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=u-boot@lists.denx.de \
/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