public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Pavel Machek <pavel@ucw.cz>, Andrew Morton <akpm@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] out out damn perl
Date: Sat, 17 Jan 2015 13:55:17 -0600	[thread overview]
Message-ID: <54BABE25.4030009@landley.net> (raw)
In-Reply-To: <20150117080136.GA7396@amd>

On 01/17/2015 02:01 AM, Pavel Machek wrote:
> 
> On Tue 2015-01-06 15:50:24, Andrew Morton wrote:
>> On Tue, 06 Jan 2015 17:41:35 -0600 Rob Landley <rob@landley.net> wrote:
>>
>>> Commit e6023367d779 added perl back to the kernel build in -rc6.
>>> Replace 39 lines of perl with 4 lines of shell script.
...
>> - The offending commit has cc:stable, so have a think about adding a
>>   cc:stable to this one as well.
> 
> Actually, I don't think this should go to stable. I like the patch,
> but it is not a bug, and certainly not serious enough one.

As long as the kernel doesn't make a habit of it, I don't care if
there's a release or two embedded developers should skip. Under ideal
conditions BSPs only tend to update about once every 18 months, and
that's the _good_ ones.

Rob

  parent reply	other threads:[~2015-01-17 19:55 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 [this message]
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
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=54BABE25.4030009@landley.net \
    --to=rob@landley.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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