From: Tony Lindgren <tony@atomide.com>
To: Sergei Shtylyov <sshtylyov@mvista.com>
Cc: Jan Weitzel <j.weitzel@phytec.de>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] ARM: OMAP4: Add pcm049 to Kconfig/Makefile
Date: Fri, 8 Jul 2011 04:55:21 -0700 [thread overview]
Message-ID: <20110708115521.GA5783@atomide.com> (raw)
In-Reply-To: <4E16EECF.7030102@mvista.com>
* Sergei Shtylyov <sshtylyov@mvista.com> [110708 04:45]:
> Hello.
>
> On 08-07-2011 14:04, Jan Weitzel wrote:
>
> >Signed-off-by: Jan Weitzel<j.weitzel@phytec.de>
> >---
> > arch/arm/mach-omap2/Kconfig | 5 +++++
> > arch/arm/mach-omap2/Makefile | 4 ++++
> > 2 files changed, 9 insertions(+), 0 deletions(-)
>
> >diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig
> >index 19d5891..c6a2d43 100644
> >--- a/arch/arm/mach-omap2/Kconfig
> >+++ b/arch/arm/mach-omap2/Kconfig
> [...]
> >diff --git a/arch/arm/mach-omap2/Makefile b/arch/arm/mach-omap2/Makefile
> >index b148077..e81b594 100644
> >--- a/arch/arm/mach-omap2/Makefile
> >+++ b/arch/arm/mach-omap2/Makefile
> >@@ -238,6 +238,10 @@ obj-$(CONFIG_MACH_OMAP4_PANDA) += board-omap4panda.o \
> > hsmmc.o \
> > omap_phy_internal.o
> >
> >+obj-$(CONFIG_MACH_PCM049) += board-omap4pcm049.o \
>
> You need to first add board-omap4pcm049.c, and only then wire it
> to the Makefile. You could do both in onme patch though...
Yes looks like this should be just one patch for everything.
Regards,
Tony
next prev parent reply other threads:[~2011-07-08 11:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 10:04 [PATCH 0/3] ARM:OMAP4 add Phytec phyCORE-OMAP4 board Jan Weitzel
2011-07-08 10:04 ` [PATCH 1/3] ARM: OMAP4: Add pcm049 to Kconfig/Makefile Jan Weitzel
2011-07-08 11:49 ` Sergei Shtylyov
2011-07-08 11:55 ` Tony Lindgren [this message]
2011-07-08 11:58 ` Felipe Balbi
2011-07-14 7:27 ` Tony Lindgren
2011-07-14 7:47 ` Tony Lindgren
2011-07-08 12:21 ` [PATCH v2] ARM:OMAP4 add Phytec phyCORE-OMAP4 board Jan Weitzel
2011-07-13 8:03 ` Tony Lindgren
2011-07-13 10:58 ` Jan Weitzel
2011-07-13 10:59 ` [PATCH] ARM: OMAP4: PCM049: remove vusim regulator Jan Weitzel
2011-07-13 12:13 ` Sergei Shtylyov
2011-07-13 12:54 ` [PATCH v2] " Jan Weitzel
2011-07-13 12:56 ` [PATCH] " Jan Weitzel
2011-07-14 7:34 ` Tony Lindgren
2011-07-14 8:39 ` Jan Weitzel
2011-07-15 7:50 ` Tony Lindgren
2011-07-15 7:58 ` Felipe Balbi
2011-07-15 8:20 ` Tony Lindgren
2011-07-15 8:31 ` Felipe Balbi
2011-07-15 10:59 ` Tony Lindgren
2011-07-15 9:47 ` Jan Weitzel
2011-07-15 10:55 ` Tony Lindgren
2011-07-15 16:06 ` [RFC 0/2] join omap4panda and pcm049 Jan Weitzel
2011-07-18 8:42 ` Tony Lindgren
2011-07-19 11:45 ` [RFC 0/2 v2] " Jan Weitzel
2011-07-19 11:45 ` [RFC 1/2] omap4: board-omap4panda: prepare for join Jan Weitzel
2011-07-21 7:25 ` Tony Lindgren
2011-07-19 11:45 ` [RFC 2/2] omap4: board-omap4pcm049: add Phytec phyCORE-OMAP4 Jan Weitzel
2011-07-21 7:38 ` Tony Lindgren
2011-07-15 16:06 ` [PATCH 1/2] omap4: board-omap4panda: prepare for join Jan Weitzel
2011-07-15 16:06 ` [PATCH 2/2] omap4: board-omap4panda: join Phytec phyCORE-OMAP4 Jan Weitzel
2011-07-08 10:04 ` [PATCH 2/3] ARM: OMAP4: add pcm049 DEBUGLL Jan Weitzel
2011-07-08 10:04 ` [PATCH 3/3] ARM: OMAP4: platformcode board-omap4pcm049.c Jan Weitzel
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=20110708115521.GA5783@atomide.com \
--to=tony@atomide.com \
--cc=j.weitzel@phytec.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=sshtylyov@mvista.com \
/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).