[Arm-dev] Next set of APM X-Gene patches

Tue Jan 5 16:05:08 UTC 2016

I hit a snag with the installer segfaulting on specific hardware. I've
since resolved that and have pushed an iso for Johnny to test as well.
If that works, I'll be syncing the trees and pushing this week.

Your patches will be rolled into an update kernel that will also be
available at the same time. This way the install media matches what
people expect, and the updates are available to enable the additional
features.

On 01/04/2016 07:57 PM, Phong Vo wrote:
> Happy New Year, Jim.
> 
> I am following up on this submission whether it has been done.
> 
> Also, when do we have a full 4.2 release with installer and rootfs?
> 
> Thanks,
> 
> -Phong
> 
> -----Original Message-----
> From: arm-dev-bounces at centos.org [mailto:arm-dev-bounces at centos.org] On
> Behalf Of Jim Perrin
> Sent: Wednesday, December 09, 2015 9:09 PM
> To: arm-dev at centos.org
> Subject: Re: [Arm-dev] Next set of APM X-Gene patches
> 
> Got it, thanks.
> 
> On 12/09/2015 01:01 AM, Phong Vo wrote:
>> Hi Jim,
>>
>> Please find the attached APM patches for 4.2 based kernel.
>>
>> Thanks,
>>
>> -Phong
>>
>> -----Original Message-----
>> From: arm-dev-bounces at centos.org [mailto:arm-dev-bounces at centos.org] On
>> Behalf Of Jim Perrin
>> Sent: Thursday, December 03, 2015 3:55 AM
>> To: arm-dev at centos.org
>> Subject: Re: [Arm-dev] Next set of APM X-Gene patches
>>
>> I've just pushed pushed the update to the sig-altarch7-aarch64 branch.
>> You can find the new 4.2 based kernel at
>> https://git.centos.org/summary/sig-altarch!kernel.git
>>
>> If you could supply any needed patches for that kernel I'll run through
>> the build.
>>
>>
>>
>> On 12/02/2015 08:00 AM, Phong Vo wrote:
>>> Hi Jim,
>>>
>>> We need to enable newly added configuration, and the only way I could
>>> think of is to do it as part of kernel-aarch64.spec utilizing the
>>> existing configuration merge mechanism, and without impacting the
>>> config-xxx files received from Redhat.
>>>
>>> Yes, 4.2 patches are ready. I'll submit as soon as you are ready.
>>> However, we still need to resolve the config issue then.
>>>
>>> -Phong
>>>
>>> On Wed, Dec 2, 2015 at 8:30 PM, Jim Perrin <jperrin at centos.org> wrote:
>>>> I've been reasonably head-down on getting the new sources built.
>>>>
>>>> I guess my concern here is the need to merge your config changes in
>> each
>>>> iteration. Is there a particular reason for doing it that way? Are you
>>>> trying to ensure ordering here?
>>>>
>>>> Also, we'll have the updated builds ready to go in the next few days.
> I
>>>> can run with this for the 3.19 update for now, however we'd need the
>> 4.2
>>>> patches reasonably soon. Would that be a problem?
>>>>
>>>> On 12/02/2015 03:44 AM, Phong Vo wrote:
>>>>> Hi Jim,
>>>>>
>>>>> Do you have any feedback?
>>>>>
>>>>> -Phong
>>>>>
>>>>> On Tue, Nov 24, 2015 at 6:04 PM, Phong Vo <pvo at apm.com> wrote:
>>>>>> Hi Jim,
>>>>>>
>>>>>> I am resending the config patch. The change is to use merge.pl to
>>>>>> merge config-centos-sig into the final config in
> SPECS/kernel-aarch64
>>>>>> instead of modifying Makefile.config.
>>>>>>
>>>>>> The patch is against branch 3.19 of
>> git://git.centos.org/sig-altarch/kernel.git
>>>>>>
>>>>>> Let me know what you think.
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> -Phong
>>>>>>
>>>>>> On Mon, Nov 23, 2015 at 11:09 PM, Jim Perrin <jperrin at centos.org>
>> wrote:
>>>>>>>
>>>>>>>
>>>>>>> On 11/23/2015 09:42 AM, Phong Vo wrote:
>>>>>>>> Hi Jim,
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> The config patch works fine for me.  It would be creating a
>>>>>>>> SOURCES/config-centos-sig and also modifying
>> SOURCES/Makefile.config.
>>>>>>>> Actually, the patch is against the 3.19 version of c7-aarch64, not
>> the
>>>>>>>> sig-altarch/kernel 3.19 branch version; but I believe both should
>> be
>>>>>>>> the same.
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Right. It's this modification of the Makefile.config I'm trying to
>>>>>>> avoid. The way the configs are combined in the spec file mean that
>> we
>>>>>>> don't need to modify it. It's a semantic difference in how the
>> packaging
>>>>>>> is done, where I'm trying to reduce or eliminate the need to
>>>>>>> modify/touch files provided by rh or in the kernel tarball.
>>>>>>>
>>>>>>> --
>>>>>>> Jim Perrin
>>>>>>> The CentOS Project | http://www.centos.org
>>>>>>> twitter: @BitIntegrity | GPG Key: FA09AD77
>>>>>>> _______________________________________________
>>>>>>> Arm-dev mailing list
>>>>>>> Arm-dev at centos.org
>>>>>>> https://lists.centos.org/mailman/listinfo/arm-dev
>>>>> _______________________________________________
>>>>> Arm-dev mailing list
>>>>> Arm-dev at centos.org
>>>>> https://lists.centos.org/mailman/listinfo/arm-dev
>>>>>
>>>>
>>>> --
>>>> Jim Perrin
>>>> The CentOS Project | http://www.centos.org
>>>> twitter: @BitIntegrity | GPG Key: FA09AD77
>>>> _______________________________________________
>>>> Arm-dev mailing list
>>>> Arm-dev at centos.org
>>>> https://lists.centos.org/mailman/listinfo/arm-dev
>>> _______________________________________________
>>> Arm-dev mailing list
>>> Arm-dev at centos.org
>>> https://lists.centos.org/mailman/listinfo/arm-dev
>>>
>>
>>
>>
>> _______________________________________________
>> Arm-dev mailing list
>> Arm-dev at centos.org
>> https://lists.centos.org/mailman/listinfo/arm-dev
>>
> 

-- 
Jim Perrin
The CentOS Project | http://www.centos.org
twitter: @BitIntegrity | GPG Key: FA09AD77