public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Graeme Russ <graeme.russ@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: Add option to disable code relocation
Date: Tue, 07 Feb 2012 20:52:30 +1100	[thread overview]
Message-ID: <4F30F45E.3030204@gmail.com> (raw)
In-Reply-To: <CAPnjgZ1PWGnFjpjw=EKPt-3tDKe7Lw2G65RjOPqrVAQ_fHMBJg@mail.gmail.com>

Hi Simon,

On 02/06/2012 10:41 AM, Simon Glass wrote:
> Hi Graeme,
> 
> On Sun, Feb 5, 2012 at 3:37 PM, Graeme Russ <graeme.russ@gmail.com> wrote:
>> Hi Simon
>>
>> On Mon, Feb 6, 2012 at 10:32 AM, Simon Glass <sjg@chromium.org> wrote:
>>> Hi Graeme,

[snip]

>>> Which reminds me - did you do that pull request for your x86 refactor?
>>> If not, what is the plan?
>>
>> I pushed the changes into the x86 sub-repo but noticed a minor glitch
>> which breaks the build. On top of that, I've upgraded my dev machine to
>> a 64-bit arch, moved from Ubuntu to Fedora and got a dud motherboard in
>> the mix. So my dev machine is only just now back online, but I need to
>> sort out the last few 64-bit build issues (which require U-Boot patches)
>> and fix up the x86 sub-repo before sending the pull request.

OK, it turned out there was no glitch - In the process of upgrading my dev
PC my local git repo git a bit confused (I think the timestamps went off
into lala land). Anyway, I backed-up all my dev patches and re-cloned a
fresh copy from git.denx.de and all appears to build fine

>> Sorry for the dealy, but hopefully I'll have it all sorted by the end of
>> the week
> 
> OK thanks for the update. Would be keen to get my generic board stuff
> tested on x86 also, but that might be a separate problem. For
> initcalls, are you still thinking of looking at that?

If you want to fetch the x86 repo, you can work off it until Wolfgang does
the pull

Regards,

Graeme

  parent reply	other threads:[~2012-02-07  9:52 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-05  6:44 [U-Boot] [PATCH] arm: Add option to disable code relocation Simon Glass
2012-02-05  7:39 ` Mike Frysinger
2012-02-05 12:05   ` Marek Vasut
2012-02-05 20:38     ` Mike Frysinger
2012-02-05 21:40       ` Simon Glass
2012-02-05 22:44         ` Wolfgang Denk
2012-02-05 23:23           ` Graeme Russ
2012-02-05 23:32             ` Simon Glass
2012-02-05 23:37               ` Graeme Russ
2012-02-05 23:41                 ` Simon Glass
2012-02-05 23:46                   ` Graeme Russ
2012-02-07  9:52                   ` Graeme Russ [this message]
2012-02-06  7:51             ` Wolfgang Denk
2012-02-06  8:43               ` Graeme Russ
2012-02-06 14:49                 ` Tom Rini
2012-02-06 19:27                   ` Mike Frysinger
2012-02-06 19:46                     ` Tom Rini
2012-02-06 20:25                     ` Graeme Russ
2012-02-07  6:41                       ` Dirk Behme
2012-02-07 23:23                         ` Wolfgang Denk
2012-02-07 23:28                           ` Graeme Russ
2012-02-07 23:36                             ` Wolfgang Denk
2012-02-07 23:48                               ` Graeme Russ
2012-02-08  6:42                                 ` Dirk Behme
2012-02-08  6:51                               ` Dirk Behme
2012-02-08  7:12                                 ` Simon Glass
2012-02-08  7:16                                   ` Dirk Behme
2012-02-08 22:05                                   ` Graeme Russ
2012-02-09  3:38                                   ` Graeme Russ
2012-02-09 18:30                                     ` Simon Glass
2012-02-08 14:03                                 ` Wolfgang Denk
2012-02-06 21:17                     ` Albert ARIBAUD
2012-02-06 22:24                       ` Wolfgang Denk
2012-02-07  6:51                       ` Dirk Behme
2012-02-07  7:25                   ` Aneesh V
2012-02-05 23:32           ` Simon Glass
2012-02-05 12:05 ` Marek Vasut
2012-02-05 18:54 ` Wolfgang Denk

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=4F30F45E.3030204@gmail.com \
    --to=graeme.russ@gmail.com \
    --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