public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Doug Thompson <norsk5@yahoo.com>,
	akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: PATCH: EDAC, core EDAC support code
Date: Mon, 17 Oct 2005 18:59:17 +0100	[thread overview]
Message-ID: <1129571958.2424.0.camel@localhost> (raw)
In-Reply-To: <1129531119.2907.1.camel@laptopd505.fenrus.org>

On Llu, 2005-10-17 at 08:38 +0200, Arjan van de Ven wrote:
> that doesn't work that way.. with the /proc stuff you add an api/abi,
> which you can't get rid of afterwards, so it's important to get that
> right from the start..... 

The proc interface for this dates back to Linux 2.0 or so. Existing
tools will still expect it for some time.


      reply	other threads:[~2005-10-17 18:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-15 19:06 PATCH: EDAC, core EDAC support code Alan Cox
2005-10-16  3:05 ` Nish Aravamudan
2005-10-16  8:25 ` Arjan van de Ven
2005-10-17  1:48   ` Doug Thompson
2005-10-17  6:38     ` Arjan van de Ven
2005-10-17 17:59       ` Alan Cox [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=1129571958.2424.0.camel@localhost \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=norsk5@yahoo.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