From: lachlan@sgi.com (Lachlan McIlroy)
To: sgi.bugs.xfs@engr.sgi.com, xfs@oss.sgi.com
Subject: PARTIAL TAKE 971186 - lose xfs_hex_dump in favor of print_hex_dump
Date: Mon, 8 Oct 2007 16:31:05 +1000 (EST) [thread overview]
Message-ID: <20071008063105.2E85558C38F1@chook.melbourne.sgi.com> (raw)
lose xfs_hex_dump in favor of print_hex_dump
No need for xfs to have its own hex dumping routine now that the
kernel has one.
Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
Date: Mon Oct 8 16:30:20 AEST 2007
Workarea: redback.melbourne.sgi.com:/home/lachlan/isms/2.6.x-oss
Inspected by: Eric Sandeen <sandeen@sandeen.net>
Author: lachlan
The following file(s) were checked into:
longdrop.melbourne.sgi.com:/isms/linux/2.6.x-xfs-melb
Modid: xfs-linux-melb:xfs-kern:29847a
fs/xfs/xfs_error.c - 1.59 - changed
http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfs_error.c.diff?r1=text&tr1=1.59&r2=text&tr2=1.58&f=h
fs/xfs/xfs_error.h - 1.49 - changed
http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfs_error.h.diff?r1=text&tr1=1.49&r2=text&tr2=1.48&f=h
fs/xfs/support/debug.c - 1.39 - changed
http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/support/debug.c.diff?r1=text&tr1=1.39&r2=text&tr2=1.38&f=h
- lose xfs_hex_dump in favor of print_hex_dump
reply other threads:[~2007-10-08 6:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20071008063105.2E85558C38F1@chook.melbourne.sgi.com \
--to=lachlan@sgi.com \
--cc=sgi.bugs.xfs@engr.sgi.com \
--cc=xfs@oss.sgi.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