mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: -mm merge plans
Date: Fri, 24 Mar 2006 17:50:29 -0700	[thread overview]
Message-ID: <m1k6ajfiui.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20060324155332.4639a9c2.akpm@osdl.org> (Andrew Morton's message of "Fri, 24 Mar 2006 15:53:32 -0800")

Andrew Morton <akpm@osdl.org> writes:

> ebiederm@xmission.com (Eric W. Biederman) wrote:
>>
>> Andrew Morton <akpm@osdl.org> writes:
>> 
>> >   This is Oleg's romp through the core kernel.  There's a ton of material
>> >   here.  I'll probably send it all to Linus and ask him to review it.  (aka
>> >   blame-shifting).
>> 
>> A couple of those are mine... :)
>> 
>> >   Eric's romp through /proc.  Scary, not sure yet.
>> 
>> And a couple of these were Oleg's :)
>
> You're just trying to trick me into thinking that you're different guys.

>> Anything that can be done to make these less scary?
>
> Nothing clever that I can think of, no.  It's just a whole lot of code in
> areas which are tricky and in which few people work and in which reviewing
> resources are slight.

Ok.  Thanks.  At least I now know why it is scary.

> We'll have a couple of months to shake things out.  Any lingering problems
> will be small.  As long as the small-lingering-problems aren't security
> holes then OK, that's liveable with.

Eric

  reply	other threads:[~2006-03-25  0:51 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-23  4:53 Andrew Morton
2006-03-23  7:04 ` swap prefetching " Con Kolivas
2006-03-23  7:56   ` [ck] " Grzegorz Kulewski
2006-03-23  8:01   ` jos poortvliet
2006-03-23  8:22     ` Nick Piggin
2006-03-23  9:09       ` Con Kolivas
2006-03-23  9:24         ` Con Kolivas
2006-03-23 13:23       ` Martin J. Bligh
2006-03-23  8:33     ` Thomas Kuther
2006-03-23 11:19   ` Jesper Juhl
2006-03-23 11:24   ` [ck] " André Goddard Rosa
2006-03-23 11:57   ` Spike
2006-03-23 12:03     ` Spike
2006-03-23 12:16     ` Spike
2006-03-23 11:58   ` Lenar Lõhmus
2006-03-23 13:58   ` Francesco Biscani
2006-03-23 15:37     ` James Rayner
2006-03-23 15:34   ` [ck] " Radoslaw Szkodzinski
2006-03-23 18:35   ` Mattia Dongili
2006-03-23 18:40   ` Rafael J. Wysocki
2006-03-25 14:37   ` Jan Engelhardt
2006-03-25 15:24     ` Nick Piggin
2006-03-25 23:44       ` Con Kolivas
2006-03-26  5:54         ` Mike Galbraith
2006-03-26  8:08           ` Con Kolivas
2006-03-26  7:42             ` Mike Galbraith
2006-03-26  9:34               ` Con Kolivas
2006-03-27 15:37                 ` [ck] " André Goddard Rosa
2006-03-27 22:19                   ` Con Kolivas
2006-03-26  9:20         ` Jan Engelhardt
2006-03-28  6:16   ` [ck] " Chase Venters
2006-03-23  7:59 ` -mm " Ryan M.
2006-03-23  8:09   ` [ck] " Jens Axboe
2006-03-23  9:07     ` Con Kolivas
2006-03-23 12:12       ` [ck] " Jens Axboe
2006-03-23 10:39 ` Takashi Iwai
2006-03-23 12:33 ` Christoph Hellwig
2006-03-23 12:49 ` [PATCH] remove pps support Roman Zippel
2006-03-23 13:43 ` -mm merge plans Michal Piotrowski
2006-03-24 23:33 ` Eric W. Biederman
2006-03-24 23:53   ` Andrew Morton
2006-03-25  0:50     ` Eric W. Biederman [this message]
2006-03-25  1:53 ` Arthur Othieno

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=m1k6ajfiui.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome