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

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

[Geert Uytterhoeven]

Hi all,

I've pushed renesas-drivers-2014-07-07-v3.16-rc4 to
https://git.kernel.org/cgit/linux/kernel/git/geert/renesas-drivers.git
This tree is meant to ease development of platform support and drivers for
Renesas ARM ("shmobile") SoCs. It's created by merging the for-next branches
of various subsystem trees into the development branch of Simon Horman's
renesas.git tree.

Today's version is based on renesas-devel-v3.16-rc4-20140707, and contains
the following for-next branches:

git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git#linux-next
git://git.linaro.org/people/mturquette/linux.git#clk-next
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git#for-next
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git#for-next
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git#for-next
git://git.infradead.org/users/dedekind/l2-mtd-2.6.git#master
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git#master
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git#tty-next
git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git#i2c/for-next
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git#asoc/for-next
git://gitorious.org/linux-can/linux-can-next.git#master
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git#usb-next
git://people.freedesktop.org/~airlied/linux#drm-next
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git#next
git://linuxtv.org/mchehab/media-next.git#master
git://git.kernel.org/pub/scm/linux/kernel/git/cjb/mmc.git#mmc-next
git://git.kernel.org/pub/scm/linux/kernel/git/thierry.reding/linux-pwm.git#for-next
git://git.linaro.org/people/daniel.lezcano/linux.git#clockevents/next
git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git#next
git://git.kernel.org/pub/scm/linux/kernel/git/djbw/dmaengine.git#next
git://git.infradead.org/users/vkoul/slave-dma.git#next
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git#staging-next
git://ftp.arm.linux.org.uk/pub/linux/arm/kernel/git-cur/linux-arm.git#for-next

If anything is missing, please tell me.

Thanks for your comments!

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

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

[Geert Uytterhoeven]

Hi Morimoto-san,

On Mon, Jul 7, 2014 at 1:05 PM, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> Today's version is based on renesas-devel-v3.16-rc4-20140707, and contains
> the following for-next branches:

> git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git#asoc/for-next

I had a merge conflict due to commit 7635dd189e6f3d8fb007c7a2e3bf93957a82d009
("local: ASoC: rsnd: fixup rsnd_gen_dma_addr() for Gen1") in Simon's tree.
I assume this was fixed differently in the sound-asoc tree, so I reverted the
local fix in Simon's tree. Is that correct?

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

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

[Simon Horman]

On Mon, Jul 07, 2014 at 01:07:12PM +0200, Geert Uytterhoeven wrote:
> Hi Morimoto-san,
> 
> On Mon, Jul 7, 2014 at 1:05 PM, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > Today's version is based on renesas-devel-v3.16-rc4-20140707, and contains
> > the following for-next branches:
> 
> > git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git#asoc/for-next
> 
> I had a merge conflict due to commit 7635dd189e6f3d8fb007c7a2e3bf93957a82d009
> ("local: ASoC: rsnd: fixup rsnd_gen_dma_addr() for Gen1") in Simon's tree.
> I assume this was fixed differently in the sound-asoc tree, so I reverted the
> local fix in Simon's tree. Is that correct?

I suspect so. Morimoto-san, can you double-check.

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

[Khiem Nguyen]

Hi Geert,

Thanks for creating this.

I have a naive question about its usage.
Could you clarify how developers should use your tree and Simon tree ?

- Currently, as my understanding, patches are developed and submitted 
  base on devel branch of Simon tree.
- 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 ?

Is it how it will work ?

Thanks.

Best regards,
KHIEM Nguyen

