On 2018-06-01 15:02, Joel Fernandes wrote:
On Fri, Jun 01, 2018 at 12:07:48PM +0900, Byungchul Park wrote:
On 2018-05-25 14:13, Byungchul Park wrote:
On 2018-05-09 15:33, Byungchul Park wrote:
On Thu, Jan 11, 2018 at 10:07:16AM +0100, Peter Zijlstra wrote:
Sorry for the huge delay
On 2018-06-01 15:02, Joel Fernandes wrote:
On Fri, Jun 01, 2018 at 12:07:48PM +0900, Byungchul Park wrote:
On 2018-05-25 14:13, Byungchul Park wrote:
On 2018-05-09 15:33, Byungchul Park wrote:
On Thu, Jan 11, 2018 at 10:07:16AM +0100, Peter Zijlstra wrote:
Sorry for the huge delay
On Fri, Jun 01, 2018 at 12:07:48PM +0900, Byungchul Park wrote:
>
>
> On 2018-05-25 14:13, Byungchul Park wrote:
> >
> >
> > On 2018-05-09 15:33, Byungchul Park wrote:
> > > On Thu, Jan 11, 2018 at 10:07:16AM +0100, Peter Zijlstra wrote:
> > > >
> > > >
> > > > Sorry for the huge delay on
On Fri, Jun 01, 2018 at 12:07:48PM +0900, Byungchul Park wrote:
>
>
> On 2018-05-25 14:13, Byungchul Park wrote:
> >
> >
> > On 2018-05-09 15:33, Byungchul Park wrote:
> > > On Thu, Jan 11, 2018 at 10:07:16AM +0100, Peter Zijlstra wrote:
> > > >
> > > >
> > > > Sorry for the huge delay on
On 2018-05-25 14:13, Byungchul Park wrote:
On 2018-05-09 15:33, Byungchul Park wrote:
On Thu, Jan 11, 2018 at 10:07:16AM +0100, Peter Zijlstra wrote:
Sorry for the huge delay on this, but I'll have to postpone further.
Still busy with meltdown/spectre stuff.
Please consider this. Even
On 2018-05-25 14:13, Byungchul Park wrote:
On 2018-05-09 15:33, Byungchul Park wrote:
On Thu, Jan 11, 2018 at 10:07:16AM +0100, Peter Zijlstra wrote:
Sorry for the huge delay on this, but I'll have to postpone further.
Still busy with meltdown/spectre stuff.
Please consider this. Even
On 2018-05-09 15:33, Byungchul Park wrote:
On Thu, Jan 11, 2018 at 10:07:16AM +0100, Peter Zijlstra wrote:
Sorry for the huge delay on this, but I'll have to postpone further.
Still busy with meltdown/spectre stuff.
Please consider this. Even though it's not a big bug, anyway leading
On 2018-05-09 15:33, Byungchul Park wrote:
On Thu, Jan 11, 2018 at 10:07:16AM +0100, Peter Zijlstra wrote:
Sorry for the huge delay on this, but I'll have to postpone further.
Still busy with meltdown/spectre stuff.
Please consider this. Even though it's not a big bug, anyway leading
On Thu, Jan 11, 2018 at 10:07:16AM +0100, Peter Zijlstra wrote:
>
>
> Sorry for the huge delay on this, but I'll have to postpone further.
> Still busy with meltdown/spectre stuff.
Please consider this. Even though it's not a big bug, anyway leading
mis-behavior in certain situaions.
On Thu, Jan 11, 2018 at 10:07:16AM +0100, Peter Zijlstra wrote:
>
>
> Sorry for the huge delay on this, but I'll have to postpone further.
> Still busy with meltdown/spectre stuff.
Please consider this. Even though it's not a big bug, anyway leading
mis-behavior in certain situaions.
On 3/13/2018 2:52 PM, Byungchul Park wrote:
On 1/11/2018 6:07 PM, Peter Zijlstra wrote:
Sorry for the huge delay on this, but I'll have to postpone further.
Still busy with meltdown/spectre stuff.
Could you review the patch?
Hello,
Could you see the patch now?
--
Thanks,
Byungchul
On 3/13/2018 2:52 PM, Byungchul Park wrote:
On 1/11/2018 6:07 PM, Peter Zijlstra wrote:
Sorry for the huge delay on this, but I'll have to postpone further.
Still busy with meltdown/spectre stuff.
Could you review the patch?
Hello,
Could you see the patch now?
--
Thanks,
Byungchul
On 1/11/2018 6:07 PM, Peter Zijlstra wrote:
Sorry for the huge delay on this, but I'll have to postpone further.
Still busy with meltdown/spectre stuff.
Could you review the patch?
--
Thanks,
Byungchul
On 1/11/2018 6:07 PM, Peter Zijlstra wrote:
Sorry for the huge delay on this, but I'll have to postpone further.
Still busy with meltdown/spectre stuff.
Could you review the patch?
--
Thanks,
Byungchul
On 1/11/2018 6:07 PM, Peter Zijlstra wrote:
Sorry for the huge delay on this, but I'll have to postpone further.
Still busy with meltdown/spectre stuff.
Do you have time to see the patch, now that it seems to be managed
to solve those security issues?
--
Thanks,
Byungchul
On 1/11/2018 6:07 PM, Peter Zijlstra wrote:
Sorry for the huge delay on this, but I'll have to postpone further.
Still busy with meltdown/spectre stuff.
Do you have time to see the patch, now that it seems to be managed
to solve those security issues?
--
Thanks,
Byungchul
On 1/11/2018 6:07 PM, Peter Zijlstra wrote:
Sorry for the huge delay on this, but I'll have to postpone further.
Still busy with meltdown/spectre stuff.
Do you have time to see these patches and another set, now?
--
Thanks,
Byungchul
On 1/11/2018 6:07 PM, Peter Zijlstra wrote:
Sorry for the huge delay on this, but I'll have to postpone further.
Still busy with meltdown/spectre stuff.
Do you have time to see these patches and another set, now?
--
Thanks,
Byungchul
Sorry for the huge delay on this, but I'll have to postpone further.
Still busy with meltdown/spectre stuff.
Sorry for the huge delay on this, but I'll have to postpone further.
Still busy with meltdown/spectre stuff.
On Tue, Dec 19, 2017 at 10:19:23AM +0900, Byungchul Park wrote:
> Changes from v2
> - Run spellchecker over the text and fix typos
> - Add acked-by Daniel
>
> Changes from v1
> - Enhance commit msg
> - Prevent WARN in cpumask_test_cpu() in cpudl_find() when best_cpu == -1
Hello, shall I stop
On Tue, Dec 19, 2017 at 10:19:23AM +0900, Byungchul Park wrote:
> Changes from v2
> - Run spellchecker over the text and fix typos
> - Add acked-by Daniel
>
> Changes from v1
> - Enhance commit msg
> - Prevent WARN in cpumask_test_cpu() in cpudl_find() when best_cpu == -1
Hello, shall I stop
22 matches
Mail list logo
