On 14.06.2011, at 13:19, Jan Kiszka wrote:
> On 2011-06-14 13:17, Alexander Graf wrote:
>>
>> On 14.06.2011, at 13:07, Jan Kiszka wrote:
>>
>>> On 2011-06-14 13:05, Alexander Graf wrote:
On 08.06.2011, at 16:11, Jan Kiszka wrote:
> No longer needed with accompanied kernel h
On 2011-06-14 13:05, Alexander Graf wrote:
>
> On 08.06.2011, at 16:11, Jan Kiszka wrote:
>
>> No longer needed with accompanied kernel headers. We are only left with
>> build dependencies that are controlled by kvm arch headers.
>
> This should completely rule out all CAPs right? IIRC, all CAPs
On 14.06.2011, at 13:07, Jan Kiszka wrote:
> On 2011-06-14 13:05, Alexander Graf wrote:
>>
>> On 08.06.2011, at 16:11, Jan Kiszka wrote:
>>
>>> No longer needed with accompanied kernel headers. We are only left with
>>> build dependencies that are controlled by kvm arch headers.
>>
>> This sho
On 2011-06-14 13:17, Alexander Graf wrote:
>
> On 14.06.2011, at 13:07, Jan Kiszka wrote:
>
>> On 2011-06-14 13:05, Alexander Graf wrote:
>>>
>>> On 08.06.2011, at 16:11, Jan Kiszka wrote:
>>>
No longer needed with accompanied kernel headers. We are only left with
build dependencies tha
On 08.06.2011, at 16:11, Jan Kiszka wrote:
> No longer needed with accompanied kernel headers. We are only left with
> build dependencies that are controlled by kvm arch headers.
This should completely rule out all CAPs right? IIRC, all CAPs are defined in
generic code, so we don't get number o