On 18 August 2017 at 14:52, Steven Rostedt wrote:
> On Fri, 18 Aug 2017 14:44:15 +0100
> Ard Biesheuvel wrote:
>
>> >> It appears the stuff above needs to be move inside the double-include
>> >> guard (which oddly enough does not cover the entire file)
>> >
>> > Why was this moved to the header f
On Fri, 18 Aug 2017 14:44:15 +0100
Ard Biesheuvel wrote:
> >> It appears the stuff above needs to be move inside the double-include
> >> guard (which oddly enough does not cover the entire file)
> >
> > Why was this moved to the header file? To fulfill some checkpatch
> > warning?
> >
>
> Ye
On 18 August 2017 at 14:43, Steven Rostedt wrote:
> On Fri, 18 Aug 2017 12:44:17 +0100
> Ard Biesheuvel wrote:
>
>> On 18 August 2017 at 12:26, Ard Biesheuvel wrote:
>> > To avoid the need for relocating absolute references to tracepoint
>> > structures at boot time when running relocatable kern
On Fri, 18 Aug 2017 12:44:17 +0100
Ard Biesheuvel wrote:
> On 18 August 2017 at 12:26, Ard Biesheuvel wrote:
> > To avoid the need for relocating absolute references to tracepoint
> > structures at boot time when running relocatable kernels (which may
> > take a disproportionate amount of space)
On 18 August 2017 at 12:26, Ard Biesheuvel wrote:
> To avoid the need for relocating absolute references to tracepoint
> structures at boot time when running relocatable kernels (which may
> take a disproportionate amount of space), add the option to emit
> these tables as relative references inst
To avoid the need for relocating absolute references to tracepoint
structures at boot time when running relocatable kernels (which may
take a disproportionate amount of space), add the option to emit
these tables as relative references instead.
Cc: Steven Rostedt
Cc: Ingo Molnar
Signed-off-by: A
6 matches
Mail list logo
