From: Pavel Machek <pavel@ucw.cz>
To: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
Cc: len.brown@intel.com, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [patch 1/2] acpi: Remove procfs from bay
Date: Fri, 22 Dec 2006 11:43:55 +0000 [thread overview]
Message-ID: <20061222114355.GB4268@ucw.cz> (raw)
In-Reply-To: <20061216144027.9765bdd1.kristen.c.accardi@intel.com>
Hi!
> Remove the procfs related code from the bay driver.
>
> Signed-off-by: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
This changes userland interface... how many apps will it break?
Pavel
--
Thanks for all the (sleeping) penguins.
next prev parent reply other threads:[~2006-12-22 11:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061216223309.365745735@localhost.localdomain>
2006-12-16 22:40 ` [patch 1/2] acpi: Remove procfs from bay Kristen Carlson Accardi
2006-12-22 11:43 ` Pavel Machek [this message]
2006-12-22 18:03 ` Kristen Carlson Accardi
2006-12-16 22:40 ` [patch 2/2] Convert the bay driver to be a platform driver Kristen Carlson Accardi
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=20061222114355.GB4268@ucw.cz \
--to=pavel@ucw.cz \
--cc=kristen.c.accardi@intel.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--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