mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bryan Wu <bryan.wu@analog.com>
To: Paulo Marques <pmarques@grupopie.com>
Cc: Bryan Wu <bryan.wu@analog.com>,
	linux-kernel@vger.kernel.org, Robin Getz <robin.getz@analog.com>
Subject: [PATCH] [Scripts] kallsyms: Nuke all ChangeLog, this should be logged by git
Date: Thu, 31 Jan 2008 01:49:53 +0800	[thread overview]
Message-ID: <1201715393.6530.1.camel@roc-laptop> (raw)
In-Reply-To: <47A05CBA.2030903@grupopie.com>

>From 2375c7eaa43d4474fb5b403dba9b3175e683484a Mon Sep 17 00:00:00 2001
From: Bryan Wu <bryan.wu@analog.com>
Date: Thu, 31 Jan 2008 01:30:09 +0800
Subject: [PATCH] [Scripts] kallsyms: Nuke all ChangeLog, this should be logged by git

(25/Aug/2004) Paulo Marques <pmarques@grupopie.com>
Changed the compression method from stem compression
to "table lookup" compression

Signed-off-by: Bryan Wu <bryan.wu@analog.com>
---
 scripts/kallsyms.c |    6 ------
 1 files changed, 0 insertions(+), 6 deletions(-)

diff --git a/scripts/kallsyms.c b/scripts/kallsyms.c
index 5271db7..1dab50e 100644
--- a/scripts/kallsyms.c
+++ b/scripts/kallsyms.c
@@ -7,12 +7,6 @@
  *
  * Usage: nm -n vmlinux | scripts/kallsyms [--all-symbols] > symbols.S
  *
- * ChangeLog:
- *
- * (25/Aug/2004) Paulo Marques <pmarques@grupopie.com>
- *      Changed the compression method from stem compression to "table lookup"
- *      compression
- *
  *      Table compression uses all the unused char codes on the symbols and
  *  maps these to the most used substrings (tokens). For instance, it might
  *  map char code 0xF7 to represent "write_" and then in every symbol where
-- 
1.5.3.4


      parent reply	other threads:[~2008-01-30 17:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-30 10:20 [PATCH 1/1] [Kallsyms] Blackfin: Allow kernel symbols in L1 to be found Bryan Wu
2008-01-30 11:17 ` Paulo Marques
2008-01-30 17:27   ` Bryan Wu
2008-01-30 17:48   ` [PATCH 1/1 try #2] " Bryan Wu
2008-01-30 17:49   ` Bryan Wu [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=1201715393.6530.1.camel@roc-laptop \
    --to=bryan.wu@analog.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmarques@grupopie.com \
    --cc=robin.getz@analog.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

Powered by JetHome