public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: pci_pool reap?
Date: Tue, 12 Feb 2002 15:59:22 +0000	[thread overview]
Message-ID: <20020212155922.F31425@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20020211.184412.35663889.davem@redhat.com> <1013528224.2240.245.camel@bitch> <20020212154816.E31425@flint.arm.linux.org.uk> <20020212.075051.14974554.davem@redhat.com>
In-Reply-To: <20020212.075051.14974554.davem@redhat.com>; from davem@redhat.com on Tue, Feb 12, 2002 at 07:50:51AM -0800

On Tue, Feb 12, 2002 at 07:50:51AM -0800, David S. Miller wrote:
> The conclusion we came to is that there is no reason you can't do the
> remapping from interrupts on ARM and propagate the GFP_ATOMIC
> properly as well.  Right?
> 
> Or is this another "I'm not going to make the change until it
> is required of me" situation?  If so I'll just make it so :-)

Well, seeing as I'm currently on 2.5.2 still, waiting for various changes
to stabilise, its still not really high on my priority list.  Things
that are high on it is to move forward RSN and put in place all the
changes for ARM that are needed between 2.5.3-pre1 and 2.5.4.  There's
several bits that need to be looked at, and some of the changes that
have happened in 2.5.2-rmk clash with some of the changes in these
patches, c'est la vie.

Also high is to do something about the growing mountain of patches in
my patch system that need to be processed.

So, I hope you can see that any changes you put into current Linus
kernels won't change the situation for a while because I'm too overloaded
with other stuff and stuck back at 2.5.2 currently.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2002-02-12 15:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1013388420.27877.linux-kernel2news@redhat.com>
2002-02-11  2:49 ` pci_pool reap? Pete Zaitcev
2002-02-11  3:12   ` Alan Cox
2002-02-10 20:20     ` Gérard Roudier
2002-02-12  2:44       ` David S. Miller
2002-02-11 20:34         ` Gérard Roudier
2002-02-12 15:36         ` Daniel Stodden
2002-02-11 21:10           ` Gérard Roudier
2002-02-12 21:14             ` Daniel Stodden
2002-02-12 15:48           ` Russell King
2002-02-12 15:50             ` David S. Miller
2002-02-12 15:59               ` Russell King [this message]
2002-02-12 17:27             ` Daniel Stodden
2002-02-12 15:49           ` David S. Miller
2002-02-11  0:44 Daniel Stodden

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=20020212155922.F31425@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=davem@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox