From: Marcelo Tosatti <marcelo@conectiva.com.br>
To: john stultz <johnstul@us.ibm.com>
Cc: olof@austin.ibm.com, lkml <linux-kernel@vger.kernel.org>,
"Randy.Dunlap" <rddunlap@osdl.org>
Subject: Re: /proc/ioports overrun patch
Date: Sat, 30 Aug 2003 12:02:49 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.55L.0308301140060.31588@freak.distro.conectiva> (raw)
> If so, I would prefer to have a fix which outputs the full resource
> information. For that we would need seq_file().
> I have a patch that converts /proc/interrupts to use seq_file as well,
> however it would be much cleaner if Randy's backport of the "single"
> interface went in first
>http://www.ussg.iu.edu/hypermail/linux/kernel/0308.3/0296.html
>Are you planning on taking that patch? Or should I just resend my patch
> w/o it?
I applied the seq file single interfaces now.
next reply other threads:[~2003-08-30 15:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-30 15:02 Marcelo Tosatti [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-29 13:30 /proc/ioports overrun patch Marcelo Tosatti
2003-08-29 18:59 ` john stultz
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=Pine.LNX.4.55L.0308301140060.31588@freak.distro.conectiva \
--to=marcelo@conectiva.com.br \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@austin.ibm.com \
--cc=rddunlap@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).