public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: mpm@selenic.com
Cc: linux-kernel@vger.kernel.org
Subject: [RFC: 2.6 patch] drivers/char/random.c: #if 0 randomize_range
Date: Sun, 17 Apr 2005 22:15:37 +0200	[thread overview]
Message-ID: <20050417201537.GO3625@stusta.de> (raw)

This patch #if 0's the unused global function randomize_range.

Signed-off-by: Adrian Bunk <bunk@stusta.de>

---

 drivers/char/random.c  |    2 ++
 include/linux/random.h |    1 -
 2 files changed, 2 insertions(+), 1 deletion(-)

--- linux-2.6.12-rc2-mm3-full/include/linux/random.h.old	2005-04-17 18:17:17.000000000 +0200
+++ linux-2.6.12-rc2-mm3-full/include/linux/random.h	2005-04-17 18:17:23.000000000 +0200
@@ -65,7 +65,6 @@
 #endif
 
 unsigned int get_random_int(void);
-unsigned long randomize_range(unsigned long start, unsigned long end, unsigned long len);
 
 #endif /* __KERNEL___ */
 
--- linux-2.6.12-rc2-mm3-full/drivers/char/random.c.old	2005-04-17 18:17:30.000000000 +0200
+++ linux-2.6.12-rc2-mm3-full/drivers/char/random.c	2005-04-17 18:18:12.000000000 +0200
@@ -1618,6 +1618,7 @@
  * a <range> with size "len" starting at the return value is inside in the
  * area defined by [start, end], but is otherwise randomized.
  */
+#if 0
 unsigned long
 randomize_range(unsigned long start, unsigned long end, unsigned long len)
 {
@@ -1627,3 +1628,4 @@
 		return 0;
 	return PAGE_ALIGN(get_random_int() % range + start);
 }
+#endif  /*  0  */


             reply	other threads:[~2005-04-17 20:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-17 20:15 Adrian Bunk [this message]
2005-04-17 20:40 ` [RFC: 2.6 patch] drivers/char/random.c: #if 0 randomize_range Matt Mackall
2005-04-18  7:51   ` 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=20050417201537.GO3625@stusta.de \
    --to=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    /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