From: Greg KH <gregkh@suse.de>
To: Alessandro Rubini <rubini@gnudd.com>
Cc: linux-kernel@vger.kernel.org, giancarlo.asnaghi@st.com
Subject: Re: [RFC PATCH] debugfs: add tools to printk 32-bit registers
Date: Tue, 15 Nov 2011 14:09:13 -0800 [thread overview]
Message-ID: <20111115220913.GA17970@suse.de> (raw)
In-Reply-To: <20111115213734.GA5094@mail.gnudd.com>
On Tue, Nov 15, 2011 at 10:37:34PM +0100, Alessandro Rubini wrote:
> Hi Greg. Thanks for looking.
>
> >> +/*
> >> + * The regset32 stuff is used to print 32-bit registers using the
> >> + * seq_file utilities. We offer printing a register set in an already-opened
> >> + * sequential file or create a debugfs file that only prints a regset32.
> >> + */
> >
> > Can this be part of the kerneldoc below somehow so that people are more
> > aware of it?
>
> Ok. There's also a file by Jon in Documentation that needs updating, as it
> has all the other debugfs file types.
Ah, yes, that would be good.
> > +int debugfs_print_regs32(struct seq_file *s, struct debugfs_reg32 *regs,
> >> + int nregs, void __iomem *base, char *prefix)
>
> > This function also needs to be part of debugfs.h in the "debugfs is not
> > enabled" section of the file, right?
>
> Not really. The other one makes a regiters-only file, and it's good
> to register it withouth ifdef.
>
> This one is used to embed a register block in a file with more
> stuff, so it shouldn't be used if debugfs is not selected (btw,
> I compiled my internal stuff with and without CONFIG_DEBUG_FS
> before rebasing to next).
That makes sense, thanks.
> So, I'll post a V2 shortly, unless you refuse it in reply to this.
Nope, a v2 would be great, thanks.
greg k-h
next prev parent reply other threads:[~2011-11-15 22:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 13:02 [RFC PATCH] debugfs: add tools to printk 32-bit registers Alessandro Rubini
2011-11-15 21:20 ` Greg KH
2011-11-15 21:37 ` Alessandro Rubini
2011-11-15 22:04 ` Felipe Balbi
2011-11-15 22:21 ` Alessandro Rubini
2011-11-16 11:14 ` Felipe Balbi
2011-11-15 22:09 ` Greg KH [this message]
2011-11-16 11:31 ` Mark Brown
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=20111115220913.GA17970@suse.de \
--to=gregkh@suse.de \
--cc=giancarlo.asnaghi@st.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rubini@gnudd.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