linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: linas@austin.ibm.com (Linas Vepstas)
To: Olaf Hering <olh@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
	linuxppc-dev@ozlabs.org, Linus Torvalds <torvalds@osdl.org>,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] powerpc: add dmesg command to xmon
Date: Tue, 30 May 2006 11:58:19 -0500	[thread overview]
Message-ID: <20060530165819.GB7021@austin.ibm.com> (raw)
In-Reply-To: <20060529175834.GA31082@suse.de>

On Mon, May 29, 2006 at 07:58:34PM +0200, Olaf Hering wrote:
>  On Sun, May 28, Arnd Bergmann wrote:
> 
> > On Sunday 28 May 2006 14:07, Olaf Hering wrote:
> > > > This whole function looks fishy to me. It seems unnecessarily rude to me to
> > > > use kallsyms_lookup_name in order to get at a static variable from another
> > > > file. Can't you instead add a global function to kernel/printk.c to return
> > > > the buffer?
> > > 
> > > Its possible, but it wont end up in Linus tree.
> > 
> > Hmm, so the idea is that because Linus doesn't like kernel debuggers, we just
> > obfuscate the code for any improvements to xmon and hope he doesn't notice?
> 
> So lets just ask again for support in generic code for a dmesg command in xmon:
> 
> http://lkml.org/lkml/2004/10/28/32

I'd been planning to pester Torvalds/LKML on a regular basis until the
patch (or something else suitable) went in. Clearly, I'd failed to do
this. 

--linas

p.s. Belated apologies for failing to mention KDB; I assumed it would be 
"obvious" to those who know, and that by not mentioning KDB explicitly, 
I thought that the patch would have a better chance of acceptance (which
I expected to be low). Silly me. 

      reply	other threads:[~2006-05-30 21:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-28 10:46 [PATCH] powerpc: add dmesg command to xmon Olaf Hering
2006-05-28 12:04 ` Arnd Bergmann
2006-05-28 12:07   ` Olaf Hering
2006-05-28 16:12     ` Arnd Bergmann
2006-05-29 17:58       ` Olaf Hering
2006-05-30 16:58         ` Linas Vepstas [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=20060530165819.GB7021@austin.ibm.com \
    --to=linas@austin.ibm.com \
    --cc=akpm@osdl.org \
    --cc=arnd@arndb.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=olh@suse.de \
    --cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).