linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Khiem Nguyen <khiem.nguyen.xt@renesas.com>
To: linux-sh@vger.kernel.org
Subject: Re: renesas-drivers-2014-07-07-v3.16-rc4
Date: Mon, 07 Jul 2014 22:35:06 +0000	[thread overview]
Message-ID: <53BB209A.5030303@renesas.com> (raw)
In-Reply-To: <CAMuHMdVTOabkGyJW-jRxXjtGHdA0W=APoiMYWAtvP3y_auqXKg@mail.gmail.com>

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
> 

  parent reply	other threads:[~2014-07-07 22:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-07 11:05 renesas-drivers-2014-07-07-v3.16-rc4 Geert Uytterhoeven
2014-07-07 11:07 ` renesas-drivers-2014-07-07-v3.16-rc4 Geert Uytterhoeven
2014-07-07 12:53 ` renesas-drivers-2014-07-07-v3.16-rc4 Simon Horman
2014-07-07 22:35 ` Khiem Nguyen [this message]
2014-07-08  2:55 ` renesas-drivers-2014-07-07-v3.16-rc4 Kuninori Morimoto
2014-07-08  6:45 ` renesas-drivers-2014-07-07-v3.16-rc4 Geert Uytterhoeven
2014-07-08  9:45 ` renesas-drivers-2014-07-07-v3.16-rc4 Simon Horman
2014-07-09 23:11 ` renesas-drivers-2014-07-07-v3.16-rc4 Khiem Nguyen
2014-07-10  7:35 ` renesas-drivers-2014-07-07-v3.16-rc4 Geert Uytterhoeven
2014-07-10  7:41 ` renesas-drivers-2014-07-07-v3.16-rc4 Khiem Nguyen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53BB209A.5030303@renesas.com \
    --to=khiem.nguyen.xt@renesas.com \
    --cc=linux-sh@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).