On 04/09, Steven Rostedt wrote:
>On Tue, 10 Apr 2018 09:23:40 +0800
>Ye Xiaolong wrote:
>
>> Hi, Steven
>>
>> On 04/09, Steven Rostedt wrote:
>> >On Mon, 9 Apr 2018 13:32:52 +0800
>> >kernel test robot wrote:
>> >
>> >> FYI, we noticed the following commit (built with gcc-7):
>> >>
>> >> comm
On Tue, 10 Apr 2018 09:23:40 +0800
Ye Xiaolong wrote:
> Hi, Steven
>
> On 04/09, Steven Rostedt wrote:
> >On Mon, 9 Apr 2018 13:32:52 +0800
> >kernel test robot wrote:
> >
> >> FYI, we noticed the following commit (built with gcc-7):
> >>
> >> commit: 2580d6b795e25879c825a0891cf67390f665b11f
Hi, Steven
On 04/09, Steven Rostedt wrote:
>On Mon, 9 Apr 2018 13:32:52 +0800
>kernel test robot wrote:
>
>> FYI, we noticed the following commit (built with gcc-7):
>>
>> commit: 2580d6b795e25879c825a0891cf67390f665b11f ("init, tracing: Have
>> printk come through the trace events for initcall
On Mon, 9 Apr 2018 13:32:52 +0800
kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: 2580d6b795e25879c825a0891cf67390f665b11f ("init, tracing: Have printk
> come through the trace events for initcall_debug")
> url:
> https://github.com/0day-ci/linux
FYI, we noticed the following commit (built with gcc-7):
commit: 2580d6b795e25879c825a0891cf67390f665b11f ("init, tracing: Have printk
come through the trace events for initcall_debug")
url:
https://github.com/0day-ci/linux/commits/Steven-Rostedt/init-tracing/20180407-130743
in testcase: boot
5 matches
Mail list logo