From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Artem Bityutskiy <dedekind@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Woodhouse <dwmw2@infradead.org>,
Frank Haverkamp <haver@vnet.ibm.com>
Subject: Re: [GIT-PULL] please pull UBI tree
Date: Fri, 27 Apr 2007 17:42:11 -0500 [thread overview]
Message-ID: <20070427224211.GG23995@crusty.rchland.ibm.com> (raw)
In-Reply-To: <20070427142254.3aa89a16.randy.dunlap@oracle.com>
On Fri, Apr 27, 2007 at 02:22:54PM -0700, Randy Dunlap wrote:
> On Fri, 27 Apr 2007 13:52:24 -0700 Andrew Morton wrote:
> > The patchset used to contain lots of debugging support which wildly
> > duplicated thigs which we already did and was generally overdone. That
> > appears to all have been cleaned up now, so thanks for doing that.
> >
> > The one remaining nit I'd have with the debug code is that it adds a
> > private hexdump() facility. By my count, that is the kernel's eighth
> > hexdump implementation. There may be even more which don't have "hexdump"
> > in their name.
> >
> > lib/hexdump.c is rather overdue.
>
> I have a version of that from James Ketrenos that I have been working
> on... Can post in a few days.
Excellent. We'll take a look at it as soon as you do.
josh
prev parent reply other threads:[~2007-04-27 22:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 12:45 [GIT-PULL] please pull UBI tree Artem Bityutskiy
2007-04-27 16:00 ` Linus Torvalds
2007-04-27 17:30 ` Artem Bityutskiy
2007-04-27 17:57 ` Thomas Gleixner
2007-04-27 17:59 ` Linus Torvalds
2007-04-27 20:52 ` Andrew Morton
2007-04-27 21:22 ` Randy Dunlap
2007-04-27 22:42 ` Josh Boyer [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=20070427224211.GG23995@crusty.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dedekind@infradead.org \
--cc=dwmw2@infradead.org \
--cc=haver@vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=torvalds@linux-foundation.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