From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] NAND: MXS: include common.h first so cache.h is included in correct order
Date: Tue, 11 Sep 2012 08:52:23 +0200 [thread overview]
Message-ID: <201209110852.24038.marex@denx.de> (raw)
In-Reply-To: <504EBEE2.1050401@denx.de>
Dear stefano babic,
> Am 10/09/2012 22:20, schrieb Tom Warren:
> > Marek/Simon,
>
> Hi Tom,
>
> >> -----Original Message-----
> >> From: Marek Vasut [mailto:marex at denx.de]
> >> Sent: Monday, September 10, 2012 9:19 AM
> >> To: Tom Warren; sjg at chromium.org
> >> Cc: u-boot at lists.denx.de; scottwood at freescale.com; Tom Warren;
> >> sbabic at denx.de
> >> Subject: Re: [PATCH] NAND: MXS: include common.h first so cache.h is
> >> included in correct order
> >>
> >> Dear Tom Warren,
> >>
> >>> With Simon Glass's include/nand.h alignment changes, some mxs builds
> >>> were generating errors. Fix is to ensure asm/cache.h is included
> >>> before linux/mtd/nand.h. Moving common.h to top of include list does
> >>> that.
> >>>
> >>> Signed-off-by: Tom Warren <twarren@nvidia.com>
> >>
> >> Acked-by: Marek Vasut <marex@denx.de>
> >
> > Thanks. Applied to u-boot-tegra/next and pushed. I'll be moving /next to
> > /master today or tomorrow and sending a new pull request to Albert to
> > clear the decks for T30 support.
>
> That's ok, but should this not be merged instead into the i.MX
> repository ? That is also the reason why Marek CCed to me.
There's some rework of MTD going on in the tegra tree, I'd say let it slide, it
won't cause conflict.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-09-11 6:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 15:55 [U-Boot] [PATCH] NAND: MXS: include common.h first so cache.h is included in correct order Tom Warren
2012-09-10 15:58 ` Simon Glass
2012-09-10 16:18 ` Marek Vasut
2012-09-10 20:20 ` Tom Warren
2012-09-11 4:32 ` stefano babic
2012-09-11 6:52 ` Marek Vasut [this message]
2012-09-11 7:44 ` Stefano Babic
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=201209110852.24038.marex@denx.de \
--to=marex@denx.de \
--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