Hi List,
It seems I forgot to send a summary of the new branch layout on :- https://git.linaro.org/arm/acpi/acpi.git
1) acpi-mainline-core is a copy of the latest patch series sent by Hanjun to the linux-acpi list. 2) acpi-core is work on top of this patch series that has not yet been sent to upstream. 3) acpi-drivers is work on top of acpi-core and contains the drivers to boot the FVP Base model. It is likely these shall never be presented for upstream.
Graeme
On Monday 24 February 2014 11:33:59 Graeme Gregory wrote:
It seems I forgot to send a summary of the new branch layout on :- https://git.linaro.org/arm/acpi/acpi.git
- acpi-mainline-core is a copy of the latest patch series sent by Hanjun
to the linux-acpi list. 2) acpi-core is work on top of this patch series that has not yet been sent to upstream. 3) acpi-drivers is work on top of acpi-core and contains the drivers to boot the FVP Base model. It is likely these shall never be presented for upstream.
Is it intentional that each branch is just based on the previous one? Usually the intention of separating branches is to have them independent of one another.
Arnd
On Mon, Feb 24, 2014 at 12:44:43PM +0100, Arnd Bergmann wrote:
On Monday 24 February 2014 11:33:59 Graeme Gregory wrote:
It seems I forgot to send a summary of the new branch layout on :- https://git.linaro.org/arm/acpi/acpi.git
- acpi-mainline-core is a copy of the latest patch series sent by Hanjun
to the linux-acpi list. 2) acpi-core is work on top of this patch series that has not yet been sent to upstream. 3) acpi-drivers is work on top of acpi-core and contains the drivers to boot the FVP Base model. It is likely these shall never be presented for upstream.
Is it intentional that each branch is just based on the previous one? Usually the intention of separating branches is to have them independent of one another.
Yes becuase I've had requests for just what happens in acpi-core without the drivers stuff.
Graeme
-
Arnd Bergmann -
Graeme Gregory