linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lin Ming <ming.m.lin@intel.com>
To: "malattia@linux.it" <malattia@linux.it>, devel@acpica.org
Cc: "Moore, Robert" <robert.moore@intel.com>,
	Len Brown <lenb@kernel.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [patch 0/5] iASL patches in Debian
Date: Mon, 05 Jul 2010 09:01:39 +0800	[thread overview]
Message-ID: <1278291699.9540.7.camel@minggr.sh.intel.com> (raw)
In-Reply-To: <20100704044332.573836359@linux.it>

On Sun, 2010-07-04 at 12:43 +0800, malattia@linux.it wrote:
> Hi Robert,
> 
> Here is a series of patches that I've been carrying in the iasl Debian
> package for some time. They are all refreshed and reworked to apply
> cleanly on top of acpica-unix-20100528.
> The series consists a couple of trivial patches to fix building on the
> FreeBSD and Hurd kernel flavours of Debian and some larger ones to enable
> compiling ASL on big endian architectures.
> It would be great if you could apply the patches to your source tree and
> ship new release with this work included.
> Let me know if you want me to run more tests or change something in the
> patches.
> 
> I tested building tests/misc/grammar.asl (plus a number or other DSDTs I
> have here) with the whole set applied and the results were identical on
> BE and LE machines as well as being identical to what a clean iasl
> produces on x86[1].
> You can see build logs for all the architectures supported here:
> https://buildd.debian.org/status/package.php?p=acpica-unix

Hi,

Thanks for the patches.

(linux-acpi@vger.kernel.org is for linux-specific acpi dicussion. Better
to post these patches to ACPICA maillist devel@acpica.org)

I read these patches but not clear what the problem they solved.
Could you add info in the log of each patch?

Thanks,
Lin Ming


  parent reply	other threads:[~2010-07-05  1:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-04  4:43 [patch 0/5] iASL patches in Debian malattia
2010-07-04  4:43 ` [patch 1/5] allow overriding only some of the CFLAGS malattia
2010-07-04  4:43 ` [patch 2/5] Small tweak to define uintptr_t and successfully build on debian/kfreebsd malattia
2010-07-04  4:43 ` [patch 3/5] Support compiling DSDT tables on big endian architectures malattia
2010-07-04  4:43 ` [patch 4/5] Add architectures that do not support unaligned access and fix aligment issues malattia
2010-07-04  4:43 ` [patch 5/5] Fix FTBFS on hurd-i386 malattia
2010-07-05  1:01 ` Lin Ming [this message]
2010-07-05 11:49   ` [patch 0/5] iASL patches in Debian malattia
2010-07-06 17:01 ` Moore, Robert
2010-07-07 19:27 ` Moore, Robert
2010-07-07 22:07   ` malattia
2010-07-07 23:41     ` Moore, Robert
2010-07-08 13:41       ` malattia
2010-07-08 22:14         ` Lin Ming
2010-07-08  0:49     ` Lin Ming
2010-07-08 13:49       ` malattia
2010-07-08 22:06         ` Lin Ming
2010-07-08 14:40           ` malattia
2010-07-14  1:42             ` Lin Ming
2010-07-15 21:29               ` malattia
2010-07-08 14:44           ` Moore, Robert

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=1278291699.9540.7.camel@minggr.sh.intel.com \
    --to=ming.m.lin@intel.com \
    --cc=devel@acpica.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=malattia@linux.it \
    --cc=robert.moore@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;
as well as URLs for NNTP newsgroup(s).