All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Turquette <mturquette@ti.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	broonie@opensource.wolfsonmicro.com, rnayak@ti.com,
	viresh.kumar@linaro.org, amit.kucheria@linaro.org,
	linus.walleij@stericsson.com, shawn.guo@freescale.com,
	mkl@pengutronix.de, sr@denx.de, pawel.moll@arm.com,
	maxime.ripard@free-electrons.com, linux@arm.linux.org.uk,
	arnd.bergmann@linaro.org, olof@lixom.net
Subject: Re: linux-next: adding the common clk tree
Date: Wed, 27 Jun 2012 10:50:37 -0700	[thread overview]
Message-ID: <20120627175037.GF22766@gmail.com> (raw)
In-Reply-To: <20120628002925.dd144b4782398042593b6b47@canb.auug.org.au>

On 20120628-00:29, Stephen Rothwell wrote:
> Hi Mike,
> 
> On Tue, 26 Jun 2012 16:05:03 -0700 Mike Turquette <mturquette@ti.com> wrote:
> >
> > So please let me know if I still have the concept wrong and I'll change
> > things up.  Otherwise my clk-next fulfils all of the guidelines you've
> > mentioned below for inclusion into linux-next.
> 
> OK, that all seems to be fine.  I would make one suggestion: that you
> create the clk-next branch like this:
> 
> git checkout clk-next
> git reset --hard clk-3.x
> git merge clk-fixes
> git am patches/clk/next/incoming/*.patch
> 
> or maybe just merge clk-fixes directly into clk-3.x when necessary or
> from time to time and base clk-next just in clk-3.x.

Using clk-3.x as a base for clk-next sounds fine to me.  I'll use the
approach you outlined above.

Thanks much,
Mike

> --
> Cheers,
> Stephen Rothwell                    sfr@canb.auug.org.au



WARNING: multiple messages have this Message-ID (diff)
From: mturquette@ti.com (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: adding the common clk tree
Date: Wed, 27 Jun 2012 10:50:37 -0700	[thread overview]
Message-ID: <20120627175037.GF22766@gmail.com> (raw)
In-Reply-To: <20120628002925.dd144b4782398042593b6b47@canb.auug.org.au>

On 20120628-00:29, Stephen Rothwell wrote:
> Hi Mike,
> 
> On Tue, 26 Jun 2012 16:05:03 -0700 Mike Turquette <mturquette@ti.com> wrote:
> >
> > So please let me know if I still have the concept wrong and I'll change
> > things up.  Otherwise my clk-next fulfils all of the guidelines you've
> > mentioned below for inclusion into linux-next.
> 
> OK, that all seems to be fine.  I would make one suggestion: that you
> create the clk-next branch like this:
> 
> git checkout clk-next
> git reset --hard clk-3.x
> git merge clk-fixes
> git am patches/clk/next/incoming/*.patch
> 
> or maybe just merge clk-fixes directly into clk-3.x when necessary or
> from time to time and base clk-next just in clk-3.x.

Using clk-3.x as a base for clk-next sounds fine to me.  I'll use the
approach you outlined above.

Thanks much,
Mike

> --
> Cheers,
> Stephen Rothwell                    sfr at canb.auug.org.au

  reply	other threads:[~2012-06-27 17:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-26  1:55 linux-next: adding the common clk tree Mike Turquette
2012-06-26  1:55 ` Mike Turquette
2012-06-26  3:25 ` Stephen Rothwell
2012-06-26  3:25   ` Stephen Rothwell
2012-06-26 23:05   ` Mike Turquette
2012-06-26 23:05     ` Mike Turquette
2012-06-27 14:29     ` Stephen Rothwell
2012-06-27 14:29       ` Stephen Rothwell
2012-06-27 17:50       ` Mike Turquette [this message]
2012-06-27 17:50         ` Mike Turquette
2012-06-30 19:47 ` Linus Walleij
2012-06-30 19:47   ` Linus Walleij
2012-07-02 23:33   ` Stephen Rothwell
2012-07-02 23:33     ` Stephen Rothwell
2012-07-03  1:33     ` Turquette, Mike
2012-07-03  1:33       ` Turquette, Mike
2012-07-03  1:49 ` Stephen Rothwell
2012-07-03  1:49   ` Stephen Rothwell

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=20120627175037.GF22766@gmail.com \
    --to=mturquette@ti.com \
    --cc=amit.kucheria@linaro.org \
    --cc=arnd.bergmann@linaro.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=maxime.ripard@free-electrons.com \
    --cc=mkl@pengutronix.de \
    --cc=olof@lixom.net \
    --cc=pawel.moll@arm.com \
    --cc=rnayak@ti.com \
    --cc=sfr@canb.auug.org.au \
    --cc=shawn.guo@freescale.com \
    --cc=sr@denx.de \
    --cc=viresh.kumar@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.