From: Paul Jackson <pj@sgi.com>
To: Mike Travis <travis@sgi.com>
Cc: mingo@elte.hu, tglx@linutronix.de, hpa@zytor.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] x86: add cpuset_scnprintf function
Date: Wed, 2 Apr 2008 10:28:31 -0500 [thread overview]
Message-ID: <20080402102831.4e29b299.pj@sgi.com> (raw)
In-Reply-To: <47F399EE.4080704@sgi.com>
Mike wrote:
> But where is the API spec for /proc outputs? I'd like to see how others
> have managed to change it in the past, and what are the rules for doing so.
The primary spec is the actual behaviour, unless that's clearly
busted.
Changes are usually done by adding files, lines and fields, not
changing the format of existing fields.
Perhaps you should give me a call ... I sense that the lack of
synchrony in our viewpoints is discomforting in this forum.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.940.382.4214
prev parent reply other threads:[~2008-04-02 15:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 22:54 [PATCH 0/3] x86: add cpuset_scnprintf function Mike Travis
2008-04-01 22:54 ` [PATCH 1/3] " Mike Travis
2008-04-01 22:54 ` [PATCH 2/3] x86: modify show_shared_cpu_map in intel_cacheinfo Mike Travis
2008-04-01 22:54 ` [PATCH 3/3] cpumask: use new cpuset_scnprintf function Mike Travis
2008-04-02 6:20 ` [PATCH 0/3] x86: add " Paul Jackson
2008-04-02 7:47 ` Mike Travis
2008-04-02 10:39 ` Paul Jackson
2008-04-02 14:36 ` Mike Travis
2008-04-02 15:28 ` Paul Jackson [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=20080402102831.4e29b299.pj@sgi.com \
--to=pj@sgi.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=travis@sgi.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