> On 6 Dec 2019, at 14:21, Andrew Cooper wrote:
>
> On 03/12/2019 09:17, George Dunlap wrote:
>>
>>> On Dec 2, 2019, at 5:01 PM, Konrad Rzeszutek Wilk
>>> wrote:
>>>
>>> On Mon, Dec 02, 2019 at 03:55:04PM +, Andrew Cooper wrote:
On 02/12/2019 15:53, Konrad Rzeszutek Wilk wrote:
>>>
On 03/12/2019 09:17, George Dunlap wrote:
>
>> On Dec 2, 2019, at 5:01 PM, Konrad Rzeszutek Wilk
>> wrote:
>>
>> On Mon, Dec 02, 2019 at 03:55:04PM +, Andrew Cooper wrote:
>>> On 02/12/2019 15:53, Konrad Rzeszutek Wilk wrote:
>> I plan to release ack the patch in case the missing maintain
> On Dec 2, 2019, at 5:01 PM, Konrad Rzeszutek Wilk
> wrote:
>
> On Mon, Dec 02, 2019 at 03:55:04PM +, Andrew Cooper wrote:
>> On 02/12/2019 15:53, Konrad Rzeszutek Wilk wrote:
> I plan to release ack the patch in case the missing maintainer's acks
> are not coming in too late.
>>>
On Mon, Dec 02, 2019 at 03:55:04PM +, Andrew Cooper wrote:
> On 02/12/2019 15:53, Konrad Rzeszutek Wilk wrote:
> >>> I plan to release ack the patch in case the missing maintainer's acks
> >>> are not coming in too late.
> >> I think Andy's objection was that there has been zero testing of
> >>
On 02/12/2019 15:53, Konrad Rzeszutek Wilk wrote:
>>> I plan to release ack the patch in case the missing maintainer's acks
>>> are not coming in too late.
>> I think Andy's objection was that there has been zero testing of
>> livepatching on gcc. Maybe we can find someone to do a smoke-test.
> As
> > I plan to release ack the patch in case the missing maintainer's acks
> > are not coming in too late.
>
> I think Andy's objection was that there has been zero testing of
> livepatching on gcc. Maybe we can find someone to do a smoke-test.
As in integrate livepatch-build tools in osstest smo
On 11/27/19 4:35 PM, Jürgen Groß wrote:
> On 27.11.19 17:25, Jan Beulich wrote:
>> On 27.11.2019 17:21, George Dunlap wrote:
>>> On 11/27/19 4:14 PM, Jan Beulich wrote:
On 27.11.2019 17:01, Roger Pau Monne wrote:
> Live-patching requires unique symbols, and sadly the clang build
> gene
On 27.11.19 17:25, Jan Beulich wrote:
On 27.11.2019 17:21, George Dunlap wrote:
On 11/27/19 4:14 PM, Jan Beulich wrote:
On 27.11.2019 17:01, Roger Pau Monne wrote:
Live-patching requires unique symbols, and sadly the clang build
generates a lot of duplicate symbols:
Duplicate symbol 'asid.c#g
On 27.11.2019 17:21, George Dunlap wrote:
> On 11/27/19 4:14 PM, Jan Beulich wrote:
>> On 27.11.2019 17:01, Roger Pau Monne wrote:
>>> Live-patching requires unique symbols, and sadly the clang build
>>> generates a lot of duplicate symbols:
>>>
>>> Duplicate symbol 'asid.c#get_cpu_info' (82d08
On 11/27/19 4:14 PM, Jan Beulich wrote:
> On 27.11.2019 17:01, Roger Pau Monne wrote:
>> Live-patching requires unique symbols, and sadly the clang build
>> generates a lot of duplicate symbols:
>>
>> Duplicate symbol 'asid.c#get_cpu_info' (82d0803032c0 != 82d0802e0f50)
>> Duplicate symbol
On 27.11.2019 17:01, Roger Pau Monne wrote:
> Live-patching requires unique symbols, and sadly the clang build
> generates a lot of duplicate symbols:
>
> Duplicate symbol 'asid.c#get_cpu_info' (82d0803032c0 != 82d0802e0f50)
> Duplicate symbol 'asid.c#get_cpu_info_from_stack' (82d0802e
11 matches
Mail list logo
