From: John Spencer <maillist-linux@barfooze.de>
To: linux-kernel@vger.kernel.org
Cc: Rob Landley <rob@landley.net>
Subject: Re: [PATCH 0/3] build linux-next without perl
Date: Wed, 27 Feb 2013 17:55:31 +0100 [thread overview]
Message-ID: <512E3A83.2050501@barfooze.de> (raw)
In-Reply-To: 1361944667.957820@landley.net
Rob Landley wrote:
> Before 2.6.25 building Linux never required perl. This patch series
removes
> the requirement from basic kernel builds (tested on i686, x86_64, arm,
mips,
> powerpc, sparc, sh4, and m68k). Now updated to 3.8-rc1.
using this patch series since 2.6.32 in sabotage linux, it is highly
useful and it's about time to get it merged.
tested against linux 3.8, works perfectly.
Acked-By: John Spencer <maillist-linux@barfooze.de>
next reply other threads:[~2013-02-27 17:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 16:55 John Spencer [this message]
2013-02-27 18:53 ` [PATCH 0/3] build linux-next without perl Sam Ravnborg
2013-02-27 19:50 ` John Spencer
-- strict thread matches above, loose matches on Subject: below --
2013-02-27 5:57 Rob Landley
2013-02-27 21:51 ` Andrew Morton
2013-02-28 4:01 ` Rob Landley
2013-02-28 4:48 ` Rob Landley
2013-02-28 6:47 ` Geert Uytterhoeven
2013-02-28 8:44 ` Michal Marek
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=512E3A83.2050501@barfooze.de \
--to=maillist-linux@barfooze.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
/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