From: pdeschrijver@nvidia.com (Peter De Schrijver)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 2/3] arm/tegra: add support for ventana pinmuxing
Date: Thu, 29 Sep 2011 18:27:52 +0300 [thread overview]
Message-ID: <20110929152752.GO21166@tbergstrom-lnx.Nvidia.com> (raw)
In-Reply-To: <20110929092951.GE23944@n2100.arm.linux.org.uk>
On Thu, Sep 29, 2011 at 11:29:51AM +0200, Russell King - ARM Linux wrote:
> On Thu, Sep 29, 2011 at 01:29:35AM +0300, Peter De Schrijver wrote:
> > diff --git a/arch/arm/mach-tegra/Makefile b/arch/arm/mach-tegra/Makefile
> > index f11b910..91a07e1 100644
> > --- a/arch/arm/mach-tegra/Makefile
> > +++ b/arch/arm/mach-tegra/Makefile
> > @@ -31,6 +31,7 @@ obj-${CONFIG_MACH_SEABOARD} += board-seaboard-pinmux.o
> >
> > obj-${CONFIG_MACH_TEGRA_DT} += board-dt.o
> > obj-${CONFIG_MACH_TEGRA_DT} += board-harmony-pinmux.o
> > +obj-${CONFIG_MACH_TEGRA_DT} += board-seaboard-pinmux.o
>
> Since when did Tegra start using braces instead of parens in its Makefile?
> I note some of Tegra's makefile is using braces and some of it parens.
> What's the reason for this alternative style to the rest of kbuild?
I have no idea. I just followed the style used for the other CONFIG_MACH_TEGRA_DT entries. Colin or Olof, any idea?
Thanks,
Peter.
next prev parent reply other threads:[~2011-09-29 15:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 22:29 [PATCH v5 0/3] Add support for tegra2 based ventana board Peter De Schrijver
2011-09-28 22:29 ` [PATCH v5 1/3] arm/tegra: prepare Seaboard pinmux code for derived boards Peter De Schrijver
2011-09-28 22:29 ` [PATCH v5 2/3] arm/tegra: add support for ventana pinmuxing Peter De Schrijver
2011-09-29 9:29 ` Russell King - ARM Linux
2011-09-29 15:27 ` Peter De Schrijver [this message]
2011-09-29 15:47 ` Olof Johansson
2011-09-28 22:29 ` [PATCH v5 3/3] arm/tegra: device tree support for ventana board Peter De Schrijver
2011-09-29 17:04 ` Stephen Warren
2011-09-29 18:55 ` Peter De Schrijver
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=20110929152752.GO21166@tbergstrom-lnx.Nvidia.com \
--to=pdeschrijver@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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