From: Nicolas Pitre <nico@fluxnic.net>
To: Rob Herring <robherring2@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
Paul Gortmaker <paul.gortmaker@windriver.com>,
linux-next@vger.kernel.org, Rob Herring <rob.herring@calxeda.com>,
Eric Miao <eric.y.miao@gmail.com>,
Russell King <linux@arm.linux.org.uk>,
Haojian Zhuang <haojian.zhuang@marvell.com>,
Alessandro Zummo <a.zummo@towertech.it>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
rtc-linux@googlegroups.com, alsa-devel@alsa-project.org
Subject: Re: [PATCH 2/2] ARM: pxa: use commom IOMEM definiton
Date: Tue, 20 Mar 2012 22:33:07 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.02.1203202231420.24151@xanadu.home> (raw)
In-Reply-To: <1332296149-28110-2-git-send-email-robherring2@gmail.com>
On Tue, 20 Mar 2012, Rob Herring wrote:
> From: Rob Herring <rob.herring@calxeda.com>
>
> pxa was missed in the moving of IOMEM to a common defintion, so lots of
> IOMEM redefined warnings were introduced. So remove pxa IOMEM definition
> and fix all the fallout.
You've got at least 3 typos in the above, with 2 of them in the subject
line alone. ;-)
Nicolas
next prev parent reply other threads:[~2012-03-21 2:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 18:34 linux-next: "ARM: make mach/io.h include optional" commit breaks cm_x2xx_defconfig Paul Gortmaker
2012-03-20 21:33 ` Rob Herring
2012-03-21 2:15 ` [PATCH 1/2] ARM: dma-mapping: convert ARCH_HAS_DMA_SET_COHERENT_MASK to kconfig symbol Rob Herring
2012-03-21 2:15 ` [PATCH 2/2] ARM: pxa: use commom IOMEM definiton Rob Herring
2012-03-21 2:33 ` Nicolas Pitre [this message]
2012-03-22 13:42 ` [PATCH v2] ARM: pxa: use common IOMEM definition Rob Herring
2012-03-25 7:47 ` Russell King - ARM Linux
2012-03-21 2:30 ` [PATCH 1/2] ARM: dma-mapping: convert ARCH_HAS_DMA_SET_COHERENT_MASK to kconfig symbol Nicolas Pitre
2012-03-21 8:15 ` Haojian Zhuang
2012-03-21 20:13 ` Rob Herring
2012-03-21 22:17 ` Haojian Zhuang
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=alpine.LFD.2.02.1203202231420.24151@xanadu.home \
--to=nico@fluxnic.net \
--cc=a.zummo@towertech.it \
--cc=alsa-devel@alsa-project.org \
--cc=eric.y.miao@gmail.com \
--cc=haojian.zhuang@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=paul.gortmaker@windriver.com \
--cc=perex@perex.cz \
--cc=rob.herring@calxeda.com \
--cc=robherring2@gmail.com \
--cc=rtc-linux@googlegroups.com \
--cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).