All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Warren <twarren.nvidia@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] pull request for u-boot-tegra/master into ARM/master
Date: Fri, 16 Nov 2012 14:45:49 -0700	[thread overview]
Message-ID: <CA+m5__LkjjFVEouT2YqzDp7N6UN0aOzdb4TecBcP6RH+dz9aOg@mail.gmail.com> (raw)
In-Reply-To: <20121116222724.3e3050c2@lilith>

Albert,

A fix was found and posted awhile back by Simon (195662 on PatchWork -
it's assigned to you as delegate). Marek's last comment was 'Just
apply this', so I suppose that's his version of an Acked-by.  I don't
carry that fix in my tree since it's not specifically Tegra-related.
I can add it and resend a pull request, or you can apply it to
ARM/master and I can rebase on that (though I don't think that'll
change my pull request much, if at all).

Let me know,

Tom

On Fri, Nov 16, 2012 at 2:27 PM, Albert ARIBAUD
<albert.u.boot@aribaud.net> wrote:
> Hi Tom,
>
> On Fri, 16 Nov 2012 10:14:46 -0700, Tom Warren
> <twarren.nvidia@gmail.com> wrote:
>
>> Albert,
>>
>> Please pull u-boot-tegra/master into ARM/master. Thanks!
>>
>> ./MAKEALL -a arm completes w/o any new errors.
>> checkpatch is clean, also.
>
> I see three boards failing which do build on current u-boot-arm/master:
>
> palmld palmtc zipitz2
>
> All have the same error:
>
> /home/albert/src/u-boot-arm/common/lcd.c:125: undefined
> reference to `flush_dcache_range'
>
> git bisect run ./MAKEALL zipitz2 traces the problem to commit
> 9c9e9b0d... "lcd: Add support for flushing LCD fb from dcache after
> update" from Simon Glass (already Cc:).
>
> Simon, can you look into this?
>
> Tom, can you provide a fixed pull request once the issue is fixed?
>
> Amicalement,
> --
> Albert.

  reply	other threads:[~2012-11-16 21:45 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-16 17:14 [U-Boot] pull request for u-boot-tegra/master into ARM/master Tom Warren
2012-11-16 21:27 ` Albert ARIBAUD
2012-11-16 21:45   ` Tom Warren [this message]
2012-11-16 23:33     ` Albert ARIBAUD
2012-11-16 23:42       ` Tom Warren
2012-11-17  0:12         ` Albert ARIBAUD
2012-11-19 15:39           ` Tom Warren
2012-11-19 17:12             ` Tom Warren
2012-11-20  6:21               ` Albert ARIBAUD
  -- strict thread matches above, loose matches on Subject: below --
2014-08-20 16:12 Tom Warren
2014-08-29 17:48 ` Tom Rini
2014-06-19 17:53 Tom Warren
2014-07-01 16:58 ` Albert ARIBAUD
2014-06-06 15:53 Tom Warren
2014-06-08  7:13 ` Albert ARIBAUD
2014-05-13 21:14 Tom Warren
2014-05-15 16:15 ` Albert ARIBAUD
2014-04-17 16:08 Tom Warren
2014-04-21 19:00 ` Albert ARIBAUD
2014-03-06 15:39 Tom Warren
2014-03-07 14:30 ` Albert ARIBAUD
2014-02-04 23:19 Tom Warren
2014-02-11 16:42 ` Stephen Warren
2014-02-11 16:48   ` Albert ARIBAUD
2014-02-11 16:59     ` Stephen Warren
2014-02-11 17:48       ` Albert ARIBAUD
2014-02-12 17:12 ` Albert ARIBAUD
2013-12-18 20:06 Tom Warren
2013-12-18 21:18 ` Albert ARIBAUD
2013-12-18 22:28   ` Tom Warren
2013-08-19 22:57 Tom Warren
2013-09-04  9:49 ` Albert ARIBAUD
2013-07-11 22:00 Tom Warren
2013-07-12  7:51 ` Albert ARIBAUD
2013-06-06 16:30 Tom Warren
2013-06-07  8:06 ` Albert ARIBAUD
2013-05-28 21:16 Tom Warren
2013-05-29 16:16 ` Albert ARIBAUD
2013-04-15 23:28 Tom Warren
2013-04-16 17:17 ` Albert ARIBAUD
2013-04-16 19:55   ` Stephen Warren
2013-04-16 20:02     ` Tom Warren
2013-04-17  6:56     ` Albert ARIBAUD
2013-04-16 20:55 ` Albert ARIBAUD
2013-03-25 17:43 Tom Warren
2013-03-26 10:12 ` Albert ARIBAUD
2013-03-15 15:25 Tom Warren
2013-03-15 20:46 ` Albert ARIBAUD
2013-01-18 16:00 Tom Warren
2013-01-18 16:06 ` Albert ARIBAUD
2012-10-29 23:49 Tom Warren
2012-11-03  9:03 ` Albert ARIBAUD

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=CA+m5__LkjjFVEouT2YqzDp7N6UN0aOzdb4TecBcP6RH+dz9aOg@mail.gmail.com \
    --to=twarren.nvidia@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.