From: "Eric Miao" <eric.y.miao@gmail•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org
Subject: Re: linux-next: manual merge of the pxa tree
Date: Fri, 12 Sep 2008 08:49:55 +0800 [thread overview]
Message-ID: <f17812d70809111749n1f0300c8j2f69d933d2c8fdf6@mail.gmail.com> (raw)
In-Reply-To: <20080912083515.19517514.sfr@canb.auug.org.au>
On Fri, Sep 12, 2008 at 6:35 AM, Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> Hi Eric,
>
> Today's linux-next merge of the pxa tree got a conflict in
> arch/arm/mach-pxa/corgi.c arch/arm/mach-pxa/spitz.c between commit
> fced80c735941fa518ac67c0b61bbe153fb8c050 ("[ARM] Convert asm/io.h to
> linux/io.h") from the arm tree and commits
> c22e92f200a2b5ab8b3571747865afe3dcc7b6b3 ("[ARM] pxa/corgi: use SPI-based
> driver for ads7846, corgi-lcd and max1111"),
> db710817e3432af4d30896cdc41f144e4da7c7e2 ("[ARM] pxa/akita: use pca953x
> instead of akita-ioexp") and 43d5f82350734562e22b9ad9de3ad0aaec6aaffe
> ("[ARM] pxa/spitz: use SPI-based driver for ads7846, corgi-lcd and
> max1111") from the pxa tree.
>
> Just overlapping additions of includes. I fixed it up (see below) and
> can carry the fixup.
>
Just found that, the fixup looks correct to me. Thanks.
next prev parent reply other threads:[~2008-09-12 0:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 22:35 linux-next: manual merge of the pxa tree Stephen Rothwell
2008-09-12 0:49 ` Eric Miao [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-14 19:27 Stephen Rothwell
[not found] ` <20080915052750.0b0c924c.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2008-09-15 13:18 ` Ned Forrester
2008-09-16 3:02 ` Eric Miao
2008-09-25 4:57 ` [spi-devel-general] " David Brownell
2008-09-25 7:49 ` Eric Miao
[not found] ` <f17812d70809250049g3f3b86e7x12dab8cc4f8b1cd6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-09-25 8:20 ` David Brownell
2008-09-17 20:31 Stephen Rothwell
2008-09-17 21:40 ` Russell King
2008-09-17 22:14 ` Stephen Rothwell
2008-09-17 22:28 ` Russell King
2008-09-18 0:02 ` Stephen Rothwell
2008-09-18 18:46 Stephen Rothwell
2008-09-18 19:00 ` Eric Miao
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=f17812d70809111749n1f0300c8j2f69d933d2c8fdf6@mail.gmail.com \
--to=eric.y.miao@gmail$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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