From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: fix syntax error in main Kconfig file
Date: Tue, 10 Aug 2010 23:14:33 +0100 [thread overview]
Message-ID: <20100810221433.GE7702@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1281471252-31424-1-git-send-email-u.kleine-koenig@pengutronix.de>
On Tue, Aug 10, 2010 at 10:14:12PM +0200, Uwe Kleine-K?nig wrote:
> - select HAVE_ARM_TWD if (ARCH_REALVIEW || ARCH_VEXPRESS || ARCH_OMAP4 || \\
> + select HAVE_ARM_TWD if ARCH_REALVIEW || ARCH_VEXPRESS || ARCH_OMAP4 || \\
This is still crap. '\\' on the end of the line...
And no surprises that I'm getting conflicts when merging my master and
devel branches here. Don't bother submitting a new patch, I'll fix it
in the conflict resolution.
prev parent reply other threads:[~2010-08-10 22:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 19:42 [PATCH]: Fix arm kconfig xsecute at googlemail.com
2010-08-10 19:56 ` Russell King - ARM Linux
2010-08-10 20:07 ` Uwe Kleine-König
2010-08-10 20:14 ` [PATCH] ARM: fix syntax error in main Kconfig file Uwe Kleine-König
2010-08-10 22:14 ` Russell King - ARM Linux [this message]
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=20100810221433.GE7702@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).