From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: PRIMA2: convert to common clk and finish full clk tree
Date: Sat, 7 Jul 2012 08:41:40 +0000 [thread overview]
Message-ID: <201207070841.41494.arnd@arndb.de> (raw)
In-Reply-To: <20120707023201.GC1230@gmail.com>
On Saturday 07 July 2012, Mike Turquette wrote:
> I don't mind dropping your patches from clk-next and taking new ones.
> Go ahead and send me a new patch which does everything instead of an
> incremental patch to simply 'git mv' the code. Feel free to split the
> patch up if needed.
FWIW, I would always recommend doing this in two patches, one that changes
the code and one that moves the file, in either order. The main difference
is that for those who cannot use 'git diff -M', reviewing the patch becomes
much easier when it doesn't look like one file is removed and another
completely different file is added.
Arnd
next prev parent reply other threads:[~2012-07-07 8:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 10:00 [PATCH] ARM: PRIMA2: convert to common clk and finish full clk tree Barry Song
2012-07-07 1:31 ` Mike Turquette
2012-07-07 2:23 ` Barry Song
2012-07-07 2:32 ` Mike Turquette
2012-07-07 8:41 ` Arnd Bergmann [this message]
2012-07-08 7:26 ` Barry Song
2012-07-09 18:00 ` Turquette, Mike
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=201207070841.41494.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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.