From: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>
To: Andi Kleen <ak-l3A5Bk7waGM@public.gmane.org>
Cc: acpi-jp-l7ZBCLq5RC066kwqclu8Pg@public.gmane.org,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH] invalid resource lists and extra checking
Date: Mon, 22 Sep 2003 08:03:33 -0700 (PDT) [thread overview]
Message-ID: <20030922080137.G40076@root.org> (raw)
In-Reply-To: <20030922145315.GC13165-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org>
On Mon, 22 Sep 2003, Andi Kleen wrote:
> > --- rsaddr.c 13 Jul 2003 22:43:31 -0000 1.1.1.11
> > +++ rsaddr.c 19 Sep 2003 04:59:50 -0000
> > @@ -168,6 +168,10 @@
> > Buffer += 1;
> > ACPI_MOVE_16_TO_16 (&Temp16, Buffer);
> >
> > + /* Check for the minimum length. */
> > + if (Temp16 < 13)
> > + return_ACPI_STATUS (AE_AML_INVALID_RESOURCE_TYPE);
>
> For which acpica version is this exactly? I tried to apply it to a Linux
> tree which has nearly the latest, but it rejected on every hunk.
> The file is also repetive enough that hand applying looks a bit risky.
>
> Can you perhaps post a patch against the latest ACPICA version?
This was against 0619. Things can't have diverged THAT much since the
only public release after this was 0714 and the linux pushes have been
mostly in the linux-specific code (i.e. PIC). I have a feeling you didn't
run the patch through the LiNuXuLaTor de-caps tool and that's why it
rejected. Apply it against a stock acpica unix dist and then de-caps it.
-Nate
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
prev parent reply other threads:[~2003-09-22 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-19 15:09 [PATCH] invalid resource lists and extra checking Nate Lawson
[not found] ` <20030918221109.L16619-Y6VGUYTwhu0@public.gmane.org>
2003-09-22 14:53 ` Andi Kleen
[not found] ` <20030922145315.GC13165-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org>
2003-09-22 15:03 ` Nate Lawson [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=20030922080137.G40076@root.org \
--to=nate-y6vguytwhu0@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=acpi-jp-l7ZBCLq5RC066kwqclu8Pg@public.gmane.org \
--cc=ak-l3A5Bk7waGM@public.gmane.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