From: Huang Ying <ying.huang@intel.com>
To: Myron Stowe <myron.stowe@redhat.com>, lenb@kernel.org
Cc: linux-acpi@vger.kernel.org, rjw@sisk.pl, bhelgaas@google.com,
trenn@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] ACPI: Re-factor and remove ./drivers/acpi/atomicio.[ch]
Date: Sat, 21 Jan 2012 11:15:58 +0800 [thread overview]
Message-ID: <1327115758.7922.30.camel@yhuang-dev> (raw)
In-Reply-To: <20120121021318.14723.45698.stgit@amt.stowe>
On Fri, 2012-01-20 at 19:13 -0700, Myron Stowe wrote:
> I recently submitted a patch series that re-factored some existing
> work that Huang Ying introduced adding support for accessing ACPI
> generic registers, backed by Memory Mapped I/O (MMIO), while within
> interrupt context:
> Original series: http://marc.info/?l=linux-acpi&m=128769263327206&w=2
> Follow on series: http://marc.info/?l=linux-kernel&m=132070825520957&w=2
>
> An underlying goal has been to re-factor ./drivers/acpi/atomicio.c into
> ./drivers/acpi/osl.c, providing equivalent functionality but in a more
> generalized manner, to allow usage in non-specific (i.e. APEI) contexts
> and remove atomicio.c.
>
> In the most recent follow on series, there ended up being additions to
> atomicio.c that coincided with the attempt to remove it and as such, the
> series final removal patch could not be taken without first pulling the
> additions into osl.c. The fact that the follow on series conversion
> patch - commit 700130b41f4 - was taken has inadvertently created
> regressions with respect to the recent atomicio.c additions due to the
> conversion patch effectively making atomicio.c obsolete.
>
> The additions were commit 04c25997c97 "ACPI, Add 64bit read/write
> support to atomicio on i386" and commit 76da3fb3575 "ACPI, Add RAM
> mapping support to ACPI atomic IO support".
>
> This patch series addresses both of these issues, bringing in the
> additional functionality into the re-factored files (apei-base.c and
> osl.c) and then again, reintroduces the patch to remove
> ./drivers/acpi/atomicio.[ch].
> ---
>
> Myron Stowe (3):
> ACPI: Remove ./drivers/acpi/atomicio.[ch]
It appears there is no one uses atomicio.[ch] now. So I think it is
safe to push this into 3.3.
> ACPI, APEI: Add RAM mapping support to ACPI
> ACPI, APEI: Add 64-bit read/write support for APEI on i386
These two patches are just fixes. So I think we should push these two
patches into 3.3.
Len, Do you agree?
Best Regards,
Huang Ying
prev parent reply other threads:[~2012-01-21 3:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 2:13 [PATCH 0/3] ACPI: Re-factor and remove ./drivers/acpi/atomicio.[ch] Myron Stowe
2012-01-21 2:13 ` [PATCH 1/3] ACPI, APEI: Add 64-bit read/write support for APEI on i386 Myron Stowe
2012-01-21 2:13 ` [PATCH 2/3] ACPI, APEI: Add RAM mapping support to ACPI Myron Stowe
2012-01-21 15:04 ` Bjorn Helgaas
2012-01-21 20:38 ` Bjorn Helgaas
2012-01-23 18:03 ` Myron Stowe
2012-01-29 0:58 ` Huang Ying
2012-01-29 20:41 ` Bjorn Helgaas
2012-01-30 0:35 ` Huang Ying
2012-02-06 1:37 ` Huang Ying
2012-01-21 2:13 ` [PATCH 3/3] ACPI: Remove ./drivers/acpi/atomicio.[ch] Myron Stowe
2012-01-21 3:15 ` Huang Ying [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=1327115758.7922.30.camel@yhuang-dev \
--to=ying.huang@intel.com \
--cc=bhelgaas@google.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=myron.stowe@redhat.com \
--cc=rjw@sisk.pl \
--cc=trenn@suse.de \
/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).