Re: renesas-drivers-2014-07-07-v3.16-rc4

[Khiem Nguyen <khiem.nguyen.xt@renesas.com>]

Hi Geert,

Thanks for your explanation.

I have one more question.
I assumed you also confirm kernel build and/or kernel boot
for some board defconfigs (e.g lager/koelsch) for any new release.

Is it correct ?

Best regards,
KHIEM Nguyen

On 7/8/2014 3:45 PM, Geert Uytterhoeven wrote:
> Hi Nguyen-san,
> 
> On Tue, Jul 8, 2014 at 12:35 AM, Khiem Nguyen
> <khiem.nguyen.xt@renesas.com> wrote:
>> Could you clarify how developers should use your tree and Simon tree ?
> 
> The goal of my tree is to serve as a good base for development/testing on
> shmobile platforms. It contains the latest (accepted) support code for
> shmobile platforms and drivers, to be integrated in upstream releases soon.
> Hence people no longer have to look around in various maintainer trees
> to find shmobile driver updates that are meant for the next kernel release.
> 
>> - Currently, as my understanding, patches are developed and submitted
>>   base on devel branch of Simon tree.
> 
> Yes, but this applied to patches touching the shmobile platform code only.
> 
>> - So, with your tree, patches will be developed base on your tree and you
>>   and/or Simon will re-base into devel branch of Simon tree for upstream ?
> 
> Patches touching the shmobile platform code should still be sent to Simon.
> Patches touching other parts of the tree should still be sent to the appropriate
> maintainer, who will integrate them. There's no change in that.
> 
> I hope this answers your question. Thanks!
> 
> Gr{oetje,eeting}s,
> 
>                         Geert
> 
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
> 
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
>                                 -- Linus Torvalds
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>