mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: rmk@arm.linux.org.uk
Cc: linux-kernel@vger.rutgers.edu
Subject: Re: PageSkip
Date: Sat, 12 Aug 2000 17:19:44 -0700	[thread overview]
Message-ID: <200008130019.RAA04614@pizda.ninka.net> (raw)
In-Reply-To: <200008121801.TAA11768@flint.arm.linux.org.uk> (message from Russell King on Sat, 12 Aug 2000 19:01:53 +0100 (BST))

   From: Russell King <rmk@arm.linux.org.uk>
   Date: 	Sat, 12 Aug 2000 19:01:53 +0100 (BST)

   I've just done a grep for PageSkip on all .c and .h files in the current
   (2.4.0-test6) kernel, and have come up with:

 ...

   Since this macro is only used in two architecture-specific places, is there
   any reason to keep it in the header files?

   On ARM, I'm planning on moving it out of pgtable.h and into mm/init.c.

It should die just about everywhere, there should be no use for it
anymore for any port.

it only existed to handle generic parts of the kernel which wished to
walk the mem_map[] array by hand, there is no such code any more
thanks to various cleanups by Kanoj and others.  Ergo PageSkip and
PG_skip can both be just eradicated along with any code referencing
it.  Unless, you are using it for some strange purpose inside your
ports, and I bet even those cases can be easily removed.

Later,
David S. Miller
davem@redhat.com

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2000-08-13  0:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-12 18:01 PageSkip Russell King
2000-08-13  0:19 ` David S. Miller [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=200008130019.RAA04614@pizda.ninka.net \
    --to=davem@redhat.com \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=rmk@arm.linux.org.uk \
    /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®