On 4/24/19 9:47 AM, Bruce Ashfield wrote:
On Tue, Apr 23, 2019 at 9:35 PM Hongzhi, Song
mailto:hongzhi.s...@windriver.com>> wrote:
On 4/24/19 4:04 AM, Bruce Ashfield wrote:
Since this is still being discussed on the -rt mailing list, I'm
going to wait to see how that shakes ou
On Tue, Apr 23, 2019 at 9:35 PM Hongzhi, Song
wrote:
>
> On 4/24/19 4:04 AM, Bruce Ashfield wrote:
>
> Since this is still being discussed on the -rt mailing list, I'm going to
> wait to see how that shakes out before merging the change.
>
>
> Yes, but it seems like that upstream won't fix the is
On 4/24/19 4:04 AM, Bruce Ashfield wrote:
Since this is still being discussed on the -rt mailing list, I'm going
to wait to see how that shakes out before merging the change.
Yes, but it seems like that upstream won't fix the issue in a short time.
--Hongzhi
Bruce
On Mon, Apr 22, 2019
Since this is still being discussed on the -rt mailing list, I'm going to
wait to see how that shakes out before merging the change.
Bruce
On Mon, Apr 22, 2019 at 11:20 PM Hongzhi, Song
wrote:
> Please merge to v5.0/standard/preempt-rt/base and
> v5.0/standard/preempt-rt/intel-x86
>
>
> --Hongz
Please merge to v5.0/standard/preempt-rt/base and
v5.0/standard/preempt-rt/intel-x86
--Hongzhi
On 4/23/19 11:14 AM, Hongzhi.Song wrote:
Two commits from rt-kernel cause the following disorder log at the
early stage of boot with qemux86-64. Maybe it has other disorder logs
which I omit.
Comm
Two commits from rt-kernel cause the following disorder log at the
early stage of boot with qemux86-64. Maybe it has other disorder logs
which I omit.
Commits:
7128a815: printk: introduce emergency messages
b9d460e4: serial: 8250: implement write_atomic
[0.401166] 000: 6200.04 BogoMIPS (lpj=3
