2017. 8. 4. 오후 7:04 Robin Murphy 작성:
>> On 04/08/17 07:07, Hoeun Ryu wrote:
>> Hello, Russell King.
>>
>> The following patch has not merged yet.
>> Do you have a plan to accept and merge this patch ?
>
> This should probably go through the ARM tree, so please submit it
2017. 8. 4. 오후 7:04 Robin Murphy 작성:
>> On 04/08/17 07:07, Hoeun Ryu wrote:
>> Hello, Russell King.
>>
>> The following patch has not merged yet.
>> Do you have a plan to accept and merge this patch ?
>
> This should probably go through the ARM tree, so please submit it to
> Russell's
On 04/08/17 07:07, Hoeun Ryu wrote:
> Hello, Russell King.
>
> The following patch has not merged yet.
> Do you have a plan to accept and merge this patch ?
This should probably go through the ARM tree, so please submit it to
Russell's patch-tracking system here:
On 04/08/17 07:07, Hoeun Ryu wrote:
> Hello, Russell King.
>
> The following patch has not merged yet.
> Do you have a plan to accept and merge this patch ?
This should probably go through the ARM tree, so please submit it to
Russell's patch-tracking system here:
Hello, Russell King.
The following patch has not merged yet.
Do you have a plan to accept and merge this patch ?
Thank you.
On Mon, 2017-06-12 at 10:47 +0900, Hoeun Ryu wrote:
> Reading TTBCR in early boot stage might return the value of the previous
> kernel's configuration, especially in
Hello, Russell King.
The following patch has not merged yet.
Do you have a plan to accept and merge this patch ?
Thank you.
On Mon, 2017-06-12 at 10:47 +0900, Hoeun Ryu wrote:
> Reading TTBCR in early boot stage might return the value of the previous
> kernel's configuration, especially in
Hello, Russell King.
Do you have a plan to include this patch in your tree ?
Thank you.
On Mon, 2017-06-12 at 10:47 +0900, Hoeun Ryu wrote:
> Reading TTBCR in early boot stage might return the value of the
> previous
> kernel's configuration, especially in case of kexec. For example, if
>
Hello, Russell King.
Do you have a plan to include this patch in your tree ?
Thank you.
On Mon, 2017-06-12 at 10:47 +0900, Hoeun Ryu wrote:
> Reading TTBCR in early boot stage might return the value of the
> previous
> kernel's configuration, especially in case of kexec. For example, if
>
On Sat, Jun 10, 2017 at 01:43:24PM +0900, Hoeun Ryu wrote:
> Hello, Russell and Robin.
>
> Would you please review this patch ?
I think it's fine, thanks.
>
> Than you
>
> > On Jun 7, 2017, at 11:39 AM, Hoeun Ryu wrote:
> >
> > Reading TTBCR in early boot stage might
On Sat, Jun 10, 2017 at 01:43:24PM +0900, Hoeun Ryu wrote:
> Hello, Russell and Robin.
>
> Would you please review this patch ?
I think it's fine, thanks.
>
> Than you
>
> > On Jun 7, 2017, at 11:39 AM, Hoeun Ryu wrote:
> >
> > Reading TTBCR in early boot stage might return the value of the
Hello, Russell and Robin.
Would you please review this patch ?
Than you
> On Jun 7, 2017, at 11:39 AM, Hoeun Ryu wrote:
>
> Reading TTBCR in early boot stage might return the value of the previous
> kernel's configuration, especially in case of kexec. For example, if
>
Hello, Russell and Robin.
Would you please review this patch ?
Than you
> On Jun 7, 2017, at 11:39 AM, Hoeun Ryu wrote:
>
> Reading TTBCR in early boot stage might return the value of the previous
> kernel's configuration, especially in case of kexec. For example, if
> normal kernel (first
12 matches
Mail list logo