On 10/21/2015 01:53 PM, Christian Boltz wrote:
> Hello,
>
> Am Dienstag, 20. Oktober 2015 schrieb John Johansen:
>> On 07/20/2015 12:22 PM, Christian Boltz wrote:
>>> for debugging, it's helpful to know which part of the code
>>> initialized a profile_storage and for which profile and hat this
Hello,
Am Dienstag, 20. Oktober 2015 schrieb John Johansen:
> On 07/20/2015 12:22 PM, Christian Boltz wrote:
> > for debugging, it's helpful to know which part of the code
> > initialized a profile_storage and for which profile and hat this
> > was done.
> >
> > This patch adds an 'info' array
On 07/20/2015 12:22 PM, Christian Boltz wrote:
> Hello,
>
> for debugging, it's helpful to know which part of the code initialized a
> profile_storage and for which profile and hat this was done.
>
> This patch adds an 'info' array with that information, adds the
> corresponding parameters to
Hello,
On Tue, Jul 21, 2015 at 12:52 AM, Christian Boltz appar...@cboltz.de
wrote:
Hello,
for debugging, it's helpful to know which part of the code initialized a
profile_storage and for which profile and hat this was done.
This patch adds an 'info' array with that information, adds the
Hello,
Am Montag, 3. August 2015 schrieb Kshitij Gupta:
On Tue, Jul 21, 2015 at 12:52 AM, Christian Boltz wrote:
for debugging, it's helpful to know which part of the code
initialized a profile_storage and for which profile and hat this
was done.
This patch adds an 'info' array with
Hello,
for debugging, it's helpful to know which part of the code initialized a
profile_storage and for which profile and hat this was done.
This patch adds an 'info' array with that information, adds the
corresponding parameters to profile_storage() and changes the callers to
deliver some