On 7/7/2014 8:05 PM, Geert Uytterhoeven wrote:
> Hi all,
> 
> I've pushed renesas-drivers-2014-07-07-v3.16-rc4 to
> https://git.kernel.org/cgit/linux/kernel/git/geert/renesas-drivers.git
> This tree is meant to ease development of platform support and drivers for
> Renesas ARM ("shmobile") SoCs. It's created by merging the for-next branches
> of various subsystem trees into the development branch of Simon Horman's
> renesas.git tree.
> 
> Today's version is based on renesas-devel-v3.16-rc4-20140707, and contains
> the following for-next branches:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git#linux-next
> git://git.linaro.org/people/mturquette/linux.git#clk-next
> git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git#for-next
> git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git#for-next
> git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git#for-next
> git://git.infradead.org/users/dedekind/l2-mtd-2.6.git#master
> git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git#master
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git#tty-next
> git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git#i2c/for-next
> git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git#asoc/for-next
> git://gitorious.org/linux-can/linux-can-next.git#master
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git#usb-next
> git://people.freedesktop.org/~airlied/linux#drm-next
> git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git#next
> git://linuxtv.org/mchehab/media-next.git#master
> git://git.kernel.org/pub/scm/linux/kernel/git/cjb/mmc.git#mmc-next
> git://git.kernel.org/pub/scm/linux/kernel/git/thierry.reding/linux-pwm.git#for-next
> git://git.linaro.org/people/daniel.lezcano/linux.git#clockevents/next
> git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git#next
> git://git.kernel.org/pub/scm/linux/kernel/git/djbw/dmaengine.git#next
> git://git.infradead.org/users/vkoul/slave-dma.git#next
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git#staging-next
> git://ftp.arm.linux.org.uk/pub/linux/arm/kernel/git-cur/linux-arm.git#for-next
> 
> If anything is missing, please tell me.
> 
> Thanks for your comments!
> 
> 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
> 

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

[Kuninori Morimoto]

Hi Geert, Simon

> > > Today's version is based on renesas-devel-v3.16-rc4-20140707, and contains
> > > the following for-next branches:
> > 
> > > git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git#asoc/for-next
> > 
> > I had a merge conflict due to commit 7635dd189e6f3d8fb007c7a2e3bf93957a82d009
> > ("local: ASoC: rsnd: fixup rsnd_gen_dma_addr() for Gen1") in Simon's tree.
> > I assume this was fixed differently in the sound-asoc tree, so I reverted the
> > local fix in Simon's tree. Is that correct?
> 
> I suspect so. Morimoto-san, can you double-check.

Yes, it is correct !
Thank you

Best regards
---
Kuninori Morimoto

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

[Geert Uytterhoeven]

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

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

[Simon Horman]

On Mon, Jul 07, 2014 at 07:55:26PM -0700, Kuninori Morimoto wrote:
> 
> Hi Geert, Simon
> 
> > > > Today's version is based on renesas-devel-v3.16-rc4-20140707, and contains
> > > > the following for-next branches:
> > > 
> > > > git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git#asoc/for-next
> > > 
> > > I had a merge conflict due to commit 7635dd189e6f3d8fb007c7a2e3bf93957a82d009
> > > ("local: ASoC: rsnd: fixup rsnd_gen_dma_addr() for Gen1") in Simon's tree.
> > > I assume this was fixed differently in the sound-asoc tree, so I reverted the
> > > local fix in Simon's tree. Is that correct?
> > 
> > I suspect so. Morimoto-san, can you double-check.
> 
> Yes, it is correct !

Thanks, I'll drop the local fix from devel once it shows up
in an rc release (and I get a conflict).

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

[Khiem Nguyen]

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
> 

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

[Geert Uytterhoeven]

Hi Ngyen-san.

On Thu, Jul 10, 2014 at 1:11 AM, Khiem Nguyen
<khiem.nguyen.xt@renesas.com> wrote:
> I assumed you also confirm kernel build and/or kernel boot
> for some board defconfigs (e.g lager/koelsch) for any new release.

Yes, I usually build and boot test koelsch, both legacy and
reference/multi-platform.

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

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

[Khiem Nguyen]

Hi Geert,

On 7/10/2014 4:35 PM, Geert Uytterhoeven wrote:
> Hi Ngyen-san.
> 
> On Thu, Jul 10, 2014 at 1:11 AM, Khiem Nguyen
> <khiem.nguyen.xt@renesas.com> wrote:
>> I assumed you also confirm kernel build and/or kernel boot
>> for some board defconfigs (e.g lager/koelsch) for any new release.
> 
> Yes, I usually build and boot test koelsch, both legacy and
> reference/multi-platform.

Understood. Thanks.

-- 
Best regards,
KHIEM Nguyen