Patchwork [v4] linux-libc-headers 2.6.24: backport arm/asm/hwcap.h from recent kernel

Enables building of OpenJDK which uses HWCAP_THUMBEE that is not present
in 2.6.24 headers and was introduced with

  commit 4baa9922430662431231ac637adedddbb0cfb2d7
  Author: Russell King <rmk@dyn-67.arm.linux.org.uk>
  Date:   Sat Aug 2 10:55:55 2008 +0100

      [ARM] move include/asm-arm to arch/arm/include/asm

Signed-off-by: Steffen Sledz <sledz@dresearch-fe.de>
Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
---
 .../arm-hwcap-add-new-entries.patch                |   26 ++++++++++++++++++++
 .../linux-libc-headers_2.6.24.bb                   |    6 +++-
 2 files changed, 30 insertions(+), 2 deletions(-)
 create mode 100644 recipes/linux-libc-headers/linux-libc-headers-2.6.24/arm-hwcap-add-new-entries.patch

Dear Steffen,


unfortunately I still have something to add. :(

Am Donnerstag, den 15.09.2011, 09:55 +0200 schrieb Steffen Sledz:

1. Please do not use `recent` but write the correct version. In this
case it would be 2.6.26 (see below).

> Enables building of OpenJDK which uses HWCAP_THUMBEE that is not present
> in 2.6.24 headers and was introduced with
> 
>   commit 4baa9922430662431231ac637adedddbb0cfb2d7
>   Author: Russell King <rmk@dyn-67.arm.linux.org.uk>
>   Date:   Sat Aug 2 10:55:55 2008 +0100
> 
>       [ARM] move include/asm-arm to arch/arm/include/asm

2. Of course that is not correct and I asked that in my last response
why a move should introduce new code lines.

Using

        git log --follow 4baa9922430662431231ac637adedddbb0cfb2d7 -- arch/arm/include/asm/hwcap.h

I found the following commit

        commit d7f864be8323e5394040e2877594645b0e7da85d
        Author: Catalin Marinas <catalin.marinas@arm.com>
        Date:   Fri Apr 18 22:43:06 2008 +0100
        
            ARMv7: Add support for the ThumbEE state saving/restoring
            
            This patch adds the detection and handling of the ThumbEE extension on
            ARMv7 CPUs.
            
            Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>

introduced in 2.6.26.

        $ git describe --contains
        d7f864be8323e5394040e2877594645b0e7da85d
        v2.6.26-rc1~1090^2~27

Please note that this commit contains not only the addition of
HWCAP_THUMBEE to the header but a lot more. So is OpenJDK doing
something incorrectly then? Does it detect the wrong architecture?

> Signed-off-by: Steffen Sledz <sledz@dresearch-fe.de>
> Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
> ---
>  .../arm-hwcap-add-new-entries.patch                |   26 ++++++++++++++++++++
>  .../linux-libc-headers_2.6.24.bb                   |    6 +++-
>  2 files changed, 30 insertions(+), 2 deletions(-)
>  create mode 100644 recipes/linux-libc-headers/linux-libc-headers-2.6.24/arm-hwcap-add-new-entries.patch

[…]

Please update the relevant parts and send it to the list again. You can
commit it the next day if nobody else objects.


Thanks,

Paul


PS: It is hard for reviewers to see what changed in your patch
iterations. For example between v3 and v4. Please add a short note below
the commit message and separate that with an additional `---`. `git am`
will not pick that comment up then.

On 15.09.2011 11:05, Paul Menzel wrote:
> PS: It is hard for reviewers to see what changed in your patch iterations. For example between v3 and v4. Please add a short note below the commit message and separate that with an additional `---`. `git am` will not pick that comment up then.

Is it possible to add such a comment while running "git format-patch" or "git send-email"?

Or is it necessary to mix this into the commit comment itself?

Am Donnerstag, den 15.09.2011, 13:54 +0200 schrieb Steffen Sledz:
> On 15.09.2011 11:05, Paul Menzel wrote:
> > PS: It is hard for reviewers to see what changed in your patch iterations. For example between v3 and v4. Please add a short note below the commit message and separate that with an additional `---`. `git am` will not pick that comment up then.
> 
> Is it possible to add such a comment while running "git format-patch" or "git send-email"?

I do not know of a way and I did not find anything in the manual. I
guess you have to edit the mbox file created by `git format-patch` and
then send it.

Other people also use the cover letter feature. But in all cases it
seems to be one step more.

> Or is it necessary to mix this into the commit comment itself?

No, since `git push` is not leaving the comment out.

Thank you again for addressing my comments.


Thanks,

Paul

On 15.09.2011 16:56, Paul Menzel wrote:
> Am Donnerstag, den 15.09.2011, 13:54 +0200 schrieb Steffen Sledz:
>> On 15.09.2011 11:05, Paul Menzel wrote:
>>> PS: It is hard for reviewers to see what changed in your patch iterations. For example between v3 and v4. Please add a short note below the commit message and separate that with an additional `---`. `git am` will not pick that comment up then.
>>
>> Is it possible to add such a comment while running "git format-patch" or "git send-email"?
> 
> I do not know of a way and I did not find anything in the manual. I
> guess you have to edit the mbox file created by `git format-patch` and
> then send it.

After reading the manual i found the --annotate option for "git send-email" which helped me here.

Steffen