From: stillcompiling@gmail.com (Joshua Clayton)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC] ARM: tango4: Fix build issues
Date: Tue, 29 Dec 2015 18:10:59 -0800 [thread overview]
Message-ID: <1525426.F8aV4pV4EX@diplodocus> (raw)
In-Reply-To: <5682F1AE.60108@free.fr>
Hi Marc,
On Tuesday, December 29, 2015 09:48:47 PM Mason wrote:
> On 25/12/2015 22:49, Mason wrote:
>
> > Move SMP setup to platsmp.c
> > Specify the CPU type to the assembler, and only for smc.S
> >
> > Signed-off-by: Marc Gonzalez <marc_gonzalez@sigmadesigns.com>
> > ---
> > arch/arm/mach-tango/Makefile | 3 ++-
> > arch/arm/mach-tango/platsmp.c | 16 ++++++++++++++++
> > arch/arm/mach-tango/setup.c | 14 --------------
> > 3 files changed, 18 insertions(+), 15 deletions(-)
> > create mode 100644 arch/arm/mach-tango/platsmp.c
>
> I have a question. When the original commit hasn't been pushed to
> Linus' tree yet, is the original commit simply amended?
> (fixup option in rebase -i)
>
> Or are they handled as regular commits on top of the previous commits?
>
Unless you are asked to revise and resubmit a patch, so that the
original is never accepted, all follow on patches end up a separate commits.
> Regards.
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kerne
Merry Christmas & Happy New Year,
Joshua
next prev parent reply other threads:[~2015-12-30 2:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-25 21:49 [PATCH RFC] ARM: tango4: Fix build issues Mason
2015-12-29 20:48 ` Mason
2015-12-30 2:10 ` Joshua Clayton [this message]
2015-12-31 13:20 ` Olof Johansson
2015-12-31 13:21 ` Olof Johansson
2015-12-31 16:31 ` Olof Johansson
2015-12-31 16:51 ` Arnd Bergmann
2016-01-01 11:11 ` Mason
2016-01-01 10:52 ` Mason
2016-01-01 12:03 ` Mason
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=1525426.F8aV4pV4EX@diplodocus \
--to=stillcompiling@gmail.com \
--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.