From: Rob Landley <rob@landley.net>
To: Richard Weinberger <richard.weinberger@gmail.com>,
Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] out out damn perl
Date: Mon, 12 Jan 2015 10:14:26 -0600 [thread overview]
Message-ID: <54B3F2E2.5030807@landley.net> (raw)
In-Reply-To: <CAFLxGvyyujXptcD3d6AF+Fri+UC_G1n8ED+uJZZ0TuD22kszow@mail.gmail.com>
On 01/12/2015 09:27 AM, Richard Weinberger wrote:
> On Mon, Jan 12, 2015 at 4:16 PM, Lennart Sorensen
> <lsorense@csclub.uwaterloo.ca> wrote:
>> On Tue, Jan 06, 2015 at 05:41:35PM -0600, Rob Landley wrote:
>>> From: Rob Landley <rob@landley.net>
>>>
>>> Commit e6023367d779 added perl back to the kernel build in -rc6.
>>> Replace 39 lines of perl with 4 lines of shell script.
>>
>> Maybe checkpatch should be updated to look for perl. :)
>
> Yeah, then checkpatch.pl warn on itself. ;-)
There's a difference between a development tool and a build tool. We
have "make xconfig" and "make gconfig" but don't require qt and gtk to
both be in your cross compile environment in order to build the kernel.
Rob
next prev parent reply other threads:[~2015-01-12 16:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 23:41 [PATCH] out out damn perl Rob Landley
2015-01-06 23:50 ` Andrew Morton
2015-01-12 16:54 ` [PATCHv2] remove recently added perl build requirement Rob Landley
2015-01-13 1:01 ` Kees Cook
2015-01-17 8:01 ` [PATCH] out out damn perl Pavel Machek
2015-01-17 11:56 ` Geert Uytterhoeven
2015-01-17 19:55 ` Rob Landley
2015-01-12 15:16 ` Lennart Sorensen
2015-01-12 15:25 ` Borislav Petkov
2015-01-12 15:27 ` Richard Weinberger
2015-01-12 16:14 ` Rob Landley [this message]
2015-01-12 16:17 ` Richard Weinberger
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=54B3F2E2.5030807@landley.net \
--to=rob@landley.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=richard.weinberger@gmail.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