mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Oliver Pinter" <oliver.pntr@gmail.com>
To: "Willy Tarreau" <w@1wt.eu>
Cc: "Hugh Dickins" <hugh@veritas.com>,
	stable@kernel.org, "Andrew Morton" <akpm@linux-foundation.org>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC, 2.6.26.2-rc1] exec: remove some includes
Date: Sat, 2 Aug 2008 22:03:25 +0200	[thread overview]
Message-ID: <6101e8c40808021303h10ecb2d7v70604740413c5df0@mail.gmail.com> (raw)
In-Reply-To: <20080802195622.GG615@1wt.eu>

I understood, I do not send patches with a character like this in the
future then, but I send it because of this in RFC

On 8/2/08, Willy Tarreau <w@1wt.eu> wrote:
> On Sat, Aug 02, 2008 at 09:45:17PM +0200, Oliver Pinter wrote:
>> >From ba92a43dbaee339cf5915ef766d3d3ffbaaf103c Mon Sep 17 00:00:00 2001
>> From: Hugh Dickins <hugh@veritas.com>
>> Date: Fri, 25 Jul 2008 01:45:43 -0700
>> Subject: [PATCH] exec: remove some includes
>>
>> [ Upstream commit ba92a43dbaee339cf5915ef766d3d3ffbaaf103c ]
>>
>> fs/exec.c used to need mman.h pagemap.h swap.h and rmap.h when it did
>> mm-ish stuff in install_arg_page(); but no need for them after 2.6.22.
>                                           ^^^^^^^
> Oliver, this patch apparently fixes nothing, and playing with includes
> always causes a risk of regression. Please ensure that only fixes for
> real problems are submitted to stable and check stable_kernel_rules.txt
> when in doubt.
>
> Willy
>
>


-- 
Thanks,
Oliver

      reply	other threads:[~2008-08-02 20:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-02 19:45 Oliver Pinter
2008-08-02 19:39 ` Linus Torvalds
2008-08-02 19:53   ` Hugh Dickins
2008-08-02 19:56 ` Willy Tarreau
2008-08-02 20:03   ` Oliver Pinter [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=6101e8c40808021303h10ecb2d7v70604740413c5df0@mail.gmail.com \
    --to=oliver.pntr@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=w@1wt.eu \
    /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

all inboxes | Powered by JetHome®