public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown@intel.com>
To: Jaya Kumar <jayakumar.acpi@gmail.com>
Cc: akpm@osdl.org, linux-acpi@vger.kernel.org,
	dtor_core@ameritech.net, luming.yu@intel.com
Subject: Re: [patch 02/14] ACPI: Atlas ACPI driver
Date: Fri, 18 Aug 2006 10:44:54 -0400	[thread overview]
Message-ID: <200608181044.55097.len.brown@intel.com> (raw)
In-Reply-To: <756b48450608170048n4d4941c2s349f44883628df9a@mail.gmail.com>

On Thursday 17 August 2006 03:48, Jaya Kumar wrote:
> On 8/16/06, Len Brown <len.brown@intel.com> wrote:
> > Andrew,
> > Please delete this patch from MM -- it is stale.
> > Jaya, please send Andrew the newer patch that replaces it -- the one
> > that doesn't touch drivers/acpi.
> >
> > thanks,
> > -Len
> 
> Hi Len,
> 
> I had sent that on June 26 to everyone on the CC list. Archive link is here:
> http://marc.theaimsgroup.com/?l=linux-acpi&m=115391161115058&w=2

that patch was an incremental depending on the previous patch.
Please send just the final patch vs 2.6.18-rc4  to the above, also cc: linux-kernel@vger.kernel.org

> Also, Dmitry had asked what we should do about handing ACPI errors to
> upper layers here:
> http://marc.theaimsgroup.com/?l=linux-acpi&m=115392091425952&w=2

Dmitry has a good question and we need to iron it out for the general case.
I recommend that for your driver you simply do something like this for now:

if (ACPI_ERROR(status))
	status = -EINVAL

and get your driver into the mm tree to find the next problem.

thanks,
-Len

  reply	other threads:[~2006-08-18 14:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-15  5:37 [patch 02/14] ACPI: Atlas ACPI driver akpm
2006-08-16  3:13 ` Len Brown
2006-08-17  7:48   ` Jaya Kumar
2006-08-18 14:44     ` Len Brown [this message]
2006-08-23 17:49       ` Dmitry Torokhov
2007-01-11  5:16         ` Jaya Kumar

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=200608181044.55097.len.brown@intel.com \
    --to=len.brown@intel.com \
    --cc=akpm@osdl.org \
    --cc=dtor_core@ameritech.net \
    --cc=jayakumar.acpi@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=luming.yu@intel.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