renesas-drivers-2016-06-28-v4.7-rc5

renesas-drivers-2016-06-28-v4.7-rc5

[Geert Uytterhoeven]

I have pushed renesas-drivers-2016-06-28-v4.7-rc5 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 SoCs. It is created by merging (a) the for-next branches
of various subsystem trees and (b) branches with driver code submitted
or planned for submission to maintainers into the development branch of
Simon Horman's renesas.git tree.

Today's version is based on renesas-devel-20160627-v4.7-rc5.

Included branches with driver code:
  - clk-renesas-for-v4.8
  - sh-pfc-for-v4.8
  - topic/r8a7796-clk-wdt-v1
  - topic/r8a7796-rwdt-v1
  - topic/rcar-dmac-niklas
  - topic/ipmmu-multi-arch-v4
  - topic/r8a7795-ipmmu-v2-rebased1
  - topic/r8a7796-ipmmu-v1-rebased1
  - topic/salvator-x-ipmmu-rfc-v3-rebased4
  - topic/spi-slave-v1
  - topic/apmu-dt-v5
  - git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git#topic/sdr104-v3
  - git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git#renesas/topic/pretimeout
  - topic/h3-pfc-set-voltage-v1-rebased2~1
  - https://git.ragnatech.se/linux#for-renesas-drivers
  - git://linuxtv.org/pinchartl/media.git#for/renesas-drivers
  - topic/fcpf-v1-rebased4
  - topic/r8a7796-pfc-v1

Included subsystem trees:
  - git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git#linux-next
  - git://git.kernel.org/pub/scm/linux/kernel/git/clk/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#for-next
  - git://git.kernel.org/pub/scm/linux/kernel/git/mkl/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.linaro.org/people/ulf.hansson/mmc.git#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#testing/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://git.armlinux.org.uk/~rmk/linux-arm.git#for-next
  - git://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux.git#next
  - git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git#for-next
  - git://git.infradead.org/users/jcooper/linux.git#irqchip/for-next
  - git://git.kernel.org/pub/scm/linux/kernel/git/tomba/linux.git#for-next
  - git://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git#for-next
  - git://git.infradead.org/battery-2.6.git#master
  - git://www.linux-watchdog.org/linux-watchdog-next.git#master
  - git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git#for-next
  - git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git#for-next
  - git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git#for-next/core
  - git://anongit.freedesktop.org/drm-intel#topic/drm-misc
  - git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git#next
  - git://git.kernel.org/pub/scm/linux/kernel/git/kishon/linux-phy.git#next
  - git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal.git#next

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-2016-06-28-v4.7-rc5

[Kuninori Morimoto]

Hi Geert

> I have pushed renesas-drivers-2016-06-28-v4.7-rc5 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 SoCs. It is created by merging (a) the for-next branches
> of various subsystem trees and (b) branches with driver code submitted
> or planned for submission to maintainers into the development branch of
> Simon Horman's renesas.git tree.
> 
> Today's version is based on renesas-devel-20160627-v4.7-rc5.

Can we have new version of below branches for -rc5 branch ?
Or for next new renesas-drivers ?

	salvator-x-hdmi-prototype-drivers-X
	salvator-x-hdmi-prototype-integration-X

My picky opinion is that
it is easy to understand that above additional branch has
same/similar naming of base branch...

	ex) salvator-x-hdmi-prototype-drivers-20160627-v4.7-rc5

Re: renesas-drivers-2016-06-28-v4.7-rc5

[Geert Uytterhoeven]

Hi Morimoto-san,

On Tue, Jul 5, 2016 at 3:40 AM, Kuninori Morimoto
<kuninori.morimoto.gx@renesas.com> wrote:
>> I have pushed renesas-drivers-2016-06-28-v4.7-rc5 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 SoCs. It is created by merging (a) the for-next branches
>> of various subsystem trees and (b) branches with driver code submitted
>> or planned for submission to maintainers into the development branch of
>> Simon Horman's renesas.git tree.
>>
>> Today's version is based on renesas-devel-20160627-v4.7-rc5.
>
> Can we have new version of below branches for -rc5 branch ?
> Or for next new renesas-drivers ?
>
>         salvator-x-hdmi-prototype-drivers-X
>         salvator-x-hdmi-prototype-integration-X
>
> My picky opinion is that
> it is easy to understand that above additional branch has
> same/similar naming of base branch...
>
>         ex) salvator-x-hdmi-prototype-drivers-20160627-v4.7-rc5

Currently I provide e.g.:

  topic/salvator-x-hdmi-prototype-drivers-v3-rebased2
  topic/salvator-x-hdmi-prototype-integration-v3-rebased4

The drivers branch needs only a rebase when Laurent's for/renesas-drivers
changes, while the integration branch needs a rebase after each
renesas-drivers release.

I'll merge both of them in topic/salvator-x-hdmi-prototype-v3-<date>-<version>.
Would that be OK for you?

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-2016-06-28-v4.7-rc5

[Kuninori Morimoto]

Hi Geert

> Currently I provide e.g.:
> 
>   topic/salvator-x-hdmi-prototype-drivers-v3-rebased2
>   topic/salvator-x-hdmi-prototype-integration-v3-rebased4
> 
> The drivers branch needs only a rebase when Laurent's for/renesas-drivers
> changes, while the integration branch needs a rebase after each
> renesas-drivers release.
> 
> I'll merge both of them in topic/salvator-x-hdmi-prototype-v3-<date>-<version>.
> Would that be OK for you?

Thank you for your help.
New naming rule is easy to understand for me.
But, I wonder do we need -v3- ?
We don't use old prototype on latest branch,
so, <date> and <verion> is very enough ?
Not a big deal though.

Re: renesas-drivers-2016-06-28-v4.7-rc5

[Geert Uytterhoeven]

Hi Morimoto-san,

On Tue, Jul 5, 2016 at 9:31 AM, Kuninori Morimoto
<kuninori.morimoto.gx@renesas.com> wrote:
>> Currently I provide e.g.:
>>
>>   topic/salvator-x-hdmi-prototype-drivers-v3-rebased2
>>   topic/salvator-x-hdmi-prototype-integration-v3-rebased4
>>
>> The drivers branch needs only a rebase when Laurent's for/renesas-drivers
>> changes, while the integration branch needs a rebase after each
>> renesas-drivers release.
>>
>> I'll merge both of them in topic/salvator-x-hdmi-prototype-v3-<date>-<version>.
>> Would that be OK for you?
>
> Thank you for your help.
> New naming rule is easy to understand for me.
> But, I wonder do we need -v3- ?
> We don't use old prototype on latest branch,
> so, <date> and <verion> is very enough ?
> Not a big deal though.

Indeed, we don't need it, as we can identify the prototype patchset version
from the individual topic/salvator-x-hdmi-prototype-drivers-v* and
topic/salvator-x-hdmi-prototype-integration-v* branches that are included.

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