From: Alessandro Rubini <rubini@gnudd.com>
To: balbi@ti.com
Cc: gregkh@suse.de, 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 23:21:19 +0100 [thread overview]
Message-ID: <20111115222119.GA17953@mail.gnudd.com> (raw)
In-Reply-To: <20111115220437.GA26711@legolas.emea.dhcp.ti.com>
> this will be useful to dwc3 too, we currently have:
> [...]
Yes, this is similar, just factorized for everybody to use. I looked
for files that may use it (besides stuff I received internally) by
counting the %08x.
So in V2, tomorrow, I'll port your file to use the centralized code
tool, as a separate patch.
thank your for your interest
/alessandro
next prev parent reply other threads:[~2011-11-15 22:21 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 [this message]
2011-11-16 11:14 ` Felipe Balbi
2011-11-15 22:09 ` Greg KH
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=20111115222119.GA17953@mail.gnudd.com \
--to=rubini@gnudd.com \
--cc=balbi@ti.com \
--cc=giancarlo.asnaghi@st.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.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