All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@o2.pl>
To: Jarek Poplawski <jarkao2@o2.pl>
Cc: Adrian Bunk <bunk@kernel.org>, Jens Axboe <jens.axboe@oracle.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] make I/O schedulers non-modular
Date: Wed, 28 Nov 2007 00:02:08 +0100	[thread overview]
Message-ID: <474CA1F0.3090504@o2.pl> (raw)
In-Reply-To: <474C9714.1080308@o2.pl>

Jarek Poplawski wrote, On 11/27/2007 11:15 PM:
...

> Otherwise it's not so hard to overlook some stagnation.

Btw., after this 'forking' thing etc. it seems I might have lost the point
a little: which removed choices should justify such a fork. But, I hope,
you didn't mean your patch only, because then e.g. this stagnation threat
looks like a bit exaggerated...

Jarek P.

  parent reply	other threads:[~2007-11-27 22:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-25 16:18 [2.6 patch] make I/O schedulers non-modular Adrian Bunk
2007-11-25 16:21 ` Jens Axboe
2007-11-25 16:31   ` Adrian Bunk
2007-11-25 16:45     ` Jens Axboe
2007-11-25 16:56       ` Adrian Bunk
2007-11-25 17:22         ` Jens Axboe
2007-11-26  4:57           ` Al Boldi
2007-11-26  5:12             ` Andrew Morton
2007-11-26  5:28               ` Al Boldi
2007-11-27  7:09           ` Jarek Poplawski
2007-11-27 16:47             ` Adrian Bunk
2007-11-27 22:15               ` Jarek Poplawski
2007-11-27 22:53                 ` Adrian Bunk
2007-11-28  0:20                   ` Jarek Poplawski
2007-11-27 23:02                 ` Jarek Poplawski [this message]
2007-11-27 23:21                   ` Adrian Bunk
2007-12-30 17:52                 ` Jarek Poplawski
2007-11-25 23:27         ` Arjan van de Ven

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=474CA1F0.3090504@o2.pl \
    --to=jarkao2@o2.pl \
    --cc=bunk@kernel.org \
    --cc=jens.axboe@oracle.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.