From: pebolle@tiscali.nl (Paul Bolle)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] mach-spear: fixed spear1340.c file
Date: Thu, 03 Jul 2014 20:04:51 +0200 [thread overview]
Message-ID: <1404410691.16291.11.camel@x220> (raw)
In-Reply-To: <1404354994-7478-1-git-send-email-xerofoify@gmail.com>
On Wed, 2014-07-02 at 22:36 -0400, Nicholas Krause wrote:
> This is the fixed file after moving sata support to new file in
> spear1340_sata.c
>
> Signed-off-by: Nicholas Krause <xerofoify@gmail.com>
> ---
> arch/arm/mach-spear/spear1340.c | 111 ----------------------------------------
> 1 file changed, 111 deletions(-)
This patch, together with patch 1/2, basically moves a chunk of code
into a separate file, didn't it? If so, why did you split that move in
two patches?
And how does all this work without any changes to a Makefile?
> diff --git a/arch/arm/mach-spear/spear1340.c b/arch/arm/mach-spear/spear1340.c
> index 7b6bff7..f9d8ef3 100644
> --- a/arch/arm/mach-spear/spear1340.c
> +++ b/arch/arm/mach-spear/spear1340.c
> @@ -21,117 +21,6 @@
> #include "generic.h"
> #include <mach/spear.h>
>
> -/* FIXME: Move SATA PHY code into a standalone driver */
(I have no idea what this FIXME is about, but I do wonder whether that
new file by itself is the standalone driver this FIXME is about. The
spear developers will surely know.)
Paul Bolle
next prev parent reply other threads:[~2014-07-03 18:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 2:36 [PATCH 2/2] mach-spear: fixed spear1340.c file Nicholas Krause
2014-07-03 18:04 ` Paul Bolle [this message]
2014-07-03 18:08 ` Nick Krause
2014-07-03 18:36 ` Paul Bolle
2014-07-03 20:37 ` Nick Krause
2014-07-04 4:40 ` Viresh Kumar
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=1404410691.16291.11.camel@x220 \
--to=pebolle@tiscali.nl \
--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 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).