public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] move: rockchip: move clock drivers into a subdirectory
Date: Fri, 29 Jul 2016 22:42:48 +0200	[thread overview]
Message-ID: <8909926.YVrDd6ux0h@phil> (raw)
In-Reply-To: <CAPnjgZ39cp0MYtgLnFhwxOaKB-enU0NjfR1KPXSVV=UdfyRGpQ@mail.gmail.com>

Am Freitag, 29. Juli 2016, 07:51:14 schrieb Simon Glass:
> On 29 July 2016 at 06:47, Heiko Stuebner <heiko@sntech.de> wrote:
> > With the number of Rockchip clock drivers increasing, don't clutter up
> > the core drivers/clk directory with them and instead move them out of
> > the way into a separate subdirectory.
> > 
> > Suggested-by: Simon Glass <sjg@chromium.org>
> > Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> > ---
> > 
> >  drivers/clk/Makefile                    | 3 +--
> >  drivers/clk/rockchip/Makefile           | 8 ++++++++
> >  drivers/clk/{ => rockchip}/clk_rk3036.c | 0
> >  drivers/clk/{ => rockchip}/clk_rk3288.c | 0
> >  4 files changed, 9 insertions(+), 2 deletions(-)
> >  create mode 100644 drivers/clk/rockchip/Makefile
> >  rename drivers/clk/{ => rockchip}/clk_rk3036.c (100%)
> >  rename drivers/clk/{ => rockchip}/clk_rk3288.c (100%)
> 
> Isn't this a v2 patch? Anyway:

it seems I was in a bit of a rush, so yeah, this could also be labeled v2, 
although the only change is the "-M" for git format-patch. When rebasing on 
top of your rockchip-master, no changes were needed


> Acked-by: Simon Glass <sjg@chromium.org>

  reply	other threads:[~2016-07-29 20:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29 12:47 [U-Boot] [PATCH] move: rockchip: move clock drivers into a subdirectory Heiko Stuebner
2016-07-29 13:51 ` Simon Glass
2016-07-29 20:42   ` Heiko Stuebner [this message]
2016-08-04  4:20     ` Simon Glass

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=8909926.YVrDd6ux0h@phil \
    --to=heiko@sntech.de \
    --cc=u-boot@lists.denx.de \
    /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