From: Paul Mundt <lethal@linux-sh.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Robert Schwebel <robert@schwebel.de>,
Sascha Hauer <s.hauer@pengutronix.de>,
Russell King <rmk+kernel@arm.linux.org.uk>,
linux-kernel@vger.kernel.org
Subject: ARM defconfig bogosity in current git
Date: Sat, 10 Nov 2007 17:06:29 +0900 [thread overview]
Message-ID: <20071110080629.GA18520@linux-sh.org> (raw)
The last ARM merge contained this gem:
commit f33bac8dd4573428b94c67149c5607be489092d1
Author: Robert Schwebel <robert@schwebel.de>
Date: Mon Nov 5 17:59:25 2007 +0100
[ARM] 4642/2: netX: default config for netx based boards
This patch updates the default config file for netx based boards.
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
diff --git a/arm/configs/netx_defconfig b/arm/configs/netx_defconfig
new file mode 100644
index 0000000..57f32f3
--- /dev/null
+++ b/arm/configs/netx_defconfig
...
Isn't there something in Documentation/ about -p1 being a good idea
precisely so this sort of silliness is avoided?
Currently this breaks tab completion on arch/, which is very much a
regression ;-)
next reply other threads:[~2007-11-10 8:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-10 8:06 Paul Mundt [this message]
2007-11-10 9:10 ` ARM defconfig bogosity in current git Russell King
2007-11-10 11:26 ` Robert Schwebel
2007-11-10 11:49 ` Adrian Bunk
2007-11-10 13:40 ` Robert Schwebel
2007-11-10 13:41 ` [PATCH] netx: remove bogus defconfig patch with wrong -p Robert Schwebel
2007-11-11 9:41 ` Russell King
2007-11-11 17:50 ` Linus Torvalds
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=20071110080629.GA18520@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=robert@schwebel.de \
--cc=s.hauer@pengutronix.de \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.